Like other users who have had access to Google Wave for the past 8-10 months, I was impressed by Google’s technology — and frustrated by my inability to use it effectively.
Wave, Google’s innovative web application for real-time communication and collaboration, was a collaborative silo. This is why, on August 4, 2010, Google announced the suspension of Wave development: “Wave has not seen the user adoption we would have liked. We don’t plan to continue developing Wave as a standalone product, but we will maintain the site at least through the end of the year and extend the technology for use in other Google projects.”
The collaborative tools of Wave were fierce… It bundled email, instant messaging, threaded conversations and rich media as “waves of content” to be shared with others. Wave updates were available in real-time — and historically via playback in chronological order. Any participant of a wave could reply anywhere within the message, edit any part of the wave, and add participants at any point in the process.
However, the distribution model for Wave was flawed. it was only released to 100,000 developers as a preview. Thereafter — until May, 2010 — it was only available by special request or invitation. As a result, people who obtained Google’s collaboration tool had few people to collaborate with.
Google’s distribution model based on ‘exclusivity’ was a poorly-chose approach for a collaboration tool.
Meet Doctor Wave
Product manager Greg, a.k.a. Dr. Wave, gives an introduction to Google Wave and points out parts of the user interface. (Note: This is meant to be viewed inside Google Wave.)

