How is Google Wave intended to be used in a way that I can't use Google Docs for? It seems like it's Google Docs, except they've integrated the chat and the actual document.
|
show 2 more comments
feedback
|
closed as off topic by alex, quack quixote, Diago Feb 7 '10 at 9:25
Questions on Super User are expected to generally relate to computer software or computer hardware, within the scope defined in the faq.
|
It's really hard to answer your question, because Google Wave is not the same as Google Docs. Problem is, if you are determined to think of it as such, you just end up using it like a bad version of Google Docs. There are people claiming it's just a bad IM client as well. They have probably ended up using it as a bad version of an IM client. Well, guess what, it isn't an IM client either. The point is, it's a new system. Google Wave is not Google Docs, it's not a wiki, it's not email, it's not MSN Messenger, ICQ, or any other IM either. And it's not a blog, or a web forum. Nor is it an USENET news group. Admittedly, it's easy to mistake as such, since it incorporates features from all of the above. Yet, it's not even just a bloated integration of the above - it is it's own communication system that just has many similarities to existing tools. But since you asked for differences from Google Docs, here are some:
Now the use cases specific to Wave are a bit more difficult - Google Docs, like many tools, can probably be used for most cases. Even email can be used for collaborative editing, but it's a real pain. I would argue that the best cases for Wave is communication where there isn't a specific task at hand. If you need to build an information base, use Wiki. If you need to create a book, use Google Docs. But if you need to communicate before doing anything, use Wave. | ||||
|
feedback
|
|
One way I use Google Wave with my friends is to organize events. This allows us to collaboratively decide on all the details of the trip and becomes a useful reference refer back to. Having it as a structured document means that it's easy to highlight the important details while hiding the parts of the document that descend into chatter. The other particular useful part about wave for this use case is that since it's a single document which you can easily invite people to follow, you never have the issue of accidentally dropping people off the recipient list, which is a risk with each reply-all to an email thread. This has happened to us a couple of times, with people being dropped off the email thread without anyone realizing until it's a bit late. Related to the last point, it's much easier to quickly get up to speed on the contents of an existing wave than an existing email thread as you can ignore entire branches that are clearly not relevant and you can use the replay feature to see the order in which people responded and added new information. | |||||
feedback
|
|
For private use, such as when planning an event, or discussing a topic, Wave bring the functionality of Google Docs plus live chat plus easier change tracking plus gadgets. For public use (use with:public in the search box, and see), Wave is far more powerful than the other tools, as it brings the best of Wikis, Blogs, Forums and Discussion groups. The easy editing, easy tagging, real time chat, search capabilities, etc. makes the difference. There are some issues where Wave isn't the best replacement, especially when it comes to permission management (cannot really remove people from waves) and integration with other products. Give it some time, as the technology is still in preview. | ||||
|
feedback
|

will bebecause the invitation process is slow and it takes time to get enough people (friends, business associates, etc.) to actually start a collaboration process. I just started last month to actually get enough business associates invited to use Google Wave effectively. – ricbax Dec 2 '09 at 4:50