Linguistics → UXR | The 15-Minute Post-Interview Debrief

This post is a deep dive into the debrief — the quick team check-in that happens immediately after each user interview. Done well, it helps you exchange observations while memory is fresh, surface the most important moments, and avoid losing anything in the cracks.

First, Let’s Talk About Interviews

User Research has many methods — some quantitative (surveys, behavioral data), some qualitative. Qualitative research almost always involves interviews. For the full process, see User Research 101.

Interviews are usually one-on-one, conducted by the UX Researcher, often with a note-taker and sometimes observers present.

At my current role, deep-dive interviews typically run about an hour — opening, core discussion, and wrap-up. A single study usually involves more than five participants. That’s a lot happening across a lot of sessions. Good note-taking matters, but so does consolidating each session right after it ends.

That’s why we run a debrief after every single interview.

Purpose of the Debrief

My first debrief was terrifying — I had no idea what I was supposed to say or how the whole thing worked. After a few rounds and some good guidance from my manager and colleagues, it clicked.

The debrief is for consolidating observations, insights, and questions from the just-completed interview while memory is fresh. Since each session is long and there are many participants, you want to capture key impressions immediately, then have a quick team discussion to highlight what matters.

Even with just the interviewer and one note-taker, running a debrief is worthwhile. When observers come from different disciplines, even better — you get genuinely different angles.

The interviewer is often so deep in the moment that they miss things. The observers catch what the interviewer missed. Debrief fills in the gaps.

In-person: post-its on a wall. Remote: FigJam, Miro, etc. Miro even has a ready-made debrief template you can use.

What Goes Into a Debrief

Observation

Facts, behaviors, phenomena. Think of these as objective captures:

• The user didn’t tap the home icon — they scrolled down instead
• The user successfully navigated to the page
• The user prefers to buy on the web version rather than the app

These are things the user said or did. No interpretation needed — just record them.

Insight

Given the observations, why did the user behave this way? This is where you add your interpretation:

• The home icon color wasn’t prominent enough, so users overlooked it and couldn’t find the entry point
• The app interface is clunky enough that users prefer the web version

Sometimes insights come from reading between the lines — what the user implied rather than stated outright (illocutionary content, for those familiar with linguistics).

Insights are critical, but be careful: are you genuinely interpreting what the user meant, or over-reading?

Quote

Actual words from the user. Usually added after reviewing notes, to make observations and insights more credible.

Question

Sometimes you leave an interview still not knowing why a user couldn’t find a path, or why they made a certain choice. Log these as open questions to explore in future sessions or follow-up research.

Action Item

If stakeholders are in the debrief and see something that needs a quick fix, it can become an immediate action item. Things like: “Most users couldn’t find the homepage entry, so we’ll strengthen it in the next release.” Track these here.

Debrief Flow

At ShopBack, we run a debrief immediately after each session — 10 to 20 minutes. Even if there’s another session in half an hour, there’s still time.

The flow:

1. Set a 5-minute timer. Everyone writes their observations, insights, quotes, questions on FigJam — one sticky per point.
2. Take turns sharing what you wrote. If there are many people or many notes, pick your top 3–5.
3. Others can react, add stickies, or comment while listening.
4. Quick final check for anything missing. Done.

It’s a remarkably efficient process.

After everyone’s off the call, the UXR can then analyze and cluster everything that was written.

Tips

• Pre-establish a format to make analysis faster. For example: gray stickies = observations, yellow = insights (or color-code by participant). Easier to read and sort later.
• One insight per sticky. Keeps things granular and easier to reorganize.
• Use tagging at the start of each note. I habitually prefix mine: #shopping-behavior #intention etc. Makes sorting instant.
• Time it. Time is precious. Set timers at the start so everyone has enough space to write without running over.
• Brief first-time participants beforehand. The first debrief is always nerve-wracking — people worry their contributions aren’t useful, and don’t know where to start. As the UXR, explain the flow and purpose upfront, and remind everyone that any observation is helpful. If you’re new to debriefs: just write what you noticed. That’s it.

Afterword

Debrief is one of those activities that’s both fun and genuinely important. You see how differently people experienced the same session — and combining those perspectives makes the whole study stronger.

My first debrief, I walked out a little deflated. Felt like I hadn’t contributed anything useful. My colleague Amy said something that’s stuck with me:

When you’re the one running the interview, you have so much to keep track of that a lot of details slip by.
Even if all you do is write down observations, you’re filling in gaps that the interviewer missed — and helping identify what really matters.

That meant a lot to me, and slowly gave me confidence. Sharing it here in case it helps someone else.

Questions welcome in the comments anytime!

Thanks for reading :D

If you enjoyed this post, feel free to click the coffee button in the lower right to support us and give Lottery a can 🐾