Download to read offline
Uploaded byDesignHammer
Get It Right the First Time Through Cheap and Easy DIY Usability Testing - Drupal Camp Asheville 2015
The document discusses diy usability testing techniques and tools, emphasizing the importance of testing early and often to improve website usability. It defines usability, outlines different types of tests, and provides examples of tools for conducting usability tests, user testing, and gathering analytics. The session aims to equip attendees with practical methods for evaluating and enhancing their websites without requiring extensive expertise.
More Related Content
Similar to Get It Right the First Time Through Cheap and Easy DIY Usability Testing - Drupal Camp Asheville 2015
Get It Right the First Time Through Cheap and Easy DIY Usability Testing - Drupal Camp Asheville 2015
- 1. Get It Rightthe FirstTime Through Cheap and Easy DIY Usability Testing Saturday,August 15th Drupal Camp Asheville 2015 ! Stephen Pashby @DH_Stephen @DesignHammer 1
- 2. Overview • Introduction • Whatis Usability • Who,What,Where, and When • Free and/or Inexpensive Tools 2
- 3.
- 4. Disclaimer Let’s get thisout of the way first! 4
- 5. Disclaimer I am nota Usability expert • I’ll share easy DIY techniques & tools I won’t tell you how to fix your website • But I will point you in the right direction 5
- 6. Scope What I’ll coverand what I won’t. 6
- 7. What we willcover • What is usability? • Why should I bother? • How can I test my site? • How do I keep my site usable? 7
- 8. What we won’tcover • Usability best practices • Statistical analysis of results • Every type of usability test 8
- 9.
- 10. What is usability? “Usabilitytesting refers to evaluating a product or service by testing it with representative users.The goal is to identify any usability problems, collect qualitative and quantitative data and determine the participant's satisfaction with the product.” usability.gov 10
- 11. What is usability? “Ifthere's one thing you learn by working on a lot of different Web sites, it's that almost any design idea—no matter how appallingly bad— can be made usable in the right circumstances, with enough effort.” Steve Krug, author Don't Make MeThink: A Common Sense Approach toWeb Usability 11
- 12. Keep in mind •Popular≠Good • Attractive≠Usable • Ugly≠Unusable 12
- 13. What, when, and whoto test? 13
- 14. What to test? Anythingor everything? 14
- 15. What should youtest? • Information Architecture • Navigation • User Interface elements • New Functionality • Critical User Interactions • Everything! 15
- 16. When to test? Isit too soon, or too late? 16
- 17. When to test •The sooner the better • Tests should be part of any change process • Test early and test often! 17
- 18. Who to test? Youropinion probably isn’t the one that matters. 18
- 19. Potential test subjects •Actual site users • Representative site users • Crowdsourced • Artificial intelligence 19
- 20. Actual site users Pros: •Most relevant to site Cons: • May have limited availability • May already have learned “work arounds” • May require compensation 20
- 21. Representative users Pros: • Relevantto site • Usually new to the site Cons: • Only as relevant as your recruiting • May require compensation 21
- 22. Crowdsourced Pros: • Readily available •Usually new to the site Cons: • May not closely model actual site users • Generally fee based 22
- 23. Artificial intelligence Pros: • Readilyavailable • Complete tests in real time Cons: • May not closely model actual human users 23
- 24. Which is rightfor you? • What kind of site are you testing? • What is your site’s demographic? • What access do you have to site users? 24
- 25.
- 26. Types of tests Onesize does not fit all! 26
- 27. Formative Tests • Usedthroughout the change process. • Support tool for decision making. • Different tools for different stages. 27
- 28. Summative Tests • GenerallyQA testing. • Determine if finished feature/site is usable. • Confirm improved usability. • Also used prior to making changes to determine and document any usability problems. 28
- 29. Types of testing •Analytics • User Testing • Usability Testing 29
- 30. Analytics • Measure ofactual user behavior. • May suggest usability problems. • Not a substitute for usability testing. • May provide baseline to measure success of plans derived from usability testing. 30
- 31. User Testing • Basedon user opinion. • Not tied to specific task completion. • Can provide insight into users desires or expectations. 31
- 32. Usability testing • Basedon task completion. • Usually measurable. 32
- 33. Analytics It takes timeto collect data; start today! 33
- 34. Web Analytics Formative • Recordsactual site visitor interaction. • Can suggest usability problems. 34
- 35. Web Analytics Possible tools •Google Analytics (Google) • WebTrends Analytics (WebTrends) • AWStats (AWStats) 35
- 36. Heat Maps Formative • Recordsspecific actual site visitor interaction: mouse click and scroll depth. • Can suggest usability problems. 36
- 37. Heat Maps Possible tools •Crazy Egg (Crazy Egg) • Hotjar (Hotjar) • Lucky Orange (Lucky Orange) • Google Analytics* (Google) *sort of 37
- 38. User testing Opinions arelike noses, everyone’s got one. 38
- 39. User Surveys Formative • Askusers what they like or don’t like. • Good starting point for refining or adding new features. 39
- 40. User Surveys Possible tools •Paper • SurveyMonkey (SurveyMonkey) • SurveyGizmo (Widgix) • Qualtrics (Qualtrics) 40
- 41. A/B & MultivariateTests Formative • Users are randomly given an implementation. • Determine which implementation is most effective based on conversion rates. 41
- 42. A/B & MultivariateTests Possible tools • GoogleWebsite Optimizer (Google) • CMS Specific tools (e.g. Drupal Multivariate) • Optimizely (Optimizely) 42
- 43. Usability testing Choose thetest based on your question. 43
- 44. Open Card Sort Formative •Participants organize a list of items into categories they provide. 44
- 45. Open Card Sort Possibletools • Index cards • Cardsort (Optimal Workshop) • UserZoom (UserZoom) 45
- 46. Closed Card Sort Formative •Participants organize a list of items into categories you provide. 46
- 47. Closed Card Sort Possibletools • Index cards • Cardsort (Optimal Workshop) • UserZoom (UserZoom) 47
- 48. Tree Test Formative • Askstest participants where they would go to find specific content. • Tests the organization of content if navigation labels make sense to users • Test website’s pre-defined navigation. 48
- 49. Tree Test Possible tools •Index cards • Treejack (Optimal Workshop) 49
- 50. Expectancy Test Formative • Testsa user’s impressions of an early prototype of the interface. • Typically paper prototype, wireframes, or design concepts. 50
- 51. Expectancy Test Possible tools •Paper Prototype • Wireframes • Design Concepts 51
- 52. 5-Second Usability Test Formative •Tests individual pages (not homepage) for a specific scenario and task. • Not suitable for testing complex systems or user interaction. 52
- 53. 5-Second Usability Test Possibletools • Paper Prototype • Wireframes • Design Concepts • FiveSecondTest (UsabilityHub) 53
- 54. Visual Affordance Test Formative •Tests the “Clickability/Tappability.” • Show subject web page or design concept. • Subject indicate every item believed clickable, and items believed not clickable. 54
- 55. Visual Affordance Test Possibletools • Paper Prototype • Wireframes • Design Concepts 55
- 56. Click Test Summative • Providescenario and task. • User clicks on the design element to complete task. 56
- 57. Click Test Possible tools •Paper Prototype • Wireframes • Design Concepts • Chalkmark (Optimal Workshop) • Flippa (UsabilityHub) 57
- 58. Sample-of-One Test Summative • Documentfundamental errors in interface layout, labels, content organization, affordance, and functionality • Use single subject who fits main persona. 58
- 59. Sample-of-One Test Possible tools •Silverback (Clearleft) • OpenHallway (OpenHallway) • TryMyUI (TryMyUI) • UXRecorder (Foraker Labs) - Mobile 59
- 60. Performance Test Formative orSummative • Can be to look for problems in existing site or confirm function in a new site. • Provide participants a task with a scenario • Observe user interact with website. 60
- 61. Performance Test Possible tools •Silverback (Clearleft) • OpenHallway (OpenHallway) • TryMyUI (TryMyUI) • UXRecorder (Foraker Labs) - Mobile 61
- 62. Free Exploration Test Summative •Observe users interaction with website for set period of time (5 minutes?). • Use when navigation is no longer an issue. 62
- 63. Free Exploration Test Possibletools • Silverback (Clearleft) • OpenHallway (OpenHallway) • TryMyUI (TryMyUI) • UXRecorder (Foraker Labs) - Mobile 63
- 64.
- 65. Survey Monkey Likes: • Robustquestion functionality & reporting. • Filter response data by response or URL. • Data export to allow manipulation in excel. Be Aware: • Some features require more pricey plans. 65
- 66.
- 67.
- 68.
- 69.
- 70.
- 71.
- 72.
- 73. CrazyEgg Likes: • Variety ofways to filter/visual data • Can test mobile and desktop Be Aware: • Not real time. • Not cheap to monitor entire sites. 73
- 74.
- 75.
- 76.
- 77.
- 78.
- 79.
- 80.
- 81.
- 82.
- 83.
- 84. Optimal Sort Likes: • Easyto set up. • Can use for remote testing. Be Aware: • Normalizing data requires assumptions. • Not cheap if you need the full version. 84
- 85.
- 86.
- 87.
- 88.
- 89.
- 90.
- 91. Treejack Likes: • Easy toset up. • Can use for remote testing. Be Aware: • Not cheap if you need the full version. 91
- 92.
- 93.
- 94.
- 95.
- 96.
- 97. Chalkmark Likes: • Easy toset up. • Can use for remote testing. Be Aware: • Only single response per question. • Not cheap if you need the full version. 97
- 98.
- 99.
- 100.
- 101.
- 102. Silverback Likes: • Portable, workswell on a standard laptop. • Does not require a dedicated usability lab. Be Aware: • Mac only. • For on location testing. 102
- 103.
- 104.
- 105. Conclusion • No silverbullet to make sites usable. • Usability is a never-ending process. • Making sites more usable is fun for all! 105
- 106.