Usability testing recording template
A consistent session script and observation log, so findings are comparable across participants and researchers.

- Time
- 45 min per session
- People
- 1–2 facilitators per session
Overview
Two halves in one file: the script the facilitator reads, and the log the observer fills in. The point is comparability — five sessions run by three people are only evidence if they were run the same way and written down in the same shape.
When to use it.
During concept validation, for every usability session against the prototype. Set it up before the first session, not after the third, or the early sessions are not comparable with the later ones.
Who to involve.
One to two facilitators per session: one running it, one recording. If the session is remote, recommend just one facilitator rather than two, and keep the meeting small, with only one participant per test. Two facilitators at most, and only if the session is in person. This keeps the room small enough that the participant is not nudged toward a confirmation-biased answer. Participants are real users, recruited against the persona.
Effort.
High prep Medium engagement Preparing the script once takes longer than any individual session — and is what determines whether the round is usable.
Outcomes.
Findings you can compare across participants and across researchers, separated into what people did and what you think it means. Feeds the Jobs to be done refinement and the now / next / later prioritisation at handover.
Recommendations.
Record the workaround, not just the failure — in industrial software what someone does instead is usually more informative than where they got stuck. Do not fix the prototype mid-round, or you have tested two different things. And debrief within the hour, while it is fresh, before the next session overwrites it.
How to run it
Write the tasks, not the questions
Each task is something the participant is trying to achieve. “Find out whether this job can be finished today” is a task. “What do you think of this screen?” is not.
Fix the script
Same intro, same wording for each task, same prompts when someone gets stuck. Deviating helps that one participant and costs you the comparison.
Brief the observer
Before the first session, agree which of the two facilitators runs it and which records — and walk the second person through the script so they know what to expect.
Log behaviour, then interpretation
Keep the two in separate columns. What they did, then what you think it means. Only the first column is evidence.
Debrief within the hour
Immediately after each session, the two facilitators spend five minutes comparing notes: what surprised them, and anything to flag before the next participant arrives.


