Google Wave: Disorienting if not Disruptive

·—— ···· ·· — ····· ···—— ——···

When Gmail came out, it had a clear story even if some people didn't like it: Email without folders. Google Wave attempts to be a much more disruptive technology, and—perhaps fittingly—my first impression is one of disorientation. I'm struggling to connect.

Am I composing an email? I have a three-pane layout with an inbox and a contact list, but there are other people editing at the same time as I am. There's no time to "compose" here.

Am I building a shared document? I have a document canvas with rich widgets, but it's rather cramped, and these documents are awkwardly splintered into subdocuments, and it's unclear whether I am building something long-lived or ephemeral.

Am I chatting? Others are editing in real-time, but there is no continuous stream. Do I answer their question inline, in a response, in a subdocument, or in a new Wave?

This high-level mental fog is mirrored in the UI. Whether in email, documents, or chat, I expect to be able to just click somewhere and start typing. But with Wave there are extra steps that I still haven't internalized yet. Do I right click? Select and (right?) click? Click a little menu dropdown? Click in the thin little space to start a new reply? Or should I inline-reply? Now how do I do that again? Gah! Meanwhile, others are editing in real time, adding to the feeling of pressure.

I can see a few scenarios:

I agree that there is room for something by way of a communications [r]evolution, but I'm not sure Wave is it. Wave doesn't feel accidental enough to be revolutionary. Though even if the real winner comes from left field, Google isn't ruled out: remember that they had already invested in Google Video when they bought YouTube.

For the time being, I see myself checking in on Wave occasionally, but sticking with Gmail, chat, and EtherPad for day to day communication.

You?

·—— ···· ·· — ····· ···—— ——···
Feed back to Chad Whitacre.