WHY DO APPLICATIONS FAIL? It is either: a. They solve the wrong problem. b. They have the wrong features for the right problem. More Importantly - They make the right features too complicated to use or understand. Paradigm Shift: Designers are NOT Users Developers are NOT Users Systems must be easy-to-learn andeasy-to-use to get TOTAL USER SATISFACTION!

1. A P P S T H A T
C A R E
KiranBudhrani
Feb 13, 2009

2. What do I need to do first?
Where do I click next?
What do I do now?
Im LOST!
Help!

3. WHY DO APPLICATIONS FAIL?
They solve the wrong problem.
They have the wrong features for
the right problem.
They make the right features
too complicated to use or understand.

4. Paradigm Shift
Designers are NOT
Users
Developers are NOT
Users

5. Designing the Workflow
Effective
Efficient

6. Effective vs. Efficient
• Effective
– The right processes are defined
• Efficient
– Doing processes right

7. Designing the Workflow
Effective
Efficient
Developing the application
Useful
Usable

8. Useful vs. Usable
• Useful
– Allows users to “do” things by providing the
tools needed to perform specific tasks.
– It works!
• Usable
– Allows users to “do” things they need to do
easily

9. Systems must be
easy-to-learn
and
easy-to-use

10. USER
SATISFACTION
(happy farmers)


11. YES!
People WILL LEAVE if…
they cant find what they need
the application is unclear
navigation is difficult

12. In e-commerce,
if users cannot find a
product, they will not
buy it.

13. Get to know the
USER PERSONA
Remove the
“we’ll, it works for me!”

14. Use the power of
RICH-MEDIA to provide
interaction and spark
interest

15. Provide system
feedback as often as
needed
• Lightboxes or Error Messages
• Real-time Checks
• Progress Bar
• Provide Default Values
• Remember Information

16. Communicate with the
right visual elements.

17. Arrange information so
that it is easy to read
and understand.
Talk to the User

18. If possible, allow users to
customize what they need
and when they need it.

19. Conduct Usability Tests
to make your application
“idiot-proof”
• Get user-representatives (at least 5)
• Ask them to perform the tasks
• Observe

20. Don’t ask users what
they want or prefer,
watch them USE the
application.

21. Review Good Examples
See what works and what
doesn’t

22. Usability Test Variations
• Individual Usability
– Impact on individual operations and
functions
• Group Usability
– Impact on a group workflow
• Enterprise Usability
– Impact over time in the company

23. Why bother?
• Productivity
– Users spend time getting work done
rather than figuring out how how to
do what they need to do
• Usage and Adoption
– Users opt to use the new system
rather than stick to the older
methods
– Users wont go looking for other
options

24. Why bother?
• Support and Training Cost
– Users will be able to accomplish
their tasks with less training and
support, saving time (and money)
for both the organization
• Development Time and Cost
– Users will be able to
communicated what they need
and what they will use

25. Again, its all about
A P P S T H A T
C A R E