Planning and Implementation

Social Business Community Wiki

There are many implementation methodologies, but many organizations have abandoned the traditional linear or waterfall approach in favor of an iterative approach called continuous implementation. They prefer to not seek perfection in any one pass, but start small with the system, with the people who are the early users of the system, and continue to build out from there. An open methodology for this is MIKE2.0 (Method for an Integrated Knowledge Environment).

Change-Management
Culture may support or hinder any types of change. Users need to see the business benefits and personal benefits of change, they need to be listened to, engaged, and have a role in the new environment. They need to be responsible and accountable for certain parts or use cases, and the organization needs both positive and negative incentives to change their way of working.

Top-down and Button-up
A successful implementation requires both bottom up adoption and emergent behaviors as well as have support from the top down. Top-down focuses more on the business needs of all users, and it’s tied to real business problems. Bottom-up means that users understand, and to some extent demand, new ways of working.

Managing the implementation
One of the key concepts of Web2.0 and E2.0 is to start small and build and expand on it as with agile and lean development. So don't spent too much time creating the perfect structure. The Mike 2.0 Implementation Methodology suggests an iterative, not linear, approach so that development is continuous with a starting goal as functioning technology.

Tools
There are specific enterprise 2.0 tools that you can start using today to accomplish your enterprise 2.0 goals; the Enterprise 2.0 Technology to Case Matrix provides a quick glance of which tool can work for various enterprise 2.0-type applications. Whether project management or capturing meeting agendas, an enterprise wiki can be used for multiple purposes; including using a wiki as a simple online database. Blogs can help in locating internal experts and SharePoint has multiple uses in the context of enterprise 2.0. Finally, 8-Reasons-Why-GoogleWave-May-or-May-Not-Kill-E-Mail may be a useful collaboration tool and perhaps a replacement for email.

Pilot
Always take into consideration what the sponsor wants. Start small and see how the organization can learn from the pilot phase. Correct things based on lessons learned, improve them, and then roll out. Set the priorities, make sure that the organization gets maximum return from very easy low hanging fruit: areas where people are already looking for improvement and/or willing to change the way they work.

Test the system constantly with real users attempting real tasks, to see if usability and overall business usefulness is happening, and remember to feed back what you learn into the next iteration of fixes, expanded functionality, or expanded #s of users.

Usability
Plan usability testing a part of your entire implementation process. Develop personas and scenarios, and do user interface mockups of work flow to understand before implementing any code that changes work flow exactly how the workflow might be improved and get feedback.

Pre-Rollout Checklist
Start the rollout by ensuring that the organization is ready to rollout E2.0. Before we begin to implement anything we have a pre-implementation checklist. These are the things that you should have that are complete, in position, documented and actually understood and agreed upon by the people involved in this project.