« Barriers to Enterprise 2.0 Adoption |
Main
| Enterprise 2.0 Blueprint »
May 20, 2008
Visual Model of Enterprise 2.0 Barriers
Yesterday, I took
my list of barriers and provided a few examples in each area. I have added a
few more and switched things around a tad. More importantly, I asked myself
what is the impact of the barriers on the eventual success of the
implementation.
Clearly, nothing
much is going to happen until you get the infrastructure in place but the impact
of overcoming the technology barriers is relatively low. However, like shooting
a rocket into space, you need a lot of energy just to get the momentum going.
So I don't want to short change the technology barriers but you will spend a lot
of energy and resources with little to show for the effort.
The second area, which focuses on the implementation barriers, is where the major integration
takes place. Here is where you can see that investments in your business model,
education, training, and marketing leverage the technology success. The
business model wasn’t included in the prior post but the basic idea is utilizing
self-service, consulting, and integration into a value-add framework.
The final area,
which seems to get most of the press, is the organizational barriers. I am
still under the belief that if you nail the first two then this area will take
care of itself. From this model, you could summarize that overcoming the
technical and organizational barriers will deliver the 20% while overcoming the implementation
barriers will deliver 80% of your success.
Posted by Todd at May 20, 2008 1:49 PM
Trackback Pings
TrackBack URL for this entry:
http://www.rtodd.com/cgi-bin/mt/mt-tb.cgi/188
I'm not sure about the last area taking care of itself... unless the purpose of the middle bit (awareness, training etc) is specifically designed to create the right culture. Likewise, all the awareness in the world will not help if there is a political obstacle (such as a policy that prevents people from working with people outside of their immediate team, for example)
Posted by: Rob Gray at May 21, 2008 11:06 AM
Seems good for communicating with a traditional audience that looks at things from a top-down perspective, but may scare off experimentation with potentially viral or smaller, localized, remotely hosted applications that do not require so much modification of existing corporate infrastructure or processes.
Dennis D. McDonald
Alexandria, Virginia
http://www.ddmcd.com
Posted by: Dennis McDonald at May 21, 2008 11:12 AM
Post a comment
|
Home
About
Speaking
Publications
Portfolio
Patents
Projects
Blog
