Jump to content
Asked by jonjohns65
Posted Nov 12 2009 10:54 AM
I have a challenge that is unique (I think) and I don't know how to solve it.
I am currently collaborating with a partner in writing and creating content for a website. We rarely work in the same location.
We both write, and share things via e-mail, and chat programs. We both use twitter, both on myspace, and facebook. Both use Google Docs.
How can we collaborate by joining all these communication techniques into something that is more singularly manageable?
I find something on the internet from a link on twitter. I can direct message him with a retweet, but there is not enough room in a simple RT to expand on my ideas of how to utilize what I've found.
I can e-mail the link, and include the twitter source, and we can go back and forth with e-mail replies, but then if later I have a thought, and instant message him about it, the 'thread' to the original e-mail and link, is broken, and now I have to somehow reply to the original e-mail with the thought and discussion I had in the instant message, duplicating the work.
For a creative writing team, thoughts are the most valuable thing, and the half life of a thought is frighteningly short. Unless a team of folks work in physical close proximity, how are they supposed to communicate instantly, or relatively so, and keep trains of thought tied together, as well as separate from one another?
Is Google Wave the solution?
Build a man a fire, he'll be warm for the night. Set a man on fire, he'll be warm the rest of his life.
Answered by aferrate
Posted Nov 12 2009 07:51 PM
I believe that Google Wave is a viable solution for your collaboration challenge, especially as you are already familiar with many of the elements that are integrated into Google Wave (email, IM, wiki, online documents, and conversation threads).
In the context of your workflow and collaboration activities, Google Wave can be viewed as an online document that captures conversations, along with media and attachments. Each wave not only serves as an archive of your conversation (and its respective threads), but it also serves as a central repository for files, images/graphics, and bookmarks/links.
Using the example you provided about finding tweets with interesting links and then sharing them with your colleagues, I think the case can be made for creating a new wave for each link/topic/theme that you want to discuss with your colleagues. Using Google Wave, you won't have to worry about lost email threads or the temporary nature of instant messages. All of the communication back and forth will be available as a document that encapsulates replies. The conversation itself can be treated as a wiki, so that you can revisit a 'blip' (message) from a while back and either edit it with updated information or add a reply with additional commentary.
One of the things that I have found quite valuable about using Google Wave's threaded conversation model instead of email is that media and attachments are added inline with each blip (in email, they are simply appended to the entire message/thread). That means that the attachment has a greater sense of context, as it is displayed where it was added as the conversation evolved. In fact, a blip that contains an image could be replied to with "child" blips that refer to that specific image.
Lastly, although we are at the early stages of Google Wave, it's likely that it increasingly will be integrated with other platforms such as Twitter and Facebook, making it seamless (or almost seamless) to exchange information between each platform. We are already starting to see extensions for Google Wave that do just that.
I recommend that you conduct a test run with Google Wave, thinking of the wave more as more than just an email thread or IM console. You can send me a message if you don't have a Google Wave account, and I'll be happy to pass on a few invites.
Comment by bearpaws : Feb 05 2010 06:30 AM
I agree. Google Wave is the way to go. I know of others, but Google has all the tools you'll need.