Debriefing: Closing the Loop in Research
Debriefing is a structured conversation after a research session to gather feedback and clarify observations. Use it after usability tests to understand a user's thought process and answer their questions.
WHY IT EXISTS: Research sessions can generate ambiguous data. A user might click somewhere unexpectedly, but without asking them why, you're just guessing their intent. Debriefing exists to turn observation into understanding by formally reviewing the session with the participant.
THE MENTAL MODEL: Think of debriefing as the "director's commentary" for a research session. After the "movie" (the user test) is over, you and the "actor" (the participant) sit down together to review key scenes, discuss their motivations, and clarify what really happened. It's a structured, active process, not a simple thank you.
HOW IT WORKS: Following a research exercise, the facilitator guides the participant through a structured review. This isn't an interrogation but a collaborative report-building process. You might review specific actions ("I noticed you paused here, what were you thinking?"), explain parts of the study that were intentionally vague, and answer any questions the participant has. The goal is to get a complete report of the event from their perspective.
WHEN TO USE IT: Use debriefing after almost any user-facing research activity, especially experiential ones like usability tests, simulations, or diary studies. It's essential when you need to understand the 'why' behind a user's actions and ensure they leave the study with a clear understanding of its purpose.
WHEN NOT TO USE IT: It's less critical for purely quantitative methods where user intent is not the primary focus, like A/B testing on a button color. Also, in some psychological studies, debriefing might be delayed or modified to avoid influencing future participants, though this is less common in typical product research.
ONE CANONICAL EXAMPLE: After a 30-minute usability test for a new app feature, the researcher stops the recording. They then spend 5-10 minutes debriefing: "Thanks for doing that. Let's quickly review. On the checkout screen, you tried to tap the logo. What were you expecting to happen there?" This clarifies an ambiguous action and gathers information that observation alone could not.
Read the original → en.wikipedia.org
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.