What I do:

  • I actually help companies implement and execute the adoption, introduction and institutionalization of collaborative technologies. In doing this work, I innovate, create and stimulate, ... and when necessary agitate! I spend a lot of time making sure that things are integrated; systems, processes, information flows... It bugs me when technology is introduced that dis-integrates systems, processes, etc. I use a lot of the fundamental principles of "lean execution" to support my work.

Interesting people

  • Larry Cannell
    I met Larry when I was working as a consultant to the automotive firm he was with. We had the same vision for how business could leverage collaboration. Larry is a broad thinker and a good guy to exchange ideas with.
  • Michael Sampson
    Michael is an industry analyst focused on the shared spaces market -- team workspaces, portal-based interfaces, presence & availability, wireless collaboration, and real-time interaction. I like him because he doesn't just follow the crowd.

Interesting Articles by others

In Black and White series

« Enterprise2.0 Adoption models | Main | Enterprise2.0 Adoption - Getting Management Support »

July 18, 2008

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00e55255ac69883300e553c45c578834

Listed below are links to weblogs that reference Institutionalizing Enterprise2.0:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Yao

Kvein,

I think there contexts where SIP and MIP play different roles. For idea generation and innovation diffusion, SIP is better as there is very little predefined for ideas and converstation about ideas to happen. For process execution, MIP might better as it can keep all relevant infromation and people in context for tasks at hand. If you have strong search and tagging across MIP, the difference tends to deminish.

The history of web tell us that we usually start with MIP and each of the information islands get increasing connected overtime. Then some kind of super structures (meta-structure) will emerge...

Kevin Shea

Yao

I agree that different models should be applied to different situations, different companies. There are companies whose business goals and culture are based on innovation, such as biotech, others who are commodity oriented, such as metal fabricators, and still others that are more government like.

I believe that each company must evaluate the execution model and decide which is most appropriate for them. That is, link the model to the type of business. And, in some, it could be that a hybrid may be best. I think we agree that one size doesn’t fit all.

If the connections, interaction and interfaces are known at the initiation of a project, then it is my opinion that those connections should be accounted for in any framework, as part of the system design. Then, one can either encourage interaction or wait for users to determine the need. Some connections are more well know than others since they are integral to work processes. However, the new technologies offer potential to create new or reinvigorate old connections, and these should be encouraged.

I have written in the past and hold to my opinion that the business value of emergent collaboration and Enterprise2.0 is in providing means to improve and optimize interaction and interfaces (the connections)

Kevin

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Who reads this blog

  • Folks who read this blog are interested in: systems engineering, issues of execution and adoption, how technology can satisfy business processes, creating a sustainable plan, assuring that solutions are well integrated, improving communications, and getting stuff done.

My blogging style

  • I prefer to provide blog content as a continuous stream of information on a topic. I like to stay focused on an idea for a while, rather than pop all over the place. Feel free to join in.

Current Topics and Ideas

  • What I am writing about now: Systems Engineering  Information Flow Networks Knowledge Management  Presentations  Work Processes  Enterprise 2.0 Adoption

Future topics

  • Topics that I am interested in:  Integration  Managing interactions  Visualization of flow networks  Business Analytics