A lot of what is talked about in Enterprise2.0 adoption has to do with capturing, sharing and exchanging knowledge. But, once those needs are fulfilled: What do we use this knowledge for?, How do we work the knowledge into the workflow? or more specifically, How do we process this knowledge in order to create a competitive advantage within our businesses?
If we plan on using Enterprise2.0 as a new technology, what outcomes are anticipated?
Do we create better products?
Do we institute new and move advances processes?
Do we undertake better practices?
It is my opinion that Enterprise2.0 practitioners must consider not only getting people to use the technologies but have a clear vision of how the company will reap the benefits of the introduction. In considering an Enterprise2.0 adoption, do not look at just the technology, or at the initial condition, but at the state of the company 5 years after the introduction.
Hi Kevin,
I normally look at it backward-forwards :
1. what are the benefits we want to achieve
2. which knowledge is needed for this
3. how do we collect-share-reuse
--> vision before use !!
Posted by: marnix | July 01, 2008 at 04:39 AM
Hi Marnix.
Yes, it is really an open loop and a design issue. I look at it from a systems engineering perspective.
What do you need or want to accomplish?
What are the work elements or framework that make up the task
What requirements arise from the work elements?
How do the tools support and satisfy the requirements.
Then, design, deploy, test, and see if you accomplish what you wanted.
In short, tie execution strategy to business goals -- a point well made in the book "Making Strategy Work". One good aspect of the book is the numerous examples of how companies failed in their efforts by not placing "vision before use"
Posted by: Kevin Shea | July 01, 2008 at 09:29 AM