Transition Strategies for Enterprise 2.0 Adoption is also about I

In the middle of transition we can see the I. Transitions are about me on a personal and professional level. And indeed, if we use levels, humbleness is always on its place.

Found at

Posted by Sandy Kemsley
Wednesday, June 24, 2009
1:37 PM

At this week’s Enterprise 2.0 Conference in Boston, Lee Bryant of Headshift looked at the adoption challenges for 2.0 technologies in companies that have grown up around a centralized model of IT, particularly for the second wave adopters required to move Enterprise 2.0 into the mainstream within an organization. He points out that we can’t afford the high-friction, high-cost model of deploying technology and processes, but need to rebalance the role of people within the enterprise.

External tools are subject to evolutionary forces and either adapt or die quickly, whereas we are forced to put up with Paleolithic-era tools inside the enterprise because it’s a captive market. 21st century enterprises, however, aren’t putting up with that: they’re going outside and getting the best possible tools for their uses on demand, rather than waiting for IT to provide a second-rate solution, months or years later.

There is a shift from individual productivity to network productivity, that measures the improvements that occur because we’re doing things together and connected rather than as individuals. If everyone in the company has common goals, then there’s a big boost in productivity when people work together.

There’s a need to make hidden data visible and use it to drive collective intelligence — I see this all the time with the need for enterprise search and content management for static content, but also enterprise micro-blogging and other conversations that surface more transient ideas for consumption.

This post is recommended for you  Deloitte's 2016 global mobile consumer survey: US edition (download possible)

It’s all about improving processes and reducing the cost of doing business, although not necessarily in the structured BPM style of process improvement; instead, it’s about using social tools to change how people can collaborate and work together. This might include adding a social layer to existing tools, such as we see when collaboration is added to ECM and BPM but moving beyond that.


Reblog this post [with Zemanta]