Slide Demo Epilogue Systems The problem we solve - PowerPoint PPT Presentation

slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Slide Demo Epilogue Systems The problem we solve PowerPoint Presentation
Download Presentation
Slide Demo Epilogue Systems The problem we solve

play fullscreen
1 / 10
Slide Demo Epilogue Systems The problem we solve
113 Views
Download Presentation
aimee
Download Presentation

Slide Demo Epilogue Systems The problem we solve

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Slide Demo Epilogue Systems The problem we solve

  2. Why do users of critical software applications feel like this? 2

  3. Enterprise Application Success 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. (Gartner, 2010) 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 3

  4. Learning and Retention • Most learning professionals would agree the highest learning retention occurs when the need is real and the learning is part of doing • Software routinely fails to deliver support in this fashion and when it does, it’s usually not what’s needed, isn’t correct, and is hard to find • Why? A bad starting point … 4

  5. Software’s Maslow’s Hierarchy of Needs(for effective user adoption) Maslow’s Hierarchy 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

  6. Complete Platform for Software Documentation 6

  7. What use to take days … Normal 5-10 decision points and dependencies. = 1 hour to create Nominal 1-5 decision points and dependences. = 30 min to create Complicated 10--20 decision point and dependencies. = 2 hours to create Very Complex 20+ decision points and dependencies. = 4 hours to create None No decision points or dependencies. = 5-15 min to create The Normal Distribution curve of transaction complexity 7

  8. Epilogue Approach to end-user enablement • Give users access to Every Possible Scenario • Make it Effortless and delivered in Real-Time • Only Relevant and Specificcontent in a Variety of outputs • Allow Testingand Measurement with the ability for Feedback and Improvement 8

  9. Epilogue Impact 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? 9

  10. Built for the SIZE of the Problem THANK YOU info@epiloguesystems.com for more information 10