A   P   P   S       T       H   A       T

        C   A   R       E

                            KiranBudhrani
          ...
What do I need to do first?
 Where do I click next?
  What do I do now?
        Im LOST!
          Help!
WHY DO APPLICATIONS FAIL?

   They solve the wrong problem.
  They have the wrong features for
          the right problem...
Paradigm Shift

Designers are NOT
      Users
Developers are NOT
      Users
Designing the Workflow
       Effective
       Efficient
Effective vs. Efficient
• Effective
  – The right processes are defined
• Efficient
  – Doing processes right
Designing the Workflow
        Effective
        Efficient
Developing the application
         Useful
         Usable
Useful vs. Usable
• Useful
  – Allows users to “do” things by providing the
    tools needed to perform specific tasks.
  ...
Systems must be
  easy-to-learn
      and
   easy-to-use
USER
SATISFACTION
  (happy farmers)

       
YES!
People WILL LEAVE if…
  they cant find what they need
    the application is unclear
      navigation is difficult
In e-commerce,
if users cannot find a
product, they will not
         buy it.
Get to know the
USER PERSONA
       Remove the
 “we’ll, it works for me!”
Use the power of
RICH-MEDIA to provide
 interaction and spark
        interest
Provide system
feedback as often as
      needed
  •   Lightboxes or Error Messages
  •   Real-time Checks
  •   Progress ...
Communicate with the
 right visual elements.
Arrange information so
 that it is easy to read
   and understand.
       Talk to the User
If possible, allow users to
customize what they need
  and when they need it.
Conduct Usability Tests
to make your application
     “idiot-proof”
   •   Get user-representatives (at least 5)
   •   As...
Don’t ask users what
they want or prefer,
watch them USE the
    application.
Review Good Examples

   See what works and what
           doesn’t
Usability Test Variations
• Individual Usability
  – Impact on individual operations and
    functions
• Group Usability
 ...
Why bother?
• Productivity
  – Users spend time getting work done
    rather than figuring out how how to
    do what they...
Why bother?
• Support and Training Cost
  – Users will be able to accomplish
    their tasks with less training and
    su...
Again, its all about
A   P   P   S       T       H   A   T

        C   A   R       E
Upcoming SlideShare
Loading in …5
×

Designing Applications that CARE

643 views
587 views

Published on

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 and easy-to-use to get TOTAL USER SATISFACTION!

Published in: Education, Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
643
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Designing Applications that CARE

  1. 1. A P P S T H A T C A R E KiranBudhrani Feb 13, 2009
  2. 2. What do I need to do first? Where do I click next? What do I do now? Im LOST! Help!
  3. 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. 4. Paradigm Shift Designers are NOT Users Developers are NOT Users
  5. 5. Designing the Workflow Effective Efficient
  6. 6. Effective vs. Efficient • Effective – The right processes are defined • Efficient – Doing processes right
  7. 7. Designing the Workflow Effective Efficient Developing the application Useful Usable
  8. 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. 9. Systems must be easy-to-learn and easy-to-use
  10. 10. USER SATISFACTION (happy farmers) 
  11. 11. YES! People WILL LEAVE if… they cant find what they need the application is unclear navigation is difficult
  12. 12. In e-commerce, if users cannot find a product, they will not buy it.
  13. 13. Get to know the USER PERSONA Remove the “we’ll, it works for me!”
  14. 14. Use the power of RICH-MEDIA to provide interaction and spark interest
  15. 15. Provide system feedback as often as needed • Lightboxes or Error Messages • Real-time Checks • Progress Bar • Provide Default Values • Remember Information
  16. 16. Communicate with the right visual elements.
  17. 17. Arrange information so that it is easy to read and understand. Talk to the User
  18. 18. If possible, allow users to customize what they need and when they need it.
  19. 19. Conduct Usability Tests to make your application “idiot-proof” • Get user-representatives (at least 5) • Ask them to perform the tasks • Observe
  20. 20. Don’t ask users what they want or prefer, watch them USE the application.
  21. 21. Review Good Examples See what works and what doesn’t
  22. 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. 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. 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. 25. Again, its all about A P P S T H A T C A R E

×