Usability Testing Questions: Before, During, and After a Task
By SayCraft Team · 2026-08-26 · 4 min read
Usability-testing questions should reveal context and observation, not lead the participant toward the design. Before the task, ask about relevant experience and expectations. During it, use neutral prompts such as What are you looking for? or What do you expect to happen? Afterward, ask what felt clear, difficult, surprising, or missing, then connect answers to observed behavior and the exact prototype version.
Community signal: Recorded search demand supports this facilitation question-bank intent. It is distinct from the broader UAT sign-off checklist already in the queue.
What usability testing questions are for
Usability-testing questions should reveal context and observation, not lead the participant toward the design. Before the task, ask about relevant experience and expectations. During it, use neutral prompts such as What are you looking for? or What do you expect to happen? Afterward, ask what felt clear, difficult, surprising, or missing, then connect answers to observed behavior and the exact prototype version.
Copyable facilitator question sheet
Keep questions, observations, participant quotes, assistance, and interpretation in separate fields. That separation prevents a tidy debrief from rewriting what happened in the task.
Prepare a consistent core task and question set while allowing neutral follow-ups. During the session, timestamp key events and record any facilitator help. Immediately afterward, preserve the participant's explanation before discussing solutions. Across sessions, compare the same task outcome and failure point, but retain differences in role, context, device, and build instead of averaging them away.
- Consent, role, relevant experience, device, build, and session scope
- Task goal, first expectation, search behavior, hesitation, error, recovery, and assistance
- Post-task belief, clarity, difficulty, surprise, missing information, confidence, and next action
- Researcher interpretation, alternative explanation, repeated pattern, segment difference, and follow-up test
- Quote, observed behavior, task result, facilitator influence, and evidence timestamp
Invitation-flow session example
For an invitation flow, ask what the participant expects before opening the link, observe where they pause, and use a neutral prompt if they become silent. After completion, ask what they believe happened and what they would do next. Record the build, role, result, hesitation, and quote separately.
- Confirm consent and session scope
- Ask about context without selling the design
- Observe before prompting
- Separate quotes, behavior, and interpretation
Ask before the task without training the participant
A session guide should leave room for observation. Begin with a neutral introduction, consent, the scope of the prototype, and a reminder that the design is being tested rather than the participant. Ask about relevant context without training the person on the interface. Present a realistic task as a goal, not a sequence of clicks, and wait long enough to observe the participant's first interpretation before using a prompt.
Review facilitator language alongside participant behavior. If a successful task followed a hint, a product term supplied by the facilitator, or a corrective gesture, mark the assistance. If the participant said a task was easy but hesitated or took a wrong path, preserve both signals. The next test should distinguish interface comprehension from politeness, memory, or facilitator influence.
- Nielsen Norman Group: usability test facilitator guide
- Atlassian: product requirements template
Prompt neutrally while observing behavior
During the task, prompts should recover the person's thought process without teaching the answer. Useful prompts include What are you trying to do now?, What are you looking for?, and What do you expect that control to do? Avoid praise, correction, or questions that contain product vocabulary the participant has not used. When help is required, record the point and the exact assistance because the task is no longer an unassisted success.
Debrief and interpret without overgeneralizing
Post-task questions should connect subjective experience to observed behavior. Ask what the participant believes happened, what felt difficult, what they would do next, and what they expected to find. Preserve quotes and observed actions separately from the researcher's interpretation. Across sessions, look for repeated task-level patterns while retaining meaningful differences in role, experience, device, and prototype version.
Limits of a small usability study
A preview is not evidence of production security, compliance, or launch readiness.
- Questions do not reveal the expected answer
- The task matches a realistic user goal
- Observations identify the exact build and role
- One participant is not generalized into a market conclusion
Sources and discussion
- Nielsen Norman Group: usability test facilitator guide (publisher)
- Atlassian: product requirements template (publisher)
Community posts describe individual experiences and questions; they are not treated as universal proof.
Related resources
Build the next step with SayCraft
Use a small set of neutral prompts on one important journey, then revise the product conversation from observed evidence rather than preference alone. SayCraft supports the evolving preview; the research owner controls consent, interpretation, and release decisions.