USABILITY TESTING
Notion templates for usability testing (script + report)
How to conduct sessions with users and summarize insights if you are a “UX team of one”
All design books say, “Crash-test your design with users.” But how to get started if you’ve never done it before? So, I decided to share free templates for moderated qualitative testing for newbies. You can use them to test a design prototype (Figma, Axure, Framer, etc.) or a live digital product (site, web app, or mobile app).
1. Testing script
Disclaimer. These templates are best suited for “UX teams of one.” A dedicated UX researcher will always deliver the highest quality; however, good enough testing, I believe, is better than none.
Designers often underestimate the value of a fully written script for usability testing. But there is no shame in always having one — in fact, an elaborate and well-thought-through script is the expert habit. Inspired by a classical template, which Steve Krug composed ten years ago, I created another one to reflect my testing experience.
Template structure
- Facilitator’s part: not shared with a user but essential to keep in mind.
- Intro: an explanation of the goal and “rules of the game.”
- Mini-interview: ideas for getting acquainted with a user.
- Tasks with a prototype or live product: task hierarchy and examples.
- Closing: session closing and the next steps.
Further reading
- Building effective tasks: “How to Maximize Insights in User Testing: Stepped User Tasks,” an article by Nielsen Norman Group.
- Formulating the right questions: “12 Ways to Fix Your User Interview Questions,” an article for Smashing Magazine and UX Collective.
2. Report
A report template should mirror the script so that you or your colleague, “co-pilot,” can fill it in on the fly and you won’t run the risk of twisting initial data. The template structure is an “inverted pyramid”: the key information tops the page. As a result, non-designers from your team who might see the report will grasp it more easily.
Template structure
- Executive summary: the most significant findings and conclusions after the whole usability testing iteration.
- Detailed results: users’ answers to the script questions and the results of performing tasks with a prototype or live product.
- Further actions: a to-do list for the team to address discovered issues.
