Skip to content
Tutorials Center
My learning

Topics

Lesson 28 of 36 ยท Usability Testing

Moderating Usability Sessions

Run a usability session well: set the tone, use think-aloud, ask neutral questions, avoid leading, handle silence, take notes and close the session.

Moderating is the skill of guiding a usability session while staying out of the way. A good moderator makes the participant comfortable, keeps them talking about what they think, and resists the very human urge to help. The goal is to see what happens when the design is used without you there.

This lesson assumes you have a test plan with tasks and a script.

Before the session

  • Test the equipment: screen sharing, recording, audio, and the prototype link. Have a backup.
  • Prepare a clean environment: logged-in test account, reset data, notifications off.
  • Assign roles: a facilitator who talks to the participant and a note-taker (and observers, who stay silent and muted).
  • Re-read the script, but do not memorize it word for word. Sound natural.

Opening the session

The first five minutes set the tone:

  1. Thank them and introduce yourself and anyone watching.
  2. Explain the purpose: "We are testing the design, not you. You cannot do anything wrong."
  3. Ask for permission to record and explain how the recording is used and protected.
  4. Explain think aloud: "Please say whatever comes to mind as you work: what you are looking at, what you expect, anything confusing."
  5. Say that you will not be able to answer many questions during tasks because you want to see how it works on their own, and that you will answer at the end.
  6. Ask a few easy background questions to warm up.

Think aloud

Concurrent think aloud has the participant narrate while working. It exposes expectations and confusion, but it can slow people down, so do not use it for timing studies. Retrospective think aloud replays the recording afterward and asks them to explain it; it keeps timings natural. Remind a quiet participant gently: "What are you thinking now?" or "Keep talking, please."

Say less, listen more

Moderator habits

Embrace silence Count to five before you speak.
Echo Repeat their words: "It seems confusing?"
Neutral probes "Tell me more about that."
Do not help Do not rescue, explain or defend.
1 / 2

Ask neutral, open questions

Leading (avoid) Neutral (use)
"Was that easy?" "How would you describe that?"
"Don't you think the menu is clear?" "What do you make of the menu?"
"Did you see the search box?" "What would you do next?"
"Would you use this feature?" "Tell me about the last time you needed something like this."

People tend to be polite and say what they think you want to hear, and what they predict about future behavior is unreliable. Watch behavior over opinions, and ask about past actual experiences instead of hypothetical ones.

When the participant asks you a question

Turn it around: "What would you do if I were not here?" or "What do you expect will happen?" Note that the question itself is data.

When the participant is stuck

Let them struggle for a bit: the struggle is the finding. If they are frustrated, give a graded nudge: first a neutral prompt ("What are your options here?"), then a hint, and only as a last resort the answer. Mark the task as "completed with assistance" in your notes. Do not let a participant suffer for a long time; move on.

Taking notes

Record observations separate from interpretations. A useful habit is a log with a timestamp, task, what happened, and a quote:

Python Observation log and tally

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A tally like this feeds the analysis in analyzing findings and severity. Tag a finding as it happens, and decide its severity later, together.

Closing the session

Ask a few debrief questions: "What was the best/most frustrating part?", "If you could change one thing...", and an overall rating such as SUS. Thank them, explain compensation, and stop recording. Immediately afterward, spend ten minutes with the note-taker writing down top impressions while they are fresh.

Remote and unmoderated tips

  • Check that the participant's connection and device work in the first minutes.
  • Keep instructions in writing; ask for audio and screen recording.
  • For unmoderated tests, write tasks extremely clearly, add a comprehension question, and pilot more carefully because nobody is there to clarify.

Common moderator mistakes

  • Explaining the design or defending it.
  • Leading questions and nodding when the participant does the right thing.
  • Talking too much, or finishing their sentences.
  • Letting observers comment during the session.
  • Testing a design that is not stable enough to survive the session.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. Which question is neutral?

    Open, non-judging prompts do not signal an expected answer.
  2. 2. A participant is stuck. What should the moderator do first?

    Let the struggle show, then give graded neutral help; note any assistance.
  3. 3. Why is concurrent think aloud poor for timing studies?

    Talking while working changes pace, so timings are unnatural.

Summary

  • Prepare equipment, roles and a calm environment; open by saying you test the design, not the person.
  • Use think aloud, embrace silence and ask neutral, open questions.
  • Do not rescue or defend; give graded hints and record assistance.
  • Take objective notes with timestamps and quotes; debrief right after.

Next: Analyzing Findings and Severity