I would echo a lot of other reviews: it's too complex and ambitious. This applies to the protocol/platform as well as their initial client. There's just so much going on and it's trying to do so much at once that it's very unwieldy.
I think simplicity is an important feature if you want new software to gain traction, and especially if you want new protocols to be adopted. I think simpler tools like http://shoptalkapp.com (disclosure: co-founder) do a better job of solving the problem you describe. And the tools we use to build it, which are gradually being open sourced at http://dieselweb.org, make real-time web apps pretty accessible to developers.
Having used the wave client and read about the protocol, I just think both are too complex to really gain traction. All the bugs in Gooogle's own wave client are evidence that it's not an easy platform to write apps on, at least at this point. I'm sure they'll continue to pour tons of resources into it, and maybe they'll turn it around. Time will tell.
Being marketed as "It can do everything!!! It's the new internet!", which seems to be the current strategy, could pay off, but maybe not. Likely only with geeks wanting to play with technology.
I'd be really surprised if it takes off with consumers quite yet.
Unlike Google Wave, MooGroups is available now, being improved upon everyday, doesn't require any signup, and allows you to use any email system.
If you have to coordinate communication and collaboration among any group of people, Wave will help. Though if it's only 2, 5 or 10 people, it's more likely you can get everyone to agree on convention and get by with older tools.
Perhaps they thought they had to differentiate from message boards or IM or email or IRC?
Wave seems almost obvious except that it wasn't invented earlier.
I could be missing something though, is Wave something you can install locally and have control over? It's not Google's style so I'd guess not.
If I'm mistaken, I'm more than willing to be enlightened.
If it's not obvious to you what problem it solves, then you've spent too long away from corporate environments with their massive, unwieldy threads of emails flying about, full mailboxes, and other email issues.
The problem that Wave solves is blindingly obvious to anyone who uses email as a primary tool to work with teams. Whether it's the right solution is another question altogether, but the problem is definitely there.