The problems with adoption of current solutions (wikis, hosted stuff like Basecamp) are that many corporations don't let you host proprietary data offsite, and adding another server is something that is so difficult as to be essentially impossible. Not to mention "another server" could be one of 50 alternatives, all incompatible.
There still will adoption issues, as it doesn't seem like Google is aggressive in pursuing business customers, and I don't know if they have good answers for the questions that will come up. But I see Wave as essentially a protocol designed to solve the same sorts of problems as Basecamp et. al.
But I think the best example is a customer support ticketing system. This is pretty much an attempt to record email conversations in a structured way and be able to attach files to them.
It also provides a single point of integration. In the past, I've advocated for e.g. bulletin boards to replace email exchanges where information tends to "submarine" into private exchanges. But getting corporate IS to even consider a deployment -- even just a small one for a single team -- was a non-starter. Going rogue would be a termination offense.
If you can get Wave adopted, you solve a whole bunch of problems all at once.
I remain extremely skeptical, though, about the compatibility of Wave as it currently exists with many businesses' requirements for both confidentiality and guaranteed information access -- uptime, an unlimited timeframe into to future, and not becoming locked in to a single vendor platform to the extent that Wave currently seems to imply. A Wave failure on any of these points could quickly destroy a business; so much would be locked up in its data, and if there is no alternative -- even if imperfect -- means of access...