Do-it-Yourself Usability Testing: an Introduction

3,079 views

Published on

Slides from webinar presented through the Arizona State Library on November 21st, 2013. Full webinar recording available: https://azlibrary.webex.com/cmp0306ld/webcomponents/docshow/docshow.do?siteurl=azlibrary&jvm=1.7.0_40&isJavaClient=true

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

  • Be the first to like this

No Downloads
Views
Total views
3,079
On SlideShare
0
From Embeds
0
Number of Embeds
1,466
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Do-it-Yourself Usability Testing: an Introduction

  1. 1. Arizona State Library, Archives and Public Records | Library Development | Nov. 21 st, 2013 Do-It-Yourself Usability Testing: An Introduction #diyux Rebecca Blakiston Associate Librarian University of Arizona @blakistonr
  2. 2. What to expect • Use chat for questions • 3 sections: 1. How to plan for usability testing 2. How to conduct a usability test 3. What to do with the results of a usability test • Will break for questions after each section
  3. 3. About Me • • • • Access services (’05-’07) SIRLS grad (’07) Instruction librarian (’08) Web product manager (’10)
  4. 4. University of Arizona Main Library
  5. 5. Users should always be part of the process.
  6. 6. Usability Testing
  7. 7. Small budget? No problem.
  8. 8. 1. Plan
  9. 9. Who am I and what am I trying to do on your website? Establish primary tasks.
  10. 10. Examples of tasks: • Find a specific book/ebook title • Find a book based on a topic • Find open hours • Find out how much printing costs • Request an interlibrary loan • Donate money • Donate books
  11. 11. Translate tasks into scenarios. Task Scenario Find a specific You want to see if the library ebook title has The Hunger Games that you can download to your Kindle. How would you find this out? Donate books You have books you would like to get rid of, and wonder if you can give them to the library. Find out how to do this.
  12. 12. Gather incentives.
  13. 13. Identify a facilitator and a note taker. I will lead the testing. I will take notes.
  14. 14. Pick a time.
  15. 15. Pick a place.
  16. 16. Questions?
  17. 17. 2. Test
  18. 18. Let’s do this!
  19. 19. Let them know it is for a good cause and it won’t take much time.
  20. 20. Introduce the test. • We want to improve the website. • You can’t do anything wrong. • Talk out loud, it will help us a lot..
  21. 21. Facilitate the test. Keep them talking. What are you thinking? What are you looking for?
  22. 22. Manage their emotions. Keep them happy. This is very helpful.
  23. 23. Know when to end the test.
  24. 24. Questions?
  25. 25. 3. Analyze
  26. 26. Don’t freak out. Don’t blame the user.
  27. 27. Debrief right afterwards.
  28. 28. What was he thinking? Why was he not successful? ?
  29. 29. Focus on the most serious problems.
  30. 30. Focus on the problems easiest to fix. What’s the smallest change we can make right now that will at least smooth over this problem for most people?
  31. 31. Calendar Calendar Event Calendar
  32. 32. Keyword Searching Tips
  33. 33. Test again.* Test Improve Improve Test *optional, sometimes
  34. 34. Keep an ongoing list of problems. 1. Users think the WorldCat Local search box will work like a site search. 2. Users don’t know what “WorldCat Local” means. 3. Users often go to “University Libraries” and click on the library location in this drop-down menu expecting to find everything related to that library on that page (when it’s actually a really simple page just listing some collection information and location information). 4. “How Do I” could mean anything and so users often go here but don’t find what they are looking for. Same with “Services A-Z” which could essentially be a list of everything on our website, the way users think about it. 5. Users don’t realize that the clock for “hours” is clickable. 6. Users don’t notice the “Search this site” link in the top right. 7. Users almost always fail when trying to find Video streaming – when they succeed, they find it indirectly in Services A-Z, not where it actually lives on the document delivery page. 8. Users get frustrated making sense of all the software information which is confusing and more complicated than it needs to be. 9. Users get confused by “Libraries and Collections” which is just duplicative content of “University Libraries” and could be combined into one thing. 10. Users find Frequently Asked Questions hard to navigate and think it’s weird they aren’t actually questions.
  35. 35. Create a plan for ongoing usability testing. Build it into your workflow.
  36. 36. Questions?
  37. 37. Want to learn more? Steve Krug Rocket Surgery Made Easy: a do-it-yourself guide to finding and fixing usability problems
  38. 38. Want to learn more? Library Juice Academy Do-It-Yourself Usability Testing April 2014 • 4 weeks • Online, asynchronous • Only $175 http://libraryjuiceacademy.com
  39. 39. Want to learn more? Rowman & Littlefield Publishing Usability Testing: a Practical Guide for Librarians by Rebecca Blakiston [To be published in 2014]
  40. 40. Rebecca Blakiston blakistonr@u.library.arizona.edu @blakistonr Final Questions #diyux

×