Volver al blog

How to Dictate a User Interview Debrief While It Is Fresh

After an interview, use a short voice draft to separate what happened, what you inferred, and what to check next.

15 nov 2026Whisper One TeamWhisper One Team

A user interview ends, and your next meeting starts in five minutes. Before you close your notes, say what you noticed while you can still remember the sequence. The goal is a useful debrief you can return to later. It is easy to forget whether someone said a task was confusing or you inferred that from watching them.

This guide uses a fictional interview about booking a room. The workflow starts after the conversation, when you are speaking your own summary. Use only information and tools your research policy allows. When working with real participants, keep references in the approved research workspace.

Give the note a scope and a reference

Write the session label, the task, and the part of the experience you are summarizing. For example: “Practice session R-04, finding an available room, first attempt.” Copy your reference from the original notes if one exists. This gives you a way to locate the evidence later without adding someone's identity to the voice draft.

Decide what belongs in the debrief. If you tested booking and canceling, choose one of those tasks for the first note. A narrow task makes it easier to recount the sequence. You can always add another note when you have time.

Dictate the event before the interpretation

Start with the action you saw. In the fictional session, the participant chose a date, opened Help, returned to the room list, and selected a room. That sequence means something even before you know why it happened.

Add any relevant paraphrase, and label it as one. For instance, you might recall that the participant was unsure whether the room list showed one date or the full week. Do not put quotation marks around a sentence you reconstructed from memory. If an exact quote is essential, check it later against an approved source and use the wording and permissions your team requires.

Then add your interpretation under a separate line. “The selected date may have been easy to miss” is a hypothesis. The sequence and the participant's reported uncertainty are the observations behind it. Keeping both sentences makes it possible for a colleague to suggest another explanation, such as unfamiliar wording in the room selector.

Leave one question that would change your mind

Pick a follow-up that could help distinguish between explanations. In the room example, you could ask the next participant to report which date they believe they are viewing before they choose a room. That gives the team something to look for, instead of a vague assignment to “test the page more.”

If you notice an exception, keep it. Perhaps this participant found the date immediately after opening Help. That could change what you test next. Write down missing context as well, such as whether they had booked a room in the past. Avoid turning a single session into a statement about all users.

Check the draft against the notes

Read the transcript once for facts and once for labels. Fix any swapped order, missing qualifier, or ambiguous role. Keep “observed,” “reported,” and “possible explanation” distinct. Add the source reference inside the approved system, then move the edited note to wherever the rest of the research lives. Use a draft location that your team permits if you are going to copy the text later.

For the next session, keep a short prompt handy: what happened, what might explain it, and what would I check next? This is enough structure to use when you only have a few minutes. You can practice with fictional notes using Whisper One for a supported Apple Silicon Mac and the first dictation guide. Review the history and privacy guide before deciding whether the workflow is appropriate for your material.