enterprise 2.0 adoption models

Kevin SheaKevinshea.typepad.com

1Part of the “In Black and White” series

Adoption Models for Enterprise 2.0

In Black and White

There are at least three (3) different

models for Enterprise 2.0 adoption

Generally, only two (2) are talked about

The Standard Model

Hierarchical Top-down Information flow

Generally considered a “forced-on” approach, in which,

organizational controls manage the introduction

Bottoms up, Grass roots model.

In which, a good idea is typically spread through the efforts of a

single early adopter.

Desired by most practitioners.

And, the most talked about….

The grass roots model is often called the emergence model.

Let’s call it the single initiation point model

“SIP model”

Arises from a single point

Now….. since “a good idea has many fathers”

Solutions can arise from many locations

Creating a “MIP model” of adoption

The Multiple Initiation Point (MIP) Model

Bottom up, Grass roots, informational flow.

In which, similar ideas are spawned simultaneously across a wide audience

What can happen in a MIP Model?

A dispersed global unit can have the idea

Individual divisional units or units with less capable communication skills can come up with

the same idea, in isolation.

If a MIP model is left unchecked, it can lead to

A dispersed global unit can have the idea

Individual divisional units or units with less favorable communication skills can come up with

the idea.

Siloing

Competing solutions, information segmentation, confusion

Which solution is the “right” one?

History shows that the MIP model contributes to problems in collaboration software installations that end up as

“messy”/“file share only” solutions.

Which model would most likely occur at your company?

A MIP model requires some controls or guidance to succeed.

Growth needs to be coordinated.

So, there are at least three(3) different models

for Enterprise 2.0 adoption

Standard

Single Initiation Point

Multiple Initiation Point

If you expect growth to occur as a result of an organically arising SIP model,

You don’t at least plan to respond to a MIP scenario

Your execution strategy is in jeopdary.

For a more detailed explanation and insight into the changing nature of Knowledge Management, visit my blog at http://kevinshea.typepad.com/

Other item in my In Black and White series.

• Enterprise2.0: a Simple Explanation in Black and Whitehttp://kevinshea.typepad.com/kevin_shea_process_collab/2008/06/enterprise-20-a.html

• Knowledge Management in Black and White

http://www.slideshare.net/kevinshea/knowledge-management-in-black-and-white/

enterprise 2.0 adoption models

mip model of adoption

emergence model

grass roots model

standard model hierarchical

single point

good idea

mip scenario

adoption models

Documents

potential of enterprise 2.0 (emakina academy #8 : enterprise...

web 2.0 enterprise 2.0 intro

enterprise technology adoption services

enterprise 2.0-the-benefits-and-challenges-of-adoption

intranet, web 2.0, enterprise 2.0

catn - enterprise devops adoption

enterprise cloud adoption strategies

emc enterprise 2.0 case study webinar for the 2.0 adoption...

office 2.0 / enterprise 2.0

2.0 adoption in the enterprise - the after

enterprise 2.0 black belt workshop: business case, planning,...

เทคโนโลยี2.0{web 2.0, library 2.0,...

enterprise 2.0 black belt workshop: community roles &...

enterprise api adoption patterns

2.0 adoption in the enterprise - the before

ypobo - enterprise devops adoption

enterprise 2.0 = knowledge management 2.0?

hospital adoption of medicine 2.0

web 2.0, enterprise 2.0, bi 2.0…

web 2.0 / enterprise 2.0