I used it on a number of large collaborative projects (usually design documentation in the several hundred page variety) that needed reams of documentation and

I used it on a number of large collaborative projects (usually design documentation in the several hundred page variety) that needed reams of documentation and extensive side-bar discussion. Prior to Wave we used collaboration systems like Google Groups. We'd break each project down into phases (and if necessary subphases) and create a Wave for each phase -- something like "Phase A:Secondary Requirements and Permutations". All of the assets for that phase would end up in the Wave with necessary meta-descriptions/discussions around each asset. As often as not the asset was just attached into the Wave, but we used a fair amount of links to Google Docs. The meta-discussions were usually descriptions of the asset, or directions/side-bar conversations between team members needed for coordination on that asset. After all the phases were complete, we'd make another wave for final review and synthesis of the phase sub-documents, with sidebar discussions until final deliverable document. The first Wave coordinated project we actually tried to fall back on Google Groups and email and it just made things messy and didn't really make sense. We bit the bullet on the second project and just did it all in Wave. You know what? The project ended up going stupid fast compared to a Groups/email solution. Instead of masses of junk filling up groups, and thousands of emails clogging up my mailbox (potentially getting lost in the masses of other email I get every day). Plus we got a nice historic record of everything for free. Essentially it took what would have been dozens or hundreds of hours of project coordination time and turned it to 0. It lubricated that aspect of the project coordination so my team could focus on just actually doing the project. (and also, we used Wave notifiers so we knew when there was an update).