Google today announced the impending release of their new…product, Google Wave. I hesitate when describing it, because it’s actually pretty tough to categorize. Techcrunch has a thorough writeup of the functionality and Mashable has a brief of their own, but neither does much analysis, so let me try to summarize.
Google Wave is:
- Like email, but won’t work (navtively) with existing email
- Like IM, but it isn’t an application
- Like Facebook messaging, but without Facebook
- Like Facebook’s application platform, but without Facebook
- Like Twitter, but without a public-facing feed
- Like IRC, but less temporal
Does that help? Maybe not.
Let me try to sum it up in a positioning statement that I’m making up based on the proposed featureset:
Google Wave is a web-based messaging system that helps people communicate, share, and collaborate with friends, family, and business contacts both in real-time and asynchronously.
If we look at it in these terms, Google Wave is not only extremely ambitious but is also set squarely against Facebook.
You may consider this comparison invalid because Google Wave has so many features that Facebook doesn’t and Facebook has a ton of features that Wave doesn’t, but users don’t look at features, they look at problems the product solves for them. Is it filling a need that isn’t met right now, or is it filling the need better than existing services? It’s unlikely that people would give up Facebook for Wave, so the question for Google comes down to: will they use both? You can ask the same question about Wave vs. email, IM, and Twitter.
In order to think Wave will be successful, you have to think the problems it solves are important. Here are some of the problems it purports to address:
This is just a start of what they want it to do. One of the creators, Lars, said of Wave,
“My vision is to have the one communication tool. I want all the use cases to be covered. We made up ideas of what Wave could be used for — negotiating contracts, writing articles. Lots of things.”
Is it trying to do too much? Very likely.
I fear that Wave breaks one of Google’s own product development tenets: fail often, fail early (or maybe fail early, fail often, I don’t remember, but I know there was a lot of failing involved.) This project has been in development since 2007 and has 50 developers working on it, and it already has a plethora of what we product managers call “would-be-nice” features. I encourage Google to make sure the core features work and release this thing as soon as possible to see if people like it at all. If they like it, THEN add the silly extras like real-time wiki-style collaborative editing that lets you see what other people type as they type it.
I do like the concept behind Wave in how it aims to unify communication, but I want to see that happen in a way that simplifies my life. Read through the comments on the TechCrunch article, and you’ll see that most people think it looks too complicated. As a contrast, no one who saw the iPod or iPhone unveilings thought either device would complicate their lives – they are both beautiful in their simplicity, and that’s why they sell by the boatloads. Google will have an uphill battle marketing this product until they can show an average user how it will simplify their lives. If they clear this hurdle, Facebook needs to watch out.