I have been too busy this month to follow the Enterprise 2.0 discussions thoroughly. But I’m sharing here the blog posts that made the most buzz on my twitter streamline. Enjoy!
I’ll start with an interesting white paper, a production of the 2.0 adoption Council which describes the state of enterprise 2.0 adoption accordingly to budgets, challenges, business drivers, teams and leadership.
The major discussion that reigned this last month was: Pilot or No pilot?
It all started (or shall I say re-started) at the end of April, when A. McAfee’s asked to “Drop The Pilot”. He thinks “these kinds of pilots are unintentionally set up to fail…because they contain too few people, most of whom know each other too well.”
The discussion stirred afterwards and here is a list of posts who dealt with the same question:
If Enterprise 2.0 was totally here, Andrew’s point would have been absolutely on the target and any pilots would not have been representative of critical mass needed to trigger and prove the exponential dynamics of interaction evident in online community . But, in my view, Enterprise 2.0 is not exclusively serendipity.
That’s why I believe broadly discarding pilots as useless or not effective towards large-scale adoption may introduce major drawbacks.
I think broad deployment across an organization can also lead to chaos if not done properly. Now having said that I think there is merit and justification for both but the corporate culture can play a huge role in deciding which approach to take. There is more to E2.0 than the serendipity effect.
If your pilot is genuinely experimental, then go for it. If you are trying to win support or investment to go further, then design a proof of concept that is broad enough to show real results, but shallow enough to be quick, cheap and under the radar.
I recently ran across an organization that is planning an interesting approach to introducing an enterprise social networking platform. They are considering kicking off their social networking initiative with a company wide Jam to determine the greatest business value for social for their organization. I like this approach for three main reasons:
· It calibrates the broad organization to working in a social environment
· It has a focus on business value
· It provides your initial roadmap
The second round of posts I enjoyed reading was about sharing. The first post comes with some goodies. Oscar Berg actually shares some interesting articles that are definitely worth the check out.
To improve information sharing with the use of Enterprise 2.0 technologies, we first need to understand the psychology of sharing. We also need to understand the context in which we want people to start sharing with each other.
Sharing is something that comes naturally to people — we want to help each other. Indeed sharing is at the top of the list in All I Ever Needed to Know I Learned in Kindergarten.
E2.0 technologies and approaches will allow for the natural working and sharing tendencies of people to emerge and return the critical balance needed not just for sustainable survival but for productive striving (another great s-word).
Others articles that draw attention this last month:
- What Enterprise 2.0 means for the CIO and IT department
- Can Enterprise 2.0 Adoptions Learn Anything from ERP Implementations?
- How to tell when Enterprise 2.0 is not appropriate for your organization
- Enterprise 2.0 – Towards Embracing a New Emerging Kind of Leadership