This document discusses the importance of user experience and usability testing in website design. It defines usability as how easy user interfaces are to use, and notes there are five key components: learnability, efficiency, memorability, errors, and satisfaction. Early and frequent user testing is recommended to fix issues, test assumptions, and inform the design process. Examples of tasks and questions to use during testing are provided. The benefits of testing with real users and focusing on important fixes rather than minor issues are also outlined.

1. User Experience MattersSo let’s test and play!

2. The people we design sites forhttp://www.youtube.com/watch?v=o4MwTvtyrUQ

3. Definition of Usability*Usability is a quality attribute that assesses how easy user interfaces are to use.The word "usability" also refers to methods for improving ease-of-use during the design process.* JakobNeilsen

4. Usability: Defined by5 quality components*: Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design? Efficiency: Once users have learned the design, how quickly can they perform tasks? Memorability: When users return to the design after a period of not using it, how easily can they reestablish proficiency? Errors: How many errors do users make, how severe are these errors, and how easily can they recover from the errors? Satisfaction: How pleasant is it to use the design? * JakobNeilsen

5. Utility, a key quality attributeUtility:which refers to the design's functionality:Does it do what users need?Usability and utility are equally important: Easy yet not what you wantWhat you want but hard to get

6. Not a good sign

7. User Testing for Usability

8. The Benefits of User TestingFix it earlyTest assumptionsProvide objectivity and solve the opinion issueInform the design processSet Key Performance Indicators (KPI)Budget, budget, budget

9. Steve Krug… my virtual mentor“do-it-yourself” usability testingWhat kind of people--and how many--to test (Steve’s motto: Recruit loosely, and grade on a curve)What to test, and when to test itHow to facilitate--when to listen and when to probeHow to decide what to fixOnce a month, half a day, debrief over lunch

10. When to testEarly and often!Napkin TestDesign mock upsPrototypeLive site (rebuild)

11. www.openinterface.ie

12. How to testOne person per sessionScreencast (audio) One at a timeHave the user talk out loudEnsure file of tools and content is readyUse tools: http://sensible.comScripts, forms, consent forms

13. Example TaskProvide the opportunity for the user to figure out what to do: Bad: Post a jobGood: You are a business owner and wish to hire talent within the local technology community. Find a way to do this.

14. Example QuestionsAsk about the site, not for their opinion: Bad: Do you like this?, What do you think of this?Good: What do you think this is? What would you do next?Stay neutral and away from leading questions

15. What to fix*Ignore what Steve calls – The Kayak ProblemsResist the temptation to add thingsTake new features with a grain of saltTake the low hanging fruit* Steve Krug

16. Simple Tricks for Drupal UXCustom menuNormal names Relational/suggestive contentExpanded help textWeb forms - less is moreCalls to actionUSER TESTING – early & often!!

17. Stuff to knowUsertesting.comMust reads if you build, design or manage websites: Don’t Make Me Think – Steve KrugRocket Surgery Made Easy – Steve KrugThe Elements of User Experience – Jesse James Garrett

18. Case Study: www.lethbridgecollege.ca