In Part 1 and Part 2 of this series, we touched on the need for thoroughly planning out an application adoption strategy and some of the key tactics for a successful rollout. This last post will focus on additional considerations for application adoption.
Historically, many IT organizations have focused on costs, maintaining system health and keeping a stranglehold on their environments so users cannot stray outside of provided resources and domains that are sanctioned. Today, things are a lot messier.
Each IT organization must look for a synergy between themselves and the lines of business if they want to stay relevant. Moreover, IT budgets are continually growing tighter, so working with the lines of business for joint funding can be a way to get more done without increasing the budget for IT spend.
Another consideration for your adoption plan is that not every group or application needs every possible option. We have found that some customers just need some additional training for their end users for one application, while usage reports and basic communications and marketing is good for another. Still others may require the full boat, including deep business process analysis and customized use-case-based training.
Further Adoption Considerations
Here are five factors to look at when determining how much time, energy and budget to spend on an adoption campaign:
1. Investment in the Actual Application
If the investment is large, a comprehensive adoption plan provides added insurance that the company will realize the full potential of the application.
2. Expected Outcomes from the Use of the Application
Is the business relying on this application making a significant impact on the organization? An adoption plan that takes into account the measurements that matter should be included to make sure that the goals are met.
3. Complexity of the Application
Will your users need extra help getting up to speed to use all the features of the new application?
4. The Application Is Replacing Another with a Similar Purpose
When switching applications, there is typically a productivity decline because users must become accustomed to the changes in their workflows. Taking the time to focus on an adoption plan that shows the users how their old workflows map to their new workflows will help keep this to a minimum.
5. Users’ Level of Experience with the New Application
Do most users already have some experience with the application? It may seem that an adoption plan is not needed in this case, but realize that not all users are in the same boat. At the very least, an adoption program that focuses on communication and champion programs that give instruction on how the users can get assistance from others in their area would help things to go smoothly.