The think-aloud protocol asks participants to verbalize their thoughts while they work through tasks with an interface. Instead of guessing why a user hesitated, clicked the wrong button, or abandoned a flow, you hear their reasoning in the moment: what they expected, what label confused them, what they thought would happen next. The method rests on the idea that people can report the contents of their working memory as they perform a task, which makes it one of the richest sources of qualitative usability data available in a controlled test.
In this module you are learning to run a controlled session and capture clean data, so think-aloud is both a skill and a risk. Done well, it surfaces the reasoning behind errors and slowdowns. Done poorly, it biases behavior: leading prompts put words in the participant's mouth, over-talking slows the user and distorts time-on-task, and some tasks (highly practiced expert work, for example) simply break down when narrated. That is why the distinction between concurrent think-aloud (speaking while doing) and retrospective think-aloud (reviewing afterward, often with a screen recording) matters so much.
As you watch, pay attention to three things: the exact wording facilitators use to instruct and re-prompt participants, the moments where the facilitator deliberately stays quiet, and the signals that tell you concurrent think-aloud is not working and a different approach is needed. Also notice how session logistics -- consent, recording setup, note-taking, timing -- are built into the routine rather than improvised.
This short video from Nielsen Norman Group focuses on getting participants to actually think aloud: explaining the technique and its purpose at the start of a session, reinforcing the behavior when the participant does it well, and using gentle prompts to restart narration when they fall silent. Expect concrete examples of neutral prompt wording a facilitator can reuse. It covers the practical gap between telling someone to "think out loud" and getting usable verbal data.
It maps directly onto the "training participants" and "facilitator techniques" subtopics, and NN/g is a long-standing authority on usability testing practice, so the prompt wording it models is safe to adopt in your own sessions.
This video addresses the limits of the concurrent think-aloud method, particularly with work-domain experts whose tasks are fast, automatic, or cognitively demanding enough that narrating interferes with performance. It points to alternatives such as retrospective testing, expert walkthroughs, and interviews. The framing is about choosing the right method rather than forcing think-aloud into every study.
It is the clearest fit for the concurrent versus retrospective subtopic and directly supports the idea that a method can confound the data it is meant to collect -- an important judgment call for any test facilitator.
A checklist-style walkthrough of roughly ten things a moderator should do when running a usability study, covering the sequence of a session from setup through task facilitation. It situates think-aloud within the larger routine of moderating, including preparation, consent and recording, and neutral behavior during tasks. The checklist format makes it easy to turn into a session script of your own.
It provides the procedural wrapper around think-aloud -- standardized protocol, recording and capture, moderator neutrality -- which connects this topic to the rest of the controlled user testing module.
Together these videos build the facilitation skill set MO1 describes: the checklist video supplies the standardized session routine, and the "Help Users Think Aloud" video supplies the specific moderator moves for instructing, reinforcing, and re-prompting participants mid-task. For MO2, think-aloud is the qualitative stream that sits alongside completion rates, errors, and time-on-task, and these videos show how to elicit and capture it rather than hope it happens. For MO3, "When Thinking Aloud Fails" and the emphasis on neutral, non-leading prompts teach you to recognize when the method itself is contaminating the observation -- leading questions, expert tasks disrupted by narration, or talking that inflates time measures -- and to switch to retrospective or interview-based techniques to keep the data trustworthy.
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.