Slide Demo Epilogue Systems The problem we solve. Why do users of critical software applications feel like this?. 2. Enterprise Application Success.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
The problem we solve
Effective user adoption is key to achieving software ROI … yet most organizations don’t have the time or resourcesto effectively educate employees on a new technology.
50% of polled entities who’ve deployed ERP solutions have realized 50% or less of the projected benefits from their system.
(Panorama Consulting, 2012)
Defining Enterprise Software Success
SandHill.com, Neochange , Technology Services Industry Association, 2008
Effective User Adoption Hierarchy
Self Actualization (morality, creativity, problem solving, spontaneity, lack of prejudice)
Strategy Level (understanding what systems strategies are likely to lead to organizational success)
Operational Entity Level (understanding what tactical execution is needed to achieve the systems strategies)
Esteem Needs (self-esteem, confidence, respect achievement, etc.)
Functional Level (understanding how to execute functional tactics to contribute to success at the operational entity level)
Social Needs (friends, family, intimacy)
Process Level (understanding what systems processes are required to execute the tactics by functional level)
Safety Needs (shelter, work, family, health)
Transaction Level (understanding what basic systems building blocks, the transactions, will provide the most fundamental execution)
Physiological Needs (breathing, eating, sleeping)
5-10 decision points and dependencies.
= 1 hour to create
1-5 decision points and dependences.
= 30 min to create
10--20 decision point and dependencies.
= 2 hours to create
20+ decision points and dependencies.
= 4 hours to create
No decision points or dependencies.
= 5-15 min to create
The Normal Distribution curve of transaction complexity
50-90% reduction in documentation cost
30-50% reduction in training
20-40% reduction in helpdesk calls
What is your impact of effective user adoption?