31 May 2009
Google Wave (and) the next big thing
Google announced it’s new service Wave. You can see the key-note here.
For sure it’s a great set of services and many blogs and news sites are really excited about it. I have no doubts that it will for sure bring social media and communications to the next level. It’s a milestone in human communication efficiency.
However, I think Google missed one really big aspect of it, it may have been a conscious decision or it may have been the lack of understanding of the largest portion of corporate communication.
Basically I’m making a distinction here between collaborative communication and transactional communication. Collaborative communication are things were constant interaction increases the value of a piece of work. This is mainly true in a very creative and innovaive environment. New concepts, new business models, innovative ideas all immesly benefit from collaboration.
Transactional communication instead is used on a huge amount of business processes, where a pretty certain amount of defined steps need to be taken to get to an end result (i. e. wiring money from one account to another or creating a defined dashboard report).
Google’s Wave will be an amazing tool for coolaborative communication. Againl, it’s going to bring this type of interaction to new heights and with that will provide tremendous value to the world.
But then there is still a huge lack of support for transactional communication and equally to what Google said in the key-note it’s true that we use the same, old tools to process transactions. Here’s where we’ve gone down the route to use email for a large portion of transactional communication, a big mistake, and one that’s costing us billions of dollars.
So, let me give you an example: some manager wants his team to update a project dashboard. What happens? He sends an email to the team. He’s using a tool that is completely free-form to request something very specific. Would it not be better if the request in and of-itself was a very specific work request asking to fill a specific piece of information.
I know there are workflow applications and transactional database systems, but my point is that still largely requests and answers that should be very specific are not (see the idea of Wolfram’s Alpha search engine, same thought?).
I think the next big thing in computer technology is going to be a system that rethinks how to do email for transactional communication. For sure this would be a killer-app for enterprises. I’ll give it a go at http://publicprocess.org whenever I’ll get to it.