How to take notes in a user interview (without losing the conversation)

You have a customer call at 10:00 and another meeting at 10:30. You open a blank document, type as quickly as you can, and finish with three pages of notes.

Two days later, the notes are strangely unhelpful. You have fragments such as “CSV annoying” and “asked about API”, but not the story around them. You cannot remember whether “I’d use that” was a serious commitment or a polite response to your feature pitch.

The opposite approach fails too. You take no notes so you can give the participant your full attention, then trust yourself to write everything up later. By then, the conversation has compressed itself into the points you already expected to hear.

The answer is not to choose between listening and documentation. It is to give each a different job:

Record the conversation with permission, take lightweight notes while you listen, and turn both into a short interview snapshot immediately afterwards.

This guide shows you how to take notes in a user interview when you are the only researcher in the room. It includes a simple notation system, a copyable user interview note template, and a post-interview routine that makes the notes useful weeks later.

Why verbatim note-taking makes interviews worse

Interviewing and detailed note-taking compete for the same attention.

Nielsen Norman Group identifies note-taking while facilitating as a common cause of disrupted user interviews. Looking down to type makes it harder to follow the participant, notice hesitation, and ask a useful follow-up. It can also weaken the rapport that helps someone share an awkward or critical story.

Selective note-taking creates another problem. If you start typing only when a participant mentions your planned feature, you reveal what you want to hear. A helpful participant may spend more time on that topic because your behaviour has signalled that it matters.

Your notes should support the conversation, not direct it.

That is why the goal during the call is not a complete transcript. It is to capture just enough structure to:

• notice gaps and contradictions;
• remember what you want to ask next;
• mark evidence worth finding in the recording; and
• separate what the participant said from what you inferred.

The recording stores the words. Your live notes help you think.

Choose the right note-taking setup

Use the best option your team and consent requirements allow.

Best: one interviewer and one notetaker

If a co-founder or teammate can join, give them one job: capture the conversation while you lead it. Ask them not to interrupt or react visibly to feedback. Debrief together as soon as the participant leaves.

This setup lets the interviewer stay present and gives you two perspectives afterwards. It is especially useful for high-stakes churn, win/loss, and concept-testing conversations.

Do not invite a crowd. Extra observers can make a candid conversation feel like a panel interview. One quiet notetaker is enough.

Good: a recording and lightweight notes

When you are interviewing alone, record the conversation and reduce your live notes to cues. Teresa Torres describes using a recording to avoid verbatim note-taking while remaining present, then writing only enough to follow the story and ask better questions.

Tell the participant what you are recording, why, who will have access, and how long you will keep it. Ask for explicit permission before you start. If they decline, respect the answer and use the next setup.

When you cannot record: a chronological log

Without a recording or a notetaker, you need a more complete written record. Tell the participant that you will pause occasionally to write. Capture events in order, mark exact quotations clearly, and leave interpretation until after the call.

The conversation may move more slowly. That is better than pretending sparse notes are a reliable record.

Paper or laptop? Choose the less distracting tool

There is no universal winner.

Paper makes notifications impossible, keeps a screen out of the participant’s eyeline, and makes arrows or quick diagrams easy. A plain text document is searchable, legible, and easier to combine with other interview notes.

The often-repeated claim that handwriting always produces better understanding comes from studies of students taking lecture notes, not researchers conducting interviews. A later replication found small, non-significant effects and concluded that it was too early to call one method superior.

Use whichever tool helps you look up, listen, and resist transcription. If you use a laptop, close Slack, email, and everything except your interview guide and notes.

What to write during a user interview

Use a small set of marks that you can understand at a glance. The exact symbols do not matter; consistency does.

These marks cover six useful kinds of information.

1. The spine of the story

Capture the trigger, sequence, workaround, and consequence.

Suppose a participant is describing a failed monthly report. Your notes might be:

client asked for new cut of data
→ exported CSV
→ totals did not match dashboard
→ rebuilt chart in Sheets
→ sent report next morning
consequence: missed client deadline

That sequence will help you see what is missing. Who noticed the mismatch? How did the participant decide which number to trust? What happened with the client?

“Reporting is painful” gives you nothing to probe. A sequence gives you the next question.

2. Short, exact quotations

Participant language is valuable for positioning, interface copy, and preserving the meaning of an experience. Erika Hall recommends noting the exact phrases and vocabulary participants use.

Use quotation marks only when you are confident the wording is exact. If you missed part of the sentence, write a plain-language paraphrase without quotation marks and check the recording later. A polished sentence reconstructed from memory is not a verbatim quote.

Two or three strong quotations are usually more useful than pages of transcription.

3. Observable reactions

Write what you observed, not the emotion you assume.

• Better: long pause before answering
• Worse: embarrassed
• Better: laughed, then lowered voice
• Worse: secretive

The first version remains evidence. The second has already converted your interpretation into a fact.

4. Questions to return to

Do not interrupt a useful story because three follow-up questions arrived at once. Put ? in the margin, let the participant finish, and return to the missing detail at a natural pause.

This small habit makes the interview feel like a conversation instead of a checklist.

5. Your own thoughts, clearly separated

Ideas will appear while you listen. Write them down so they stop occupying your attention, but prefix them with ME: or another unmistakable marker.

Nielsen Norman Group’s guidance on chronological research notes makes the same distinction: researcher comments and suggestions must be visibly separate from participant observations. Otherwise, your hunch can return three weeks later disguised as something a customer said.

6. Timestamps

Add the time when you hear a decisive quote, a confusing sequence, or a moment you may share with the team. You are far more likely to revisit minute 18 than rewatch an entire 40-minute call.

A user interview note template you can copy

Prepare the sheet before the call. Keep the research decision and core prompts visible so you do not have to switch documents.

USER INTERVIEW NOTES

Participant ID:
Date:
Research decision:
What I need to learn:

CORE PROMPTS
1.
2.
3.

LIVE NOTES
Use: “quote” | → sequence | ? follow-up | ! observation | ME: interpretation | timestamp


POST-INTERVIEW SNAPSHOT
Context:
Story in 4–6 steps:
Memorable quote:
Needs or pain points:
Other insights:
Contradictory or missing evidence:
Follow-up:
Recording location and deletion date:

Use a participant ID in working notes instead of attaching a person’s name to every artefact. Keep the identity key separately and restrict access to it. Nielsen Norman Group recommends numbering participants and their documents for this reason.

Turn raw notes into an interview snapshot

The work is not finished when the call ends. A recording without a summary becomes a future research backlog; rough notes without context become fragments.

Block 20–30 minutes after each interview. Do not put another meeting directly after the call if you can avoid it.

Teresa Torres’s Interview Snapshot is a one-page summary of one conversation. Her full format includes participant context, a memorable quote, opportunities, insights, and an experience map of the story. Experienced teams can create one collaboratively in 15–20 minutes; newer teams may need longer.

For a founder working alone, use this sequence:

1. Complete the story. Turn arrows and fragments into four to six chronological steps.
2. Check the evidence. Use timestamps to confirm important wording in the recording.
3. Add context. Record only the participant details relevant to the research decision.
4. Separate opportunities from insights. A need or pain point may invite action; an interesting observation may simply need more evidence.
5. Keep contradictions. Note what does not fit your emerging explanation.
6. Write the next question. Capture what you need to verify in another interview.

Do this while the conversation is still fresh. Product Talk recommends creating the snapshot immediately after the interview, and Nielsen Norman Group similarly advises teams to debrief after every session and share preliminary findings promptly.

A recording is evidence, not a substitute for notes

Recordings are useful because they preserve exact wording and let you revisit a marked moment. They are not a complete note-taking system.

Nielsen Norman Group warns that recordings take as long to review as the original session and can fail. Test the recording before the call, keep lightweight notes anyway, and confirm that the file exists before you close the session.

Treat recordings and transcripts as sensitive research data:

• collect explicit consent;
• explain how the material will be used;
• limit access to people who need it;
• remove unnecessary personal details from working artefacts;
• set a deletion date; and
• honour any promise you made to the participant.

A searchable transcript does not make careless retention safe.

Common user interview note-taking mistakes

Typing everything

You lose eye contact, miss follow-ups, and produce a transcript-shaped document that still needs analysis. Let the recording handle completeness.

Writing only conclusions

“Onboarding is confusing” cannot be audited. Capture the action, moment, and consequence that support the conclusion.

Mixing quotes and paraphrases

Quotation marks should mean exact wording. Check anything important against the recording.

Hiding your interpretation inside the notes

Use ME:. Your thinking matters, but it should not impersonate participant evidence.

Skipping the post-interview review

Unprocessed notes decay into fragments. Protect the 20–30 minute snapshot block as part of the interview itself.

Treating one memorable quote as a theme

A quote is evidence from one participant. A theme needs repeated, traceable evidence across relevant participants. Use the workflow in Maren’s guide to synthesising user interviews into themes when you are ready to compare conversations.

Where Maren fits

This manual system works when you are running live interviews yourself. Maren is useful when the repeated conversations and processing are the bottleneck.

You tell Maren what you want to learn and share an interview link. She runs adaptive research conversations, asks follow-ups, and produces a transcript and summary for each participant. Cross-interview synthesis then helps you find themes and patterns without losing the underlying conversations.

You still own the research decision. You still judge the evidence. Maren handles the repeated interviewing and first pass through the notes so you can spend more time deciding what the stories mean.

The simple rule to remember

Do not try to write the interview while you are still conducting it.

Record with permission. Capture the story’s shape, a few exact phrases, your follow-up questions, and timestamps. Mark your own thoughts as your own. Then spend 20–30 minutes turning the call into a one-page snapshot before the next conversation pushes it out of your head.

Good user interview notes are not the longest notes. They are the notes that let you recover the evidence, understand the story, and make a better decision later.