Requirements
Social Business Community Wiki
Deployment of Enterprise 2.0 solutions requires an understanding of the organization’s business and system requirements. The requirements may change over time based on lessons learned, and it’s often recommended to do a lean and agile deployment of E2.0.
Functionality
Many organizations look at Andrew McAfee’s SLATES or Dion Hinchcliffe’s FLATNESSES framework to identify required E2.0 functionality. The social aspect is often an important component of E2.0 with staff learning from each other, but also the collective wisdom of the crowd. This wisdom of the crowd can be harnessed for search, allowing recommendations, user tagging, links, etc. to rank search results.
McAfee’s recommends that the software must be easy to use and not impose any rigid structure for users. The roll-out should be informal, but on a common platform to enable future collaboration between areas.
Technologies
There are a number of Enterprise 2.0 technologies available. A few vendors offer platforms while many vendors offer one or more components of an Enterprise 2.0 environment. Many organizations have implemented blogs to improve communication, and wikis to improve collaboration.
Microsoft’s SharePoint has gotten a lot of attention the last few years, and many organizations are looking at using the SharePoint platform for social computing. Google also offer a number of Enterprise solutions, and emerging technologies like GoogleWave may change how we currently use email.
Social media sites such as FaceBook, Wikipedia, and YouTube are also driving business to Enterprise 2.0. There are also benefits of also using tools like Twitter for business usage, but we need more use cases that document the business benefits of different E2.0 technologies.
Roadmap
The requirements can be used to create a roadmap for Enterprise 2.0, which acts as the bridge between the strategy and the implementation phases.
