Slide Demo
1 / 10

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

  • Uploaded on

Slide Demo Epilogue Systems The problem we solve. Why do users of critical software applications feel like this?. 2. Enterprise Application Success.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Slide Demo Epilogue Systems The problem we solve' - aimee

An Image/Link below is provided (as is) to download presentation

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.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Slide demo epilogue systems the problem we solve

Slide Demo

Epilogue Systems

The problem we solve

Enterprise application success
Enterprise Application Success this?

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, Neochange , Technology Services Industry Association, 2008


Slide demo epilogue systems the problem we solve

Learning and Retention this?

  • 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 …


Maslow s hierarchy of needs for effective user adoption

Software’s this?

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)


Slide demo epilogue systems the problem we solve

What use to take days … this?


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

Very Complex

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


Epilogue approach to end user enablement
Epilogue Approach this?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


Slide demo epilogue systems the problem we solve

Epilogue Impact this?

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?


Built for the size of the problem
Built for the this?SIZE of the Problem

THANK YOU for more information