This post was written by Jacob Ukelson September 7th, 2009

asynchrony vs. real-time for human processes

Google wave received a lot of attention for its incorporation of real-time in email – which makes a lot of sense for  conversations and discussions among friends. Intuitively, it seemed a lot less valuable from an enterprise perspective. I was trying to figure out why when I came upon this paper by Erik Brynjolfsson from MIT. He was looking at the productivity of knowledge workers that used a database and email for thier work. Lots of interesting data in the paper but for me the bottom line is: “On average, workers using more asynchronous email and database tools handle substantially more projects simultaneously. In contrast, traditional synchronous communication modes such as phone calls correlate with less multitasking“. His research shows that multitasking is the key to knowledge worker productivity.

Bottom line, tools that make email a more effective multi-tasking tool for processes can have a big effect on knowledge worker productivity.

Share:
  • Sphinn
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • LinkedIn
  • Netvibes
  • Tumblr
  • E-mail this story to a friend!
  • Twitter

2 Responses to “asynchrony vs. real-time for human processes”

  • So, if I understand correctly, the synchronous aspect of Google Wave inhibits productivity?
    But Google Wave isn’t inherently synchronous OR asynchronous. It simply has the capacity for either.

    Jonathan Barel, September 7th, 2009 at 4:40 pm

  • I believe the right way to think about it is that real-time messaging (as in Google Wave) is a cute feature, but not a big a deal, especially in a business setting.
    As anyone who works with email in a business setting knows, asynchronous communication has its benefits – one of them being increased productivity for human processes.

    Jacob Ukelson, September 9th, 2009 at 3:33 pm

Leave a Reply