Practise the language of running a usability test: facilitator scripts, think-aloud instructions, neutral prompts when participants get stuck, and severity rating vocabulary.
0 / 11 completed
1 / 11
How should a facilitator open a usability test session with a participant?
A usability test opening should cover: welcome (put the participant at ease), purpose (what today's session is about), consent (confirm recording/data use is agreed), and the think-aloud protocol (explain that you want them to narrate their thoughts). Skipping this makes participants anxious and less likely to behave naturally, which contaminates the data.
2 / 11
Which sentence correctly introduces the think-aloud protocol to a participant?
The think-aloud instruction should invite continuous, low-effort narration — expectations, confusion, and reactions — not just bug reports. Phrasing it as 'even small comments... are useful' lowers the bar and encourages participants who might otherwise stay quiet out of politeness or self-consciousness.
3 / 11
A participant apologises, saying 'Sorry, I'm sure this is just me being bad with computers.' What is the best facilitator response?
The standard reassurance phrase in usability testing is 'I'm not testing you, I'm testing the product.' This resets the power dynamic: the participant is not being evaluated, the interface is. Option A risks a leading cue (implying the design is already known to be flawed), which can bias later behaviour.
4 / 11
A participant is stuck and asks the facilitator, 'Am I supposed to click here?' What is the best neutral response?
Facilitators must avoid steering behaviour, even under pressure. The neutral redirect — 'keep going with what your instinct tells you' — preserves the validity of the observation. Directly answering yes/no (options A and B) or demonstrating the flow (option D) contaminates the task data by injecting the facilitator's own judgement.
5 / 11
Which of these is a well-written, scenario-based task instruction (rather than a feature-based one)?
Good task instructions are scenario-based and behaviour-framed: they describe a real-world goal without naming the UI elements or feature the participant should use. 'Click the filter icon' (A) leaks the solution; 'test the search feature' (B) is too vague; 'find a bug' (D) asks the participant to evaluate rather than behave naturally.
6 / 11
In usability findings, a bug that prevents most users from completing a core task at all is rated as:
Standard usability severity ratings run: critical (blocks task completion for most users — must fix before launch), serious (causes significant difficulty or workaround for many users), moderate (causes some friction but users recover), cosmetic (visual/minor issue with no impact on task success). Severity ratings help teams prioritise fixes objectively rather than by opinion.
7 / 11
During a remote usability test of the new payment gateway API, Sarah notices a user repeatedly attempting to submit a transaction that's failing with a 'validation error'.
Which of the following is the most appropriate initial response for her as the facilitator?
The best response focuses on gathering more information from the user. Option 1 encourages the user to continue and potentially reveal more details about their process. Options 2, 3, and 4 prematurely assume a problem or offer unhelpful advice without understanding the root cause of the error. It's crucial to understand *their* experience first.
8 / 11
Mark, a senior developer, is reviewing a PR proposing a new feature for an e-commerce platform. The description reads: 'Implement the discount code logic.'
What's the most helpful follow-up question he could ask to ensure clarity and understand the scope?
Asking about integration is key to understanding the broader context. The API endpoint is important but secondary to knowing *how* it fits within the system. Option 3 focuses on a specific detail (percentage) that might be missing, and option 2 is too broad without specifics. This question aims for a holistic understanding of the feature's impact.
9 / 11
During a usability test for a mobile app redesign, David asks a participant: 'Think aloud as you try to find the settings menu.'
What is the primary purpose of this instruction?
The think-aloud protocol is fundamentally about understanding *why* a user is struggling. It's not about navigation or technical terminology; it's capturing their cognitive process – what they were intending to do, what they actually did, and why the difference occurred. This insight is invaluable for identifying usability issues.
10 / 11
Lisa is facilitating a remote usability test when a participant says: 'I'm not sure what to do here. Is there a button I should be clicking?'
Which of the following responses is MOST appropriate?
Offering a guided walkthrough is the most supportive approach in this situation. It avoids making the user feel lost or inadequate and provides immediate assistance without assuming they've missed something obvious. The other options are unhelpful – suggesting random clicks, offering platitudes, or simply providing a visual aid without guidance.
11 / 11
You're preparing a PR description for a change that adds a new logging feature to a microservice. Which of the following options provides the most effective and user-friendly instruction for a developer reviewing the code?
The best option focuses on the *benefit* of the change – 'improved debugging'. It's clear, concise, and uses relatable language. The other options are overly technical or describe the implementation details without explaining why it's valuable to the user (the reviewer).
This exercise, "Usability Test Facilitation", tests your understanding of ux research vocabulary and phrasing through 11 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 11 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this UX Research exercise for?
It's designed for IT professionals and learners who want to sound natural discussing ux research topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more UX Research exercises?
Browse the full UX Research exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.