Segmented Communication is Good

By Deane Barker on October 15, 2009

The Google Wave chatting tool is too complicated for its own good : This is what kinda bothers me about Google Wave.

The trouble is, everything you type into Wave is transmitted live, in real time—every keystroke was getting sent to Zach just as I hit it. This made me too self-conscious to get my thoughts across.

I think segmentation is good in conversations.  You talk, then I’ll talk, then you talk again.  I like how email has set this up.  It works.

What people are bantering about as the big “deficiency” with email that Wave will supposedly fix really doesn’t strike me as a problem.

On the other hand is a fairly well-reasoned argument from Daniel Tenner:

I believe that people who don’t see what Google Wave is for are simply looking at it from the wrong angle. Wave is not a social tool. It’s not Twitter, it’s not GTalk, it’s not Facebook. It was never designed to appeal to the crowds of geeks who are currently trying it out.

Wave is built for the corporate environment. It’s a tool for getting work done. And as far as those go, it’s an excellent tool, even at this very early stage.

In it, he lists a bunch of problems that Wave is supposed to solve and how it does so.  Worth reading.



  1. Can’t you turn off the real-time echoing of your keystrokes? If I recall correctly, the initial video released by Google about Wave said that it was optional.

Comments are closed. If you have something you really want to say, tweet @gadgetopia.