http://blog.actionbase.com/asynchrony-vs-real-time-for-human-processes?utm_source=rss&utm_medium=rss&utm_campaign=asynchrony-vs-real-time-for-human-processes Pondering Human Process Management Wed, 01 Sep 2010 07:17:58 +0300 http://wordpress.org/?v=2.8.6 hourly 1 http://blog.actionbase.com/asynchrony-vs-real-time-for-human-processes/comment-page-1#comment-417 Jacob Ukelson Wed, 09 Sep 2009 12:33:37 +0000 http://blog.actionbase.com/?p=120#comment-417 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. 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.

]]> http://blog.actionbase.com/asynchrony-vs-real-time-for-human-processes/comment-page-1#comment-416 Jonathan Barel Mon, 07 Sep 2009 13:40:31 +0000 http://blog.actionbase.com/?p=120#comment-416 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. 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.

]]>