I think that the biggest risk is of waves becoming too long, with many levels of nested comments, so that it’s hard to glean pertinent information. That perhaps implies the need for someone “in charge” of a wave, to split wave it before that happens, which is not quite in the egalitarian spirit of the tool.

Overall, I’m enjoying trying Wave, but am not yet convinced that it’s better than a wiki.

I use it for gathering specs, user interface discussions and peer reviews.

The problem I have with Wave is not the tool – but people’s reluctance to embrace it.

‘Why change?’
‘What’s wrong with the way we always do it?’

For some, it’s too complex, others like their current setup, and others don’t like it because you found it first… so they won’t play ball. That the way it goes.

Google has also added BUZZ to Gmail, i.e. integrated Google Reader to your Gmail. Pretty slick

And, blatant self-promotion…

Using Google Wave to Write Technical Documents

http://www.ihearttechnicalwriting.com/tools/using-google-wave-to-write-technical-documents/4184/

we look at six different ways to do this.

Ivan

Also, not to sure how revealing that would be but happy to try.