addressing many of the coordination issues I’ve encountered.

As I look forward, there are any number of roles where I can see G.Wave being used. One, may be as the manager facilitating project collaboration among multiple organizations, working toward a common goal. Second, may be as a consultant with multiple projects. In each case, it is necessary to interlace discussions in IM (multiple clients), phone calls, graphics, email, and documentation in other forms.

Like it or not, today our communication takes place in myriad forms, across multiple mediums, and is increasingly transparent. As a result, my key pain as a manager has often been governing change management. The solution is often an artificial construct (e.g. ECO process) forcing collaboration’s natural flow into a rigid form. G.Wave, Wave.G, whatever its long term nickname will be, provides a very fluid way of supporting a disciplined culture of collaboration. In support of this, an entire industry surrounding how to even -use- G.Wave is foreseeable.

One component of G.Wave I’ll continue monitoring, is integration with legacy solutions such as Outlook and its (or other) contact manager solutions. It will take time, no matter how popular, for G.Wave to overtake de facto standards like Outlook so fluid integration will be a necessity for Google to support adoption.

If Google gets it right, this is going to be exciting!