A usability testing protocol is the written plan that makes a user study repeatable. It spells out who you will recruit, what tasks participants will attempt, what the facilitator will say at each stage, what data you will capture (time on task, errors, completion, think-aloud comments, satisfaction ratings), and the practical details of where and how sessions will run. Without this document, two facilitators running the "same" study will produce results you cannot compare.
In this course, the protocol is the bridge between the prototype you are building and the evidence you will collect about it. Your task scenarios must be realistic and goal-oriented rather than instructions that give away the interface; your script must keep you neutral so you do not accidentally coach participants toward success; and your logistics plan must account for consent, recording, timing, and backup options if the prototype breaks. Pilot testing the whole package with one or two people almost always exposes confusing wording and tasks that take far longer than you estimated.
As you watch, pay attention to the exact phrasing facilitators use when introducing a session, the order of steps a moderator follows, and the distinction between testing a product's usability and testing whether users want the product at all. Try to map what you see back to specific sections of the protocol document you will write for your own project.
A short demonstration from Nielsen Norman Group showing how a facilitator greets and orients a participant at the start of a usability test session. The description indicates it draws on a facilitator's script to cover the points that should be stated up front, such as explaining the purpose of the session and setting expectations before tasks begin.
It models the opening portion of a facilitator script, which is exactly the subtopic on developing facilitator scripts, and it comes from NN/g, a long-established usability research organization.
A checklist-style video presenting ten things a moderator should do when running a usability study. It walks through the sequence of steps a facilitator follows during a session and connects following that sequence to getting usable research findings.
A moderator checklist is essentially the procedural backbone of a testing protocol, so it supports both the anatomy-of-a-protocol and session-logistics subtopics in a compact, memorable format.
Kerev Design compares user testing and usability testing as two distinct activities within UX research, explaining what each one asks and when each is appropriate. The video situates both within the broader research process introduced in the channel's earlier UX research material.
Knowing which question you are actually answering determines how you write task scenarios and what data you plan to collect, so this conceptual distinction helps students scope their protocol correctly before drafting it.
Together these videos target MO2 most directly: the NN/g demonstration and moderator checklist give concrete models for the facilitator script, session sequence, and logistics sections of a testing plan, while the comparison video helps students frame the right research question so their task scripts and data collection instruments measure the right thing. Because the protocol defines what participants will be asked to do, writing it also forces students to confirm that the prototype actually supports those tasks, which feeds back into the prototype development and verification work in MO1 and MO3.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.