Thoughts on Google Wave

So when I got my invite for Google Wave, I couldn't register fast enough. Like a lot of people, I've been waiting for the developer's curtain to be pulled back and reveal a new era in remote collaborative communication.

Well, I have been to the Wave, and can now report back on what I've been seeing.

While the platform itself hasn't disappointed, the anticipation I had before getting on board has been replaced with anticipation of the day when it will be opened up to the thundering masses.

Google Wave seems a natural fit for copywriters, art directors, strategists, UX folks and designers: It empowers us to share and work together in an autonomous space with video, images, text and pretty much any kind of file you'd need to. In real time. And like I said, the functionality and tools of Wave have not disappointed. I just need to have more projects to work on with people that require this space to open up for us, because the people I work with are (for the most part) shouting distance from me right now.

Perhaps that will be the change Google Wave brings about in the end—an opening up of when and where collaboration can and does take place. Which would be pretty sweet. I've only investigated and worked with Wave on professional projects, so it will be interesting to see what kind of social spaces it opens up once it gets fully launched. In the meantime, I've started some simulated projects/Waves with a few people just to test the waters and isolate/recognize certain pitfalls, opportunities or detours it creates.

As we began dipping our toes in it, the whole entity felt like a glorified wiki or messageboard. But the momentum grew with each one we opened. And the potential is there for that day when we need to brainstorm or develop a project and we all find ourselves in different time zones. THAT'S when the Wave will really earn its wings.

All that said, here are a few things I've learned so far about working with/within Wave:

1. keep it focused: the more focused the wave/project you're on, the better the results. Not a huge revelation, but as badly as a "real-world" brainstorm or ideation can go off track when not properly focused, it's even worse when a virtual one goes off track.

2. keep it simple (at first): it's a new technology and a new space to work within, but don't get too fancy with what you bring to the wave. Get comfortable sharing and editing the materials in basic arenas you've already mastered before you launch an elaborate mission-critical project with a lot of moving parts on Wave. The more comfortable you and your team get with Wave and all the goodies it features, the more complex your collaborations can/will become.

3. keep it friendly: goes without saying that you should play nice in whatever sandbox you're playing in, but you'll find the occasions for snarky and/or biting commentary are multiple when working in a Wave, but best left unrealized. One thing that will surely result from Wave? An entirely new etiquette and set of ground rules for engagement.

4. keep it in the family: as some of my colleagues and I have been messing around with Wave, we've found that collaboration on a given Wave is only as strong as its weakest link. Some people find it more challenging than others to work within it, so as you're getting your feet wet, either keep your group members on a Wave only to people with a less-steep learning/comfort curve, or don't let yourself get frustrated by a more challenged person on the list.

5. keep pushing it: every time you initiate a new one, you'll find the collective mentality and ability within your team rises to a new level with Wave. And it should. As I've said, comfort is gained and new spaces can open up within a Wave--with greater potential each time. So don't get too comfortable and just stay in a zone that's "good enough". Keep pushing it or you and your team will almost certainly be leaving the potential of this tool/platform untapped.