Building successful user experiences often requires an intervention. Understanding common user interface mistakes and examples of good design can help developers and make their applications more usable. We'll look at a set of principles and practises to help developers to build better, more engaging user experiences for software and web applications.

3. $yourName

4. Hi! My name is $yourName , and I have a Usability Problem.

5. We write BAD code. But we do GREAT design.

6. 1• Admit You Have a Problem You are powerless to design GOOD usability alone and the user experience of your software has become unmanageable.

8. Know thy User.

10. 2• Believe in a Power greater than yourselves (and we don't mean Jakob Nielsen)

11. David Verba, Adaptive Path • RWE 2007: Practical Design for Developers

14. Citizens Police City Homeless Police City Citizens Homeless Priority

15. 3• All this could be yours Make a decision to recognize the value of GOOD design.

16. http://mac.blorge.com

17. “Design is not just what it looks like and feels like. Design is how it works .” — Steve Jobs

18. 4• Make a searching and fearless inventory of your user experience shortcomings.

19. Opportunity Matrix Value Cost Effectivness

20. Stick Figures 101 Dave Gray, XPLANE http://communicationnation.blogspot.com/2005/12/visual-thinking-practice-draw-stick.html

22. 5• Admit to yourselves, and to another human being, the nature of your problems.

23. “ The definition of insanity is doing the same thing over and over and expecting different results.” — Albert Einstein

24. Talk to your users!

25. 6• Be entirely ready to remove these defects of character.

30. Of the top 10 feature requests, 5 had been in Office for more than a release.

32. 7• Ask for help! It's out there.

37. 8• Make a list of all users you've harmed, and then make their lives better.

38. Focused on Tasks (Products, Features) Objective/Quantifiable Focused on Experiences (People, Activities, Contexts) Subjective/Qualitative

39. 9• Made direct amends. Make direct amends to people wherever possible, except when to do so would injure them or others.

40. http://www.bumfonline.com/images/BurningBridges.jpg

41. 10• Continue to take a personal inventory and when you are wrong, promptly admit to it.

42. Iterative Practitioner Observe Analyze Design

43. Observe Analyze Solve Know thy User Prototype to find possible Solutions Prototype to flesh out a Solution

45. 11• Without users, it doesn’t matter. We’re building things for people. No people = no things.

47. 12• Pay it Forward Having had an awakening as a result of these steps, try to carry the message to other developers and to practice these principles in any projects you're involved with.

49. Thanks!