UPDATE: the link below to the “10 Persistent…” is a slide show. I prefer the text version and the accompanying writeup. I think you will too. Here is a sample:
In your average corporate environment, though, this happens all the time. People work on documents, presentations, etc. They have lengthy discussions over email. Pieces of work bounce back and forth across one or multiple organisations for weeks before they’re finalised. People are brought on to the conversation late in the day. Attachments get lost. Inboxes fill up and emails bounce. It’s a major pain.
So what are the problems with email in a corporate environment, and what does Wave do to address them?
Looking at wave? I am.
Here we have reported 10 Persistent Messaging Problems that Google Wave Solves and 5 Google wave use cases.
I’d like to try this on a project or part of a project. What about you?