Google Wave, transparency* and engagement

I’ve been using Google Wave for about a week now and every time I log on I discover something new. I’ve read a few gripes about things being broken, or it being too confusing, or too quiet, but for me the biggest problem is having time to play around with it enough to learn everything it can do.

Lifehacker has been invaluable, as has this post and this one although when I swept off in a, well, in a wave of enthusiasm to embed a wave on here I swiftly discovered my limitations. I was pretty downcast as well until I realised that it should be quite easy as it’s all done by automation but the facility isn’t switched on yet. And since my coding skills are pretty lowly I am really not up to tackling this without bot assistance. So instead of getting hung up on what it can and can’t do, I think I’m better off trying to work out the rules of engagement.

For example, I’ve just crashed a Wave. It’s about Flickr, I didn’t mean too, but I have just added myself to the discussion simply by clicking ‘reply’ to see if I could. No one cared but it was weird that a debate was going on between a group of people who obviously know one another and suddenly I’m in the middle of it. All a bit too “Ta-daaaaaaa!” for me right now. I guess it’s because I am still treating it like it’s a private conversation; it is a public Wave on the public timeline but, like Twitter, it’s not easy to keep that in mind when you’re using it. It becomes a little world and when someone new arrives it’s a surprise.

Here’s something else to, raised by Nick Miller in the ‘Wave, journalism and the mainstream media’ wave I joined today:

Watching people type in real time is fantastic, in a voyeuristic way. You can see their minds working.

But do we want people to see our minds working? How many times have we written an email, tweet or forum comment, only for our censor to kick in and say ‘don’t send that!’.

How many times? For me, a lot. Right now I’m getting mocked for my poor typing skills by fellow wavers who can see me correcting as I’m going – but there’s a lot more onus on me now to think through what I’m going to say. You know in Google Chat when it says X has entered text and it generally means they’re sense-checking what they’ve written? In a wave, your thoughts are revealed letter by letter. And I get very self-conscious if I start a sentence, then backtrack/delete and rephrase it while other people observe me making those changes.

What Google has done is create an application that allows those watching a wave to see thought-proceses at work; a wave is an aid to Transparency. A journalist using a wave is asking people to collaborate wiki-style in information-gathering – in fact, s/he should be writing the article in the wave, so contributors can participate in living, breathing news-making – a space where they can throw questions, facts and comments in themselves – not be served up a flat, one-dimensional statement of facts that ends when the story is thought to be the required amount of words.

I remember last July when a crane collapsed on an apartment block in Liverpool, and how Twitter was integral to the Post and Echo’s coverage – imagine if we’d been able to start a public wave on the topic and embed it on our websites. By bringing a contributing audience into our site and asking them to help us – using maps and images being added alongside observations and comments – the ‘journalist as gatekeeper’ would have been truly defunct. Rumours posted could be quickly checked and a breaking story updated constantly. And it would remain open for users to revisit, and add to. The playback option shows exactly who made what changes when, which is also pretty handy.

It’s not Twitter, or Facebook, or a wiki, or even email but it is, I think, a great learning opportunity for journalists who are prepared for the sense of exposure and vulnerability it brings. Letting someone see the messy spaghetti of a story-in-progress is something we’ve been conditioned against for decades – it’s many years since I sat my NCE but I’ll bet the NCTJ is still interested in the end product, not the journey – and Google Wave is all about in-progress. It would be unsettling (and possibly, initially, irritating) as a journalist to type a statement and then see another wave participant dive in and start editing the text you’ve just written to change a fact, or add information but I’d imagine it would also be exciting to see a news story being woven out of random strands of questions and facts.

Google Wave is going to be what a journalist wants make it – crowdsourcing, debating, real-time news-gathering, breaking news, image sharing, archived events, live-blogging, polling, asking for feedback – but, I think, the most exciting thing it offers is the opportunity to change the way we think about interaction and engagement. As a learning tool for transparency, it really could be amazing.

* Shortly after I published this post it was pointed out to me that the headline read ‘tansprency’; I told you my typing was hopeless…

Advertisements

About Alison Gow

I'm a journalist, particularly interested in story-telling, networks and digital innovation.
This entry was posted in collaboration, transparency. Bookmark the permalink.

7 Responses to Google Wave, transparency* and engagement

  1. A useful post with links to more useful posts esp the Daniel Tenner one which gets you thinking about Wave in the right way… thanks Alison.

    I'd love to crash a wave, but I haven't found a wave to crash yet ;/

    Tim

    Like

  2. sarahhartley says:

    I haven't had the opp to try out Wave as yet but your post has made it sound far more interesting than previously.
    Anything that makes the process more visible and easier to participate in has got to be a good thing for journalists – but I'm still not going to join those begging for invites. Much 😉

    Like

  3. Show off – I'm still Waveless.
    Your post makes it sound like Wave is another opportunity for journalists to get involved in instantaneous conversations.
    But do you foresee Wave being used like this by journalists?
    What I'm really asking is, is it just all hype, or is it a worthwhile journalistic tool which really will change not just what we do, but how we do it?

    Like

  4. Sarah says:

    I haven't seen Google Wave yet but have wondered what it's about and how it can be used.
    Thanks so much for writing this. I can't wait to try it out and see how it can be applied in the newsroom.

    Like

  5. I'm another Waveless person. When it was first announced, my reaction was “yeah, yeah, another so-called killer app that'll probably turn out to be a lot of hot air”. So I didn't try to wangle an invitation. But now, the more I hear of what it can do, the more intrigued I am to try it out myself (although, trust me, my typing's a LOT worse than yours). Thanks for a very insightful post and please bung me an invitation when you have one going spare!

    Like

  6. Hannah Green says:

    So far I have managed to crash 3 wavesa nd I have only had access to Google Wave for about 12 hours.

    It does look like it could be really really good when full functioning, especially when combined with sites like help me investigate.

    I am still having problems embedding google maps or 'robots' into waves. Any tips?

    Like

  7. Alison Gow says:

    @Kev to be honest, I don't see a sudden rush of journalists clamouring to work in Wave in collaboration with others. But it just takes a couple doing this to to start opening others' minds to the possibilities. If it wasn't still in such limited availability we could have had a QM2 Wave for example – and invited users to be a part of writing the 8-page commemorative supplement that was published today. There is no real reason why such collaboration wouldn't work – in theory.

    Tim, Sarah, Louise & Sarah – thanks guys 🙂 I think Google has put a halt on nominations for the moment (read something on the blog today) but will be allowing new joiners again soon so good luck! I'll let you know if I get the opportunity to nominate anyone.

    Hey Hannah – it is still buggy and you might just be catching it at those times. But here's a quick how-to:
    First, make sure you have Gears enabled. Google will ask you this when you click reply but if you're rushing (like me) you might miss it the first time.
    Then…
    Maps: Click the little map pin and a map of your location appears. You can search etc for where you need, then add pins, lines etc as you wish.
    Gadgets – go to http://www.google.com/ig/directory?synd=open then select the gadget you want. Click 'get code' and then copy the bit of the code that starts “url=” and ends “.xml” – not the whole thing. Go to your Wave, click Add Gadget, copy your gadget url in there and – phew!! – you should be sorted. Or possibly have blown up the Isle of Man.
    There may be a shorter way, but I don't know it.
    By the way, I'm alisongow@googlewave.com

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s