Usability & Usability Testing


Published on

AWDP Session 4

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Usability & Usability Testing

  1. 1. Web Usability &Usability Testing<br />Elaine Brennan<br />
  2. 2. Web Usability?<br />First law of web usability:<br />‘Don’t make me think!’<br />Steve Krug<br />
  3. 3. Consistent identity<br />logo or site ID<br />name<br />tagline<br />
  4. 4. Navigation<br />
  5. 5. Types of pages<br />the homepage<br />pathway pages<br />information pages<br />
  6. 6. The homepage<br /><ul><li>identify the site
  7. 7. set tone and personality
  8. 8. make clear what the site is about
  9. 9. help people start tasks immediately
  10. 10. direct them efficiently to what they want</li></li></ul><li>Pathway pages<br />get people to what they’re looking for<br />like a table of contents<br />create a smooth path which doesn’t:<br /> make people think<br /> have to use the Back button<br />most people choose the first plausible looking option: satisficing<br />
  11. 11. Information pages<br />destination pages <br />where users scan and get their information<br />
  12. 12. Page layout<br />clear visual hierarchy<br />break pages into clearly defined areas<br />make it obvious what’s clickable<br />keep down the noise<br />
  13. 13. Usability testing <br />Usability testing helps you find out how well your website is working.<br />
  14. 14. Doing a usability test<br />You carry out a usability test by:<br />watching and listening as one user at a time <br />responds to your site<br />tries to find specific information<br />tries to accomplish specific tasks with the website <br />recording the results<br />discussing results with your web team<br />making changes accordingly <br />testing again!<br />
  15. 15. What Steve Krug knows:<br />If you want a great site, you’ve got to test.<br />Testing one user is 100 percent better than testing none.<br />Testing one user early in the project is better than testing 50 near the end.<br />The importance of recruiting representative users is overrated.<br />The point of testing is not to prove or disprove something. It’s to inform your judgement.<br />Testing is an iterative process.<br />Nothing beats a live audience reaction.<br />
  16. 16. How many users to test?<br />Krug advises 3 or 4 will pick up nearly all of the most significant problems<br />
  17. 17. Who to recruit?<br />‘it doesn’t much matter who you test’ as:<br />We’re all beginners under the skin.<br />It’s usually not a good idea to design a site so that only our target audience can use it.<br />Experts are rarely insulted by something that is clear enough for beginners.<br />
  18. 18.  Where and how to test?<br />
  19. 19. Who, what, when?<br /> Who should do the testing?<br />Who should observe?<br />What do you test, and when?<br />
  20. 20. Types of live-site test<br />‘Get it’ testing<br />Key task testing<br />
  21. 21. Let’s usability test!<br />Let’s have a go at doing a quick set of ‘Get it’ tests<br />