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!
ICT Role in 21st Century Education & its Challenges.pptx
Designing Applications that CARE
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.
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
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
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