The encyclopedia · Product & Design · Product decision · 2009–2010
Google Wave tried to replace email, IM and wikis with one tool nobody understood
Announced to a standing ovation in 2009, Google Wave merged email, chat and docs into one tool. Users couldn't figure out what it was; Google killed it.
Google · 2009-05-28
What happened
At its developer conference in May 2009, Google unveiled Google Wave to a rapturous, standing-ovation reception. Wave was an ambitious attempt to reinvent online communication: a single real-time platform that merged email, instant messaging, wikis and collaborative documents into one living 'wave' that multiple people could edit together, live, as they typed.
The problem was that almost no one could explain what Wave actually was, or why they would use it instead of the tools they already had. It was invite-only at first, which built curiosity, but when Google opened it to the public in 2010, engagement was dismal. Users found it confusing, didn't know who to 'wave' at, and saw little reason to abandon email and chat for something that required everyone they knew to be on it too. The New York Times and others described it as a ghost town.
Google pulled the plug quickly. In August 2010 — barely 15 months after the standing ovation — Google announced it would stop developing Wave as a standalone product, citing low adoption. The technology was handed to the Apache Software Foundation, where it lingered as 'Apache Wave' before being discontinued in 2018. Wave became a byword for a brilliant demo that never became a product people wanted, and a reminder that a standing ovation at a launch event is not the same as a market.
Why it happened
- Wave tried to be everything at once — email, chat, wiki, docs — and ended up being hard to define and harder to explain.
- It required a network of other Wave users to be useful, but gave individuals little reason to switch from the tools they already had.
- The real-time, everything-in-one model was confusing; users didn't understand the use case or who to communicate with.
- Google mistook the excitement of a developer audience at a launch event for genuine mass-market demand.
The lesson
Wave merged email, chat, wikis and docs into one tool, and users couldn't tell what it was for — so they didn't use it. If you can't explain your product's job in one sentence, neither can they.
Aftermath
Google Wave is taught as a classic case of a product that was technically impressive but conceptually unclear — a tool nobody could explain and therefore nobody adopted. Some of its ideas (real-time collaboration, live editing) lived on in later products like Google Docs' collaboration features, but Wave itself failed. The lesson for product teams is sharp: if you can't describe the job your product does in one sentence, your users won't be able to either, and a thrilled developer audience at a keynote is not evidence of a market. Clarity of purpose beats brilliance of features.
Sources
spotted an error? The club wants to know.
Comments · 0
Sign in to join the comments.