Today we learned about a simple and a complex way of doing usability testing.
Simple: ask a human to perform some tasks on your product, observe them, identify what gives them trouble. You can also ask them some questions along the way.
Complex: you take various measures of usability such as time on task, time performance, efficiency, etc. The slides below remind you of the types of metrics and the overall flow of a usability test. I highly recommend Measuring the User Experience for more-in depth information about why and how to collect each metric, and how to analyze and report data for each one.
We began with an overview of research and evaluation methods:
|Not yet learned
- task analysis
- keystroke level modeling
- usability testing
- comparative usability testing
- A/B testing
- multivariate testing
You haven’t done any formal evaluation yet on your early prototype. It’s time to do that! Here are next steps:
- Conduct a cognitive walkthrough on your existing prototype.
- Improve the prototype, but keep it low fidelity. This is prototype v.2
- Create a plan for user feedback and usability testing.
- Get some informal user feedback on v2
- Improve the prototype based on user feedback, and create a high-fidelity prototype v. 3 in Axure or Sketch.
- Conduct formal usability testing on prototype v. 3
- Provide recommendations for moving on from v.3 to working prototype (v.4)
- Document everything and write it up in the last part of the final project, the evaluation report.