Since the success or failure of any social software solution is a direct result of its adoption rate, it is critical that you have absolute confidence in adoption before you begin. There are plenty of examples of failed social software projects. Why did they fail? Because they were not embraced by users.
While certain strategies encourage faster adoption, adoption is not something that can be mandated. Adoption occurs when users decide for themselves that the solution provides them with a net benefit. It happens when users want to use the product. Users very quickly weigh “what’s in it for me?” against any perceived pain, such as giving up the comfort of an old way of doing something.
A short list of the 5 product capabilities most critical to adoption success is outlined in our separate whitepaper, “The 5 Most Critical Requirements for Enterprise Social Software.”
This paper assumes the social software you choose has this short list of product capabilities and is therefore “highly adoptable.” The purpose of this companion paper is to outline a carefully planned roll-out process for social software; one that will generate the fastest adoption across your enterprise.