Google Wave made a conversation behave like a shared document
Most email has a clear sequence: write a message, send it, then receive replies. Google Wave replaced that sequence with a shared space called a “wave.” People could type into the same conversation and see one another’s changes appear as they happened. Replies could branch from particular lines, and participants could edit earlier text rather than simply add another message below it.
That made Wave useful for work that really was collaborative—such as drafting a plan or coordinating an event. But it also changed what a message meant. A sentence might be a finished note, a live draft, or one piece of a discussion that had split into several branches. Users had to work out not only what to say, but where and how to say it.
The interface asked users to learn a new grammar
Wave tried to combine familiar tools without preserving their familiar boundaries. It looked partly like an inbox, yet a wave was not simply an email thread; it behaved partly like a document, yet it was organized around participants and replies. The same live editing that made collaboration fast could also make a conversation feel unsettled: text might change while someone was reading it, and branching replies could be hard to follow.
The deeper problem was not that the features had no purpose. It was that their advantages depended on people adopting a new shared habit. Email’s limits are also its cues: a sent message is a discrete turn, and a reply usually arrives in a predictable place. Wave removed those cues in favor of flexibility. For many users, the result was a powerful shared workspace without a clear answer to the basic question: “Is this a message, or are we still editing it?”
