This is the third in our series on enterprise implementation issues (see - Overcoming Adoption Barriers for Enterprise 2.0 Initiatives – Part One - Enterprise 2.0 Conference Discussion). In Six Steps to Company-Wide Adoption, Michael Idinopulos, from our business partner, Socialtext, begins with the excellent observation that a year ago, the focus was on individual technologies (wikis, blogs, RSS, etc.) and now we are seeing more comprehensive solutions that integrate multiple technologies into unified platforms for enterprise interactions. This is true for Socialtext 3.0 but also a number of other vendors in the enterprise 2.0 space, validating the Socialtext move.
Michael follows the opportunities opening up with this move as we are also seeing a shift in implementation approaches. With more individual technologies, companies were conducting pilots with individual teams or departments. Now companies are evaluating the more comprehensive solutions for enterprise-wide deployment. So this changes the nature of adoption barriers. Michael provides us with six things to consider when implementing at an enterprise scale. These six steps are consistent with what we discussed in our first two posts in this series but many of them add new material.
Michael begins with the need for a broad range of use cases. Across the enterprise, “different groups will find value in different ways: finding experts, managing projects, surfacing ideas from the field, communicating to staff, building social communities, monitoring competitors, staying in constant contact with customers, etc.” Michael says to encourage diversity to touch as many needs as possible, while looking for common patterns.
He adds the importance of hands-on experiences for new users and the related suggestion to route repeated activities through the new tools. One way to do this is to integrate the new social software with existing legacy systems. He also suggests setting up public communities through the new tools to allow people to share their insights and excitement gained through these hands on experiences. Like any software implementation it is also important to find and support champions of the new tools and new ways of doing things. These are all useful suggestions. Next, I will be turning to the insights found in Enterprise 2.0 Implementation by Aaron Newman and Jeremy Thomas.
