Is Google Wave a Tidal Wave?

800px-Hokusai21_great-wave.jpg
"The Great Wave off Kanagawa" by Katsushika Hokusai (1760-1849).


Google is on a fishing expedition to see if we're willing to take web-surfing to a whole new level. My colleague Steve Backman introduced us to Google Wave a few months ago. I attended a developer's preview at Techsoup Headquarters last week, and I have some additional thoughts to share.

Google's introduction of Wave is nothing if not ambitious. As opposed to saying "We have a new web mashup tool" or "We've taken multimedia email to a new level", they're pitching Wave as nothing less than the successor to email. My question, after seeing the demo, is "Is that an outrageous claim, or a way too modest one?".

The early version of Google Wave I saw looked a lot like Gmail, with a folder list on the left and "wave" list next to it. Unlike Gmail, a third pane to the right included an area where you can compose waves, so Wave is three-columner to Gmail's two.

A wave is a collaborative document that can be updated by numerous people in real-time. This means that, if we're both working in the same wave, you can see what I'm typing, letter by letter, as I can see what you add. This makes Twitter seem like the new snail mail. It's a pretty powerful step for collaborative technology. But it's also quite a cultural change for those of us who appreciate computer-based communications for the incorporated spell-check and the ability to edit and finalize drafted messages before we send them.

Waves can include text, photos, film clips, forms, and any active content that could go into a Google Gadget. If you check out iGoogle, Google's personal portal page, you can see the wide assortment of gadgets that are available and imagine how you would use them -- or things like them -- in a collaborative document. News feeds, polls, games, utilities, and the list goes on.

You share waves with any other wave users that you choose to share with. User-level security is being written into the platform, so that you can share waves as read-only or only share certain content in waves with particular people.

Given these two tidbits, it occurred to me that each wave was far more like a little Extranet than an email message. This is why I think Google's being kind of coy when they call it an email killer - it's a Sharepoint killer. It's possibly a Drupal (or fill in your favorite CMS here) killer. It's certainly an evolution of Google Apps, with pretty much all of that functionality rolled into a model that, instead of saying "I have a document, spreadsheet or website to share" says "I want to share, and, once we're sharing, we can share websites, spreadsheets, documents and whatever". Put another way, Google Apps is an information management tool with some collaborative and communication features. Google Wave is a communications platform with a rich set of information management tools. It's Google Docs inverted.

So, Google Wave has the potential to be very disruptive technology, as long as people:

  • Adopt it;

  • Feel comfortable with it; and

  • Trust Google.



Next week, I'll spend a little time on the gotcha's - please add your thoughts and concerns in the comments.

Comments

I like Google Wave a lot! But

I like Google Wave a lot! But I really don't see it as a SharePoint alternative. In spite of its power, its strength, which is its freedformedness, is what doesn't qualify it as an alternative to SharePoint. A collaboration solution does need some amount of structure, to reflect the organizational structure. There has to be some way to group documents together by team/department. Wave lets you quickly get together and work on a document in real time. But what if a group needs to keep coming back to some documents. Do you dig for them through the Wave chaos?

Maybe SharePoint has too much structure, and needs IT intermediation at every point, and thats why alternatives like Google Apps and HyperOffice make sense. But doing away with that structure altogether...i don't think so!

Just wanted to add a timely

Just wanted to add a timely link here: Google is opening up Wave to Apps users: https://services.google.com/fb/forms/waveforapps/

Check it out!

The idea that Google Wave

The idea that Google Wave will eventually replace email will take some getting used to, thats for sure. But, it is an unavoidable eventuality. Email is a way too inefficient mode of communication, especially since time is money, and email isn't real time.

Google Wave, by itself, might not succeed but the technology that it is based on is definitely going to make the individual and business workdesk a much better place.

Contextualised communication and collaboration tools, like what Google will come out with in september, already exist in the market e.g. Colayer(http://colayer.com)

Visit the Virtual Reception at Colayer and you will get an idea what Google is aiming at.

Marc - I don't think you have

Marc - I don't think you have to worry; waves won't replace email in any big hurry, and, if they do, then Microsoft should have software that works with them -- there will certainly be alternatives to Google as the application. And I think it's still quite iffy that Wave will be more than a brilliant idea that is still ahead of it's time - by the time adoption of this type of thing makes sense, it might be an evolution of email that develops concurrently.

Michael - Good point. I'll

Michael - Good point. I'll flesh this out in my follow-up (which is in draft), but it's absolutely the case that Wave will be so flexible that it will have a lot of uses and value in situations that Google has little to do with. But Google is pushing this the way that they're pushing it because, if it takes off, it will be a great front-end to their data, and their mission is to catalog the world's information. So, what qualifies as a major success for Wave? I think, things that rely on open data sources and a culture that can adopt them.

As much as I like the idea of

As much as I like the idea of the Wave, I can tell you that the effort of migrating to Google Apps at my nonprofit makes me think twice (or more) about moving to this platform. (Read this as: "So I can still use Outlook, right?")

Speaking of spell check,

Speaking of spell check, there is a good program Spell Check Anywhere (SpellCheckAnywhere.Net) it adds spell check to all programs.

Very nice introduction Peter.

Very nice introduction Peter.

One thing however... When I was introduced to Google Wave, I was told that in addition to being a hosted service with an API layer, it was also a protocol that could be used by people outside of the Google framework all together. If that's true, then it's possible that corporate networks could use this without Google, and your trust question goes away.

Given it's likelihood of

Given it's likelihood of being browser independent, it's definitely gonna hit Sharepoint where it hurts.

What a great project tool!