Usability Testing Script: Think-Aloud Session Guide
Use this script to watch people do tasks in a prototype or a live product while they think out loud. It finds where they get stuck and what they expect.
- Length
- 45 min
- Questions
- 15
- People
- 5 to 8 for each round
- Sections
- 6
What this guide finds out
- If people can finish each task without help.
- The exact screens and labels where people get stuck or go the wrong way.
- What people expected to happen at each step, and what happened instead.
- How easy each task felt, and the reason for each score.
When to use it
- You have a prototype and want to find problems before the team builds it.
- A key task in the live product has a low completion rate.
- You redesigned a flow and want to compare it with the old one.
Who to talk to
People who match your target users and have not seen the design before, on a laptop or desktop. Talk to 5 to 8 for each round people. Each interview takes about 45 minutes.
The discussion guide
Each question has a probe note. The note tells the moderator, a person or an AI, what to do with the answer.
Set-up and practice
5 minExplain the think-aloud method and practice it once.
In this session you will try some tasks. Please say out loud what you see, what you look for and what you think. We test the design, not you. Is that clear?
ProbeIf they are unsure, repeat the instruction in one sentence. Tell them that the moderator cannot see the screen, so they must describe it.
To practice, please describe the first screen out loud. What do you see, and what do you think you can do here?
ProbeIf they stay silent for about ten seconds, ask "What are you thinking now?" Praise the method, not the content.
Background
4 minLearn how the person does this kind of task today.
How do you do this kind of task today?
ProbeAsk for the last time. Keep it short. The goal is context for the tasks.
Which other apps or websites do you use for it?
ProbeRecord the names. These set the expectations that they bring to the design.
Task 1: the main task
10 minWatch the person do the most important task without help.
Task one: imagine that you want to create a new project and invite one colleague. Please do that now, and tell me when you think you are done.
ProbeReplace the task with your main task. Do not give hints. After two minutes stuck, ask what they expect to find. Then go to the next task.
What did you expect to happen when you selected that?
ProbeAsk this after any action that surprised them. Ask them to name the button or link so that the moment is clear in the recording.
How sure are you that you finished the task?
ProbeIf they are not sure, ask what would tell them that it worked. Missing feedback is a common problem here.
Task 2: change a setting
10 minTest how people find and change a setting.
Task two: you want to stop the email notifications for this project. Show me how you would do that.
ProbeReplace the task with your second task. Note each place they look first. Do not tell them where the setting is.
Was there a moment where you were not sure where to go next?
ProbeAsk which screen it was and what they looked for there.
What did you think the label on that menu meant?
ProbeAsk about the label where they hesitated. Record their meaning in their words.
Task 3: find information
9 minTest how people find information and judge the result.
Task three: find out how much the team plan costs for five people.
ProbeReplace the task with your third task. If they give an answer, ask how sure they are.
On a scale from 1 to 5, how easy was this task?
ProbeShow the scale on screen. Ask for the reason for the score. Ask the same question after each task if time allows.
Debrief
7 minGet the overall view after all tasks.
Which part of the design was the hardest to use?
ProbeAsk them to go back to that screen and describe what should be different.
What was easier than you expected?
ProbeRecord the answer. Keep these parts in the next version.
What would you tell the designer of this product?
ProbeDo not ask a follow-up. Thank them and end the session.
Example finding
Most people looked for notification settings in their profile, but the setting was inside each project.
“I would expect it under my name, top right. It is not there, so maybe it does not exist?”
Mistakes to avoid
- Do not help when people are stuck. A hint hides the problem you came to find. Note the moment and move on.
- Do not use words from the interface in the task. "Click Share" tests reading, not the design.
- Do not count opinions as findings. Count what people did: where they clicked, where they stopped, if they finished.
- Do not test with more than eight people in one round. Fix the problems you found, then test again.
Analyze the answers
Analysis templateUsability Issue Severity Rating Scale: Levels and RulesUse this scale to rate each issue from a usability test. Rate what the issue did to the task, then apply the modifiers. Two people who use these rules should give the same rating.Questions
In a think-aloud test, a person does tasks with a product and says what they see, think and expect. It shows where the design confuses people.
Five to eight people in each round find most of the large problems in one flow. Run more small rounds, with a fix between each round.
Yes, with video and screen share. In User Evaluation, the screen is recorded, but the AI moderator only hears the person. It asks people to describe what they see and do.
Phones cannot share a screen in the browser. For a prototype test with screen recording, ask people to use a laptop or desktop.
Let the AI moderator ask these questions
The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.