Using Google Wave in the Enterprise


When Google (s goog) launched Wave last year, it was immediately obvious that it would be useful for collaboration. What was less obvious, however, was whether it would be a good choice for enterprise-level collaboration. Google’s tool takes a simplistic approach; when it comes to managing teams and projects, bells and whistles can be reassuring.

Now, though, many businesses and organizations are using Google Wave as their main collaboration tool. While it hasn’t proven itself to be the perfect tool for every company, Google Wave is certainly a good option for many teams, especially those who don’t have a lot of opportunities to interact in person.

Google Wave in Action

Jared Goralnick, the founder of AwayFind, uses Google Wave to manage his distributed teams. Goralnick decided to use Wave because his teams need real-time collaboration: “I’ve used wikis and emails for a long time, and I still do use them. Wikis do a better job with creating multi-page hierarchies and generally are better at portraying the final product of content creation…but they fail at synchronous editing, and don’t work very well for discussions. And email will always fill a role with both its ubiquity and low-tech nature. But I needed something that was more real-time and did a better job capturing not just information but how information was created. Something where discussion could become a finished product without having to open up a Word document and switch gears into ‘Now I’m writing a final paper’ mode.”

Wave definitely has a different approach from many collaboration tools, if only because of its reliance on search to go back and look at past projects and information. It may not be able to handle every aspect of your collaboration process, but it is easy to team up with other tools. In Goralnick’s case, Google Wave’s key use is as a discussion tool: “We have numerous discussions in Wave. When discussions turn into specifications or other material we want to really hold onto, we embed it into our Trac (wiki) knowledgebase. Tagging it in Wave also helps us to find things later.”

The Key Function of Google Wave

For many teams, the clearest benefit of using Google Wave is ease and speed of communication. It can, of course, handle sharing files and other tasks. But discussion is where it shines: The simple ability to have a real-time conversation that you can search later is particularly useful.

It’s also important to see Google Wave within the contexts of the various other web applications Google offers. While as a standalone tool, Google Wave’s abilities can’t match those of Basecamp, for example, when you pair it with Google Apps for Business, it can become a complete enterprise-level solution. Wave also works well with other tools, as Goralnick notes: “Before, I used PBWorks, Basecamp, and Trac — three tools that didn’t talk to one another. Now I can embed my Waves on Trac!”

Are you using Google Wave in your business? How are you getting on with it?

Related GigaOM Pro content (sub. req.): Report: The Real-Time Enterprise



Google is starting to suck with this move.

Something this revolutionary should really be given a chance, and people/companies be given more time to figure it out. People at my company -an averagely conservative one I guess – just started to realize its benefits, others would just a need a bit more time. I’d say Wave was a major benefit of our company moving to GoogleApps (which just happened 2 months ago), even if it hasn’t been advertised by IT folks at all.

I found dynamic switching between different modes/frequency of conversation is a key benefit, and this has to be experienced to be appreciated… just like any new paradigm (I for one, need 2 more years before I can see the point of microblogging:)

Jeffrey Herr

Seems like this post is moot, as Google is dropping Wave…


Unfortunate timing of this post with Google’s just announced death of Wave.

I’m currently looking for a set of solutions combining DMS, collaboration tools and a way to share iterations of creative revisions for client review, and consolidate feedback to one place.


We have been experimenting with Wave ( within the Google Apps) for slightly more than a month. Some observations…

Great for fast responses within collaborating team members. Thus eliminating unnecessary emails being sent to and fro
It is a bit of a resource hog and when we start to upload files that colleagues are working on, the machine becomes unbearably slow.
Would prefer integration with other Apps applications like cal and docs for scheduling, iterative changes in documents.
It would be great to have have gtalk voice capability in case one wishes to switch to voice.
Google Sites specifically file cabinet integration could be made available. When one does upload a file, there is no real intimation of the type of file or where it is.
Search could also be improved.


Wave is an interesting technology of course. Enterprise ready? Hardly. Wave in its current iteration is a consumer offering. To be enterprise ready it requires robust security and integrated identity controls. Novell has an offering called Pulse in prerelease that integrates directly with Wave and provides similar services, but with complete and robust security.


We use Google Wave in every telco.
This is perfect for facilitating the log of the telco and some extensions really support making quick decisions.
Only drawback: the pdf export is not very good.


I use Wave everyday. I have over 200 active waves and I just started in May, 2010.

I used it to replace my case management software in my law office. Wave had numerous advantages: word searchable, tags, easy to make and quickly customizable templates, and playback.

The biggest thing, however, is that everyone in the office (five of us) all know what the other person is doing — immediately. We don’t duplicate work. We know what needs to be done and we get it done. This doesn’t involve difference in time zones, but twenty feet apart. Yes, it is great when I’m not in the office or in court, but it works equally well when we are all in relatively close proximity.

Yes, Google Wave seems to be this wide open platform, but the failure to tame it is because of a failure of imagination.

Jeff Lucas

I would be interested to know how do you integrate email, calendaring, billing, document management, etc. into your case management process using Wave?

arun kamath

I had forgotten that I had a wave account un till reading this post. Wave is too ahead of its time. Many don’t get it and hence it is of no use if you are using it alone.


What wave does really well is to manage the shift from async to sync communications, so when a cross-timezone team are collaborating
the communication can go from IM speed (when everyone is present) to email speed (when most are asleep), but stay in the same medium and remain searchable.

We’ve been working on a conference call gadget for googlewave, which extends those benefits to an audio conversation. It works so well I find conventional conference calls really annoying now.

Simon Mackie

Agreed, managing the shift from sync to async is something other tools can’t match — you normally need to use a combination of tools to get the same effect.


“Now, though, many businesses and organizations are using Google Wave as their main collaboration tool.”

You must be joking. What is many? 5,6, maybe 7? Google Wave is far away from enterprise. SMBs don’t use it. Occasionally SOHO users might. That’s it.

Comments are closed.