Hipchat – neat group instant messaging app

Hipchat looks a neat tool for those teams with remote workers in particular.

Group chat is a fantastic tool for a distributed team because of its persistence. You keep your chat window open all the time, dropping in and out when required. It reminds you that you’re part of a team and that there are people out there you can chat to when you need to.

Hipchat seems a really nice implementation of this idea. It’s web based but also has desktop and mobile apps for all the major platforms.

Key features include a searchable archive of conversations, secure access, file sharing and the ability to spin up quick video chats when required.

What’s really nice is that is it free for teams of up to five – meaningful that for a small group, it’s perfect.

Here’s a video that explains more.

[youtube=http://www.youtube.com/watch?v=8mKivE8WqI4&w=560&h=315]

Making remote work work

SONY DSCA key part of working smarter is the idea of flexible or remote working. One neat way of describing it is that work isn’t a place you go to, it’s what you do.

There’s a lot of misunderstanding though about this concept, with it often being seen as a perk for an individual employee, say, rather than an organisational approach to work and how it should be done.

Here’s some success factors in making remote work succeed on your team.

Right location for the right work

Remote working doesn’t automatically mean home working. It means going to the right place for the particular work that is being undertaken.

Potential locations include:

  • Home
  • Cafes
  • Libraries
  • Co-working spaces
  • Other people’s offices
  • Your office

What’s more, a remote worker doesn’t just work in one of these locations but should use a range of them depending on what they are trying to achieve.

No single comms channel

Don’t pick one channel for communicating amongst remote workers. Again, as with work locations, it depends.

Some of the options include:

  • Instant messaging
  • Email
  • Group chat
  • Status updates
  • Collaborative editing
  • Video chat
  • The phone

The temptation is often to try and pick a single winner (and losers) for communications in a team. We’ll do everything through Yammer! Never use email – it sucks!

There are a range of variables that will affect which channel you might use for a particular comms task but the most important are: what are you trying to achieve; and what are your colleagues most comfortable with?

It’s always good to have a range of options available that everyone is familiar with so that no matter what the task is, you’ll have the tools to do the job to hand.

Keep communicating

In an office environment, it could be argued that over communicating is possible. Not so for a team that works remotely.

Part of the point of remote working of course is to escape the hustle and bustle of a busy office. In which case, an individual worker could just step back, switch off, and find a quiet space to concentrate in.

The rest of the time though, it ought to be possible to get hold of people individually or as part of a group. So find a way of doing group chat and encourage people to be present in it most of the time. Or ensure there is a way of privately instant messaging individuals to quickly check on the status of an action or project.

This means it’s important not to get into the habit of thinking that as someone is working outside the office, they shouldn’t be disturbed. In fact, because they aren’t physically present, disturb them more!

Meet up

Remote work really doesn’t mean never actually meeting your colleagues. What it does mean is that these get togethers become even more important to get right.

This means not meeting up for the sake of it, but ensuring you have some objectives for a get together. So, only meet when there is a need to, and not just because it hasn’t happened for a month.

Consider having a project for a meetup, with a specific deliverable to come out of it. Having everyone in the same room might not happen often, so consider whether it’s possible to run a micro project in that time.

Whole team or organisation approach – everyone adapts

Remote working only works when everyone buys into it – even (especially!) those who don’t work remotely themselves.

The important parts to remember are:

  • Remote work is not a privilege for an individual, it’s a better way of getting work done for the whole team
  • Remote work is not just home working, it’s finding the best place for an activity to happen, which could be any one of a number of locations
  • Remote work requires a shift in focus on measuring performance by qualitative outcomes and not quantitative outputs or time spent in the office

Without this wider development of working culture and acceptance of remote working and what it means for an organisation, it will always be seen as a bolt on, and many of the opportunities it presents will be missed out on.

What do you think? What are your experiences of remote working, and what helps and hinders its success?

Five for Friday – 28 March 2014

linksFive for Friday is WorkSmart’s weekly roundup of interesting stuff from the week’s reading.

  1. Your wiki is a dump
  2. Mixing the unconference format into a traditional conference
  3. Why Companies Fail To Engage Today’s Workforce: The Overwhelmed Employee
  4. The Responsive Organization
  5. Leanership: a new way of work
Did you know that WorkSmart has a Pinterest board where loads of cool stuff is shared?

We also now have a LinkyDink group which will automatically email you links to read everyday!

Fixing email : inbox zero

merlinmannSo I posed a fair few questions in my last post about email. How about some solutions?

Here’s one – inbox zero.

Inbox zero is… what? A methodology? A process? A mindset? Who knows. What we do know is that it is the brainchild of Merlin Mann, a productivity expert from the US.

Here’s the skinny:

  • Email’s just a medium
  • One place for anything
  • Process to zero
  • Convert to actions

Here’s the video from a few years ago whee Mann discussed the topic in detail.

[youtube=http://www.youtube.com/watch?v=z9UjeTMb3Yk&w=420&h=315]

If you don’t have time to watch that, here’s the quick version:

For every email you read, you should do one of the following things: delete it forever, archive it for reference, delegate it to someone else, respond immediately, or turn it into an action that you will execute at a later time or date.

In other words, move emails on fast. Get them out of your inbox and into the trash, in your archive, forward it on, reply, or make it an action.

People often make emails into actionable items by leaving them in their inbox, but this is bad. Instead, create a task in your todo list and then delete or archive the email. At the very least, have a folder in your email system called ‘Actions’ and drop it into there.

The keys to inbox zero are: first, that you recognise that actually you only receive a handful of emails every day that are worth more than a very cursory amount of your time. Second, your email software is good for receiving and sending email and that’s it. Third, get those worthwhile emails out of your inbox and into a more appropriate tool as quick as you can.

Have you tried inbox zero? How did you get on?

Should every member of staff do a stint in customer service?

customer-serviceI’m loving Scott Berkun‘s The Year Without Pants – an account of the time he spent in startup land working with Automattic, the company behind WordPress.com.

I’m going to do a full write up at some point, but some bits of the book are so good I can’t wait to share them.

Here’s one. Every new hire at Automattic spends time working in customer service, answering user questions and queries and solving their problems. No matter what their position in the company – everyone has to do it.

The reasons are clear. It helps that new starter understand the customer’s needs above everything else – what their pain points are, what they are trying to achieve and so on.

It is also the best way to learn about how any kind of system or process works, by hearing from those who are using it every day, and running into problems. Fixing those problems is a fantastic way to learn how something works.

So perhaps this is something other organisations could take up? Perhaps when a new chief executive takes over at a local authority, they should spend a week or two on the phones at the customer contact centre, learning directly from the people who depend on the services provided by the organisation.

What do you think?