Wave is a recent innovation from Google, currently in restricted beta. It's a combination of e-mail, instant messaging and wiki. So if you even feel the need to utilise e-mail, instant messaging and wiki functionality simultaneously then this is the app for you. Actually, that's a little unfair.
This is what it looks like:
So, broadly it looks like an e-mail client. I won't describe the details here but you can get a better idea from the very fine Complete Wave Guide.
At the moment the problem with Google Wave is that the a relatively small number of people have been given the equivalent of e-mail addresses and told to randomly e-mail each other. Unsurprisingly they're spending a lot of time "e-mailing" each other about Wave. However, there is serious potential in Wave, aside from the traditional Waving about Wave I got lucky and managed to have a non-Wave useful discussion on Wave. It started with a thing that looked like an e-mail (I had a bunch of questions), my interlocutor started answering the questions in real time. Wave allows you to launch chat at any point in an e-mail, not only that it always you to see your colleague typing character-by-character. In earlier forays this had been irritating but for a 'real' question it was actually rather useful - I could see my colleague getting the wrong end of the stick and put him right promptly. We managed to usefully flit between several conversations, adding things as they occurred to us and the end result is a nice record of a branching conversation.
As a wiki / document preparation system I'm less convinced. The core formatting available in Google Wave is fairly basic, although it can be extended significantly using gadgets and robots, but I can't see it being a comfortable way of working together on anything other than quite a short document.
I can see this being a great replacement for interminable e-mail threads between multiple participants, and even a way of writing minutes for a bunch of people sitting in a room with each other. If Google Wave were ubiquitous and people were willing to use it, then it would be a significant improvement over e-mail. Ubiquity may be attained in the future for the domestic user - I could imagine it becoming available as an option in Google Mail. To be honest I see far more applications for the business user and there, for larger organisations, uptake will be much slower.
This leads to another issue, even if they have access will people use such a tool? I'm dubious about this, I work in the research arm of a large commercial organisation. So you'd expect this group to be more tech savvy than average, but uptake of new software is pretty slow, people have taken to instant messaging but not wikis, reference management software, revision control, all things you might expect them to find useful. Once you get past the standard business suite of Word, Excel, PowerPoint and Outlook enthusiasm peters out and arguably mastery of even these applications is limited. This isn't a criticism of my colleagues, it highlights how difficult it is to gain traction with new software. When it comes down to it remembering how to use software is hard and unnatural so not surprisingly we don't do it very well.
Ultimately Google Wave is another tool, in a toolbox that is overflowing.
4 comments:
I'm glad you've found it more useful than our first attempt! I've not had the opportunity to use it properly yet, but I could see the live text updates as being very useful in my workplace, where time is precious and quite frankly digging through e-mail trails or calling a proper face to face meeting can often be a nightmare. It seems to me that it makes e-mails slightly less impersonal.
Like any new technology the proof will be the take-up.
I'm not holding my breath - the intersection of (1) people who have Wave (2) people who I need to communicate with and (3) people who willing to use Wave has size approximately = 1!
I've been trying to get them to use a wiki with minimal success...
I'm yet to be convinced about the real time features. Reply-all is dangerous enough, but seeing other people's unedited/proofread replies may lead to more...uhm...openness than we're accustomed to! (politeness on Google Wave may be a good blog post!)
I’m using Wave to draft out a funding application with a colleague – working quite nicely for that, especially for those online submission forms that only accept plain text. It is useful to be able to see exactly what he changes, and being able to work on the same draft at once is great.
Will be better when more people have it!
@KJHaxton I was dubious about the real-time features until I used it for a practical exercise, at which point I became slightly less dubious. I understand the greyed out 'draft' button will be enabled in the future to switch off real-time features.
Very interested to hear of your practical use for it on preparing a funding application. How long is the total text? My worry is that Wave doesn't have features for manipulating a moderate size chunk of text. I use Document Map and style based headings in Word to help me get around.
Post a Comment