Actionable and Adoptable Adoption

While focusing on a user centric solution for most is a very different way of thinking, outside of the broke fix methodology most businesses utilize. Technology can be used in many different fashions, we can replicate processes to become more efficient, utilize powerful API's to aggregate data from disparate systems or legacy applications or merge old with new to create cutting edge systems that streamline the overall business infrastructure. However, most organizations fail to see past the "what it will do" example; many only look at the how as opposed to whom. Who will be using these applications, what departments will also benefit from the launch and how can you create an adoption plan that both articulates the importance but also guides users to understand technology with limited training or resources?


Design your solutions from with a user centric or user driven purpose. As opposed to focusing on how the technology will be built focus your efforts on how the technology can be designed to replicate existing user interactions. Understand how the user experience affects the day to day lives of your workers. While most see design and aesthetics as an additional expense, one that can reduce the total cost of ownership, long term it can be devastating to your investment. Here is a real scenario I walked in a few months back, a certain telecom company located here in Seattle, spent $345,000 for an initial launch of SharePoint 2007 with many tools and departmental platforms attached. In the early stages of discussions, I had advised them that design must be incorporated to reflect the experience of the solution and enable employees to rapidly adopt the technology in to their everyday lives, this, was 11 months ago and; they did not see it as being a driving factor for them to roll out an effective solution.

The goal, 2,300 employee’s companywide utilizing SharePoint for infrastructure and operational purposes.

The end result, 20-30 employees a week logging on and using it for document management after a 6 month period. The solution, we were able to apply the initial design, user experience and interface a top their existing platform to help drive adoption.

After a companywide re launch, 5 months later, our daily log count is well over 2,100 employees daily. The spend you ask, 25% of the initial solution. Now, does it make sense to take action on adoption if it will make you technology adoptable? It is financially irresponsible to say no...