So I got my Google Wave invite a couple weeks ago.  I have been fairly skeptical of all the Wave hype lately, but I was still intrigued and very much looking forward to seeing what it had to offer.  I logged in, and…didn’t know what to do.  I felt like the first guy in the world to have email – it sounds like a cool idea, but there’s nothing to do until you know other people who have email, too.

Wave allows you to send invites out to 9 friends, so I sent some out.  And waited.  A week later, finally they started showing up, and I could really see what Wave had in store.

Wave is slick, and pretty, and for the most part fairly easy to start using, but it has too many flaws that will keep it out of the hands of mainstream users and limit its adoption to tech-savvy user groups.  My biggest issues with it are:

• No email integration. This is supposed to be the communication tool for the next century, but it isn’t backwards compatible with the communication tool(s) for the last century.  Surely someone will write an extension to allow it to interface with email, but at that point you’ll lose all the cool Wave features, making the whole exercise moot.
• Nothing to do until you know people who have it.  Adding an email extension would alleviate this.
• Built by programmers, for programmers. As Lifehacker points out, “the first search command every Wave newbie needs to know (is): with:public” which will allow you to see public waves and is very useful when you have no friends using Wave yet. Really guys?  Resorting to cryptic command lines in a supposedly mainstream web app?  Let me guess, was this documented somewhere in your man pages?
• No notifier application. If you’re not in Wave, there’s no way to know you have new Waves waiting for you.  There is a third-party app to do this, but it’s annoying that I have to have a notifier for my email and Wave.
• Watching people type in real time. Internet “old-timers” will remember that the original tools for instant messaging over the Internet (like “talk”) worked like this.  Surprisingly, it’s not much fun to watch other people type and correct their own typos.  Really.  ICQ and AIM popularized the “wait until they’re done to send the message” model, and no one looked back (until Wave.)
• Editing other people’s messages. If I want to collaborate on something with my friends, I’ll tell you.  Don’t just let other people edit my messages willy-nilly.  It’s fun for a few minutes to edit what your friends said, but threads can quickly become chaotic and impossible to follow.  There’s a reason message boards don’t have this feature.
• 

  Click for larger image

  Un-novative thread presentation. In a giant leap back to 1997, Wavelets are organized by thread first and not by date.  This means that responses to any message within the wave get indented directly below that message rather than showing at the bottom of the Wave, so new messages end up located all over the place within the thread.  In long threads, you may have to scroll up and down for several pages to find the new messages.  For ‘net old-timers, you may remember that many of the first, primitive online forums were arranged like this, but somewhere along the lines everyone discovered that it was easier to follow a conversation by always posting new messages at the bottom and just quoting the message it was in response to.  It’s not as elegant from a purist perspective, but it’s much easier for the user to follow.

• Replay. The only reasons the Replay feature needs to exist are 1) the flawed thread presentation mentioned above and 2) the fact that anyone on the thread can edit any message.  Using replay isn’t fun or interesting – it’s tedious, and it’s there to compensate for unintuitive UI and unnecessary features.
• Worst offense: Too many things in one. Wave seemingly tries to replace your email, your IM, and your Google Docs, but doesn’t do a great job on any of them.  I much prefer using my IM client to talk to my friends, so I’m not giving that up.  Gmail is a better email client, and Google Docs and Spreadsheets are pretty great for collaboration, so I’m not giving those up. (Gmail and Docs already have messaging built-in, and it’s executed rather nicely, btw.)  By trying to do so much, it doesn’t do anything well.

I should have known we were in trouble when this was the first line of the “Getting Started” wave: A wave can be both a document and a conversation. For how many users would a statement like this make any kind of sense?  For someone like myself, that’s a pretty deep statement and worth some pondering, but how would that help my mom figure out what’s going on?

Wave is truly a technical marvel, and the fact that it works as well as it does is impressive.  It’s easy to see why the room full of developers at the Wave unveiling was in awe.  But, you must do more than impress developers to build a tool that the mass market will adopt.

Ultimately I think Wave will find some fans within tech-savvy organizations because it could be useful for collaboration and communication in situations where everyone in the company is using it (competing with Yammer), but it won’t gain any significant market penetration compared to email or IM.

Related posts:

• Google Wave and the Dawn of Passive-Aggressive Communication
• Google Wave is Easier to Understand than…

Google is releasing 100,000 invitations today to Google Wave, their next-generation communications tool that could replace email, IM, and collaboration software all in one shot.  I don’t have an invite yet, so…you can check out Lifehacker for a nice hands-on review.

My take on Google Wave from when it was announced

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:

• It’s hard to communicate and collaborate with friends over email / IM / other web services
• There are too many ways to communicate with people online – I want a single method
• Email, IM, and online messaging don’t allow collaboration, and allow limited use of multimedia
• Email is not a dynamic communication mechanism
• It’s hard to share my email conversations with people who aren’t in the conversation
• “When (messaging is) not live, you lose your attention on a conversation, but when you see it live, you’re engaged.” (I remember the days of using “talk” when you could see the other person typing and correcting themselves as they type – it actually kind of sucks.)
• “IM and email shouldn’t really be two separate tools”
• I want to allow “anonymous comments, or a number of different identities” in my conversations

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.