Collaboration ground rules

Sometimes to make collaboration work you need to set some ground rules.

It’s easy to say, “let’s start up a google doc!” – and imagine everyone leaping in to give their ideas. But it’s not so simple as that, especially if folk haven’t had the experience or confidence in this way of working.

Instead it’s necessary to have a think about how the collaborative activity might be approached, and ensure everyone is aware of the process you have selected.

Often this will be the case when the technology available is a bit lacking. As an example, a recent collaborative effort I started was based in a ‘Note’ within a group on Yammer. Notes are the collaborative writing part of Yammer, but they aren’t terribly sophisticated and won’t allow you to use formatting such as tables.

So, I spent a bit of time describing how to add ideas to the list. I came up with a fairly simple process that involved a bold heading for each new item, with two bullets points underneath for other related information to be recorded.

Without this introduction, people may have been unsure what to do, and so not bother, or even accidentally start hacking up what others had written.

At the very least, when working on a Google Doc with others, for example, I’ll put “No deletions!” at the top as a general rule to people.

Any other collaboration ground rule tips to share?

Original post