Google Wave is a browser-based collaboration tool that combines messaging, document writing and discussions in real time. I participated by proxy in an experiment with the tool last week that involved fellow content management professionals. These are my observations.
Saying is easier than listening.
In many ways the collaboration was too real time. In a spoken conversation, talking across each other isn’t really possible. In the Wave, it’s the norm. Even with half a dozen participants, it seemed everyone was piling in trying to get their thoughts down rather than considering what people were writing elsewhere. There were multiple threads to the document that you couldn’t follow at once It was like being in the middle seat at a party: it seemed like a good place to be but you couldn’t figure out which conversation to jump into. This might say more about the participants than the platform, but it is a serious issue for collaborative working where listening to a conversation, being able to respond to the speaker and draw out more information is crucial to constructive dialogue.
More is easier than less.
Anyone can add to the document, but there are no commenting features and a social reluctance to delete what someone else has written. The effect is that assertions are qualified rather than challenged or deleted, meaning that you end up saying in thirty words what you could have said in ten. The compound effect of this writing style is that you layer meaning on top of meaning to the point that — as Julia Kristeva might have pointed out — as a group you’ve said something different to the individual’s original point. That’s not collaboration.
You get more than you need.
I couldn’t quite figure out what we got from the Wave that we couldn’t get from just a Google document combined with chat or a similar tool. It was less the case of the glass being half full or half empty than the glass being twice as big as we needed. There were too many features. Nearly everyone experienced serious browser issues — except Ian, whose virtual shoulder I was peering over— whose Chrome held out where Firefox faltered. Wave might run in a thin client, but it’s a fat piece of technology.
So was Wave a total washout? No, but I think it will take a lot of adapting to. If only there were some browser-based tool out there that wasn’t reliant on Ajax, that was near real-time but forced you to refresh so that you listened before you spoke and which encouraged you to be as brief as possible when you did speak up.
Where could we find a tool that met those requirements? I’ll have to ask the good people of Twitter.
- Things We Hate About Content Management
- A Collaborative Google Wave Blog Post.
- I Predict A (CMS) Riot: 1 hour, 6 People, 1 Wave, 1 Post
- Wave experiment: Things We Hate About Content Management
- The people who contributed to the post were: @irina_guseva, @justincormack, @iantruscott, @andrew_liles @adriaanbloem, @McBoof