Interview notes can become misleading even when every sentence sounds plausible. A participant says a task is “sometimes awkward,” the note becomes “the workflow is difficult,” and the final summary reports that everyone wants a redesign. The problem is a series of small shifts between what was said and what the note taker inferred.

A structured note keeps those layers visible. Use a section for the participant's answer, a section for your interpretation, and a section for follow-up questions. This guide concerns ordinary project or editorial interviews. It does not replace consent, confidentiality, research, or retention procedures that apply to your organization.

Prepare questions around a task

Choose the activity you want to understand. In a fictional interview, the participant reviews a draft instruction sheet. Useful questions concern the last review, the material they received, the changes they needed to suggest, and the point at which the review became difficult.

Avoid filling the note with assumptions before the conversation starts. “Why is the PDF workflow frustrating?” presumes frustration and a cause. “What happened when you reviewed the last draft?” leaves room for a different account. The notes will be more useful if the questions do not decide the answer.

Use identifiers that fit the sharing scope

Give the session a date, topic, and appropriate participant identifier. Do not copy personal contact details into every working note. Store identity and consent records in the place your organization has designated if the work requires them.

Record whether an answer was written down directly, paraphrased from memory, or checked against an authorized recording. Never claim a sentence is a verbatim quotation when it is only a rough recollection. If recording is relevant, obtain and follow the necessary permission rather than assuming a note-taking template authorizes it.

Capture the answer before the interpretation

Use the participant's words for short quotations when you can preserve them accurately. Otherwise label a concise paraphrase. Then write your interpretation in a separate field. This creates a useful pause before a possible explanation becomes a reported fact.

Fictional example:
Question: What happened during your last draft review?
Answer, paraphrased: I could read the PDF, but sent wording changes in a separate message.
Exact phrase recorded: “I kept switching between the two.”
Interpretation: Moving between files may add effort to wording reviews.
Follow-up: Would an editable copy change that task?
Unresolved: The participant has not compared review formats.

The example supports a question about switching, not a conclusion that an editable format is necessarily better. Keep that limit visible when you write the summary.

Preserve context that changes meaning

A comment about one urgent review should not become a claim about every review. Record the relevant conditions: deadline, draft length, available tools, and who else was involved. Include only the details needed to understand the answer.

If the participant describes a workaround, note what it solves and what it costs. A separate message may be inconvenient but also preserve a clear record of suggested wording. The interviewer's preferred solution should not erase a benefit the participant values.

Ask follow-up questions without rewriting the answer

When an answer is unclear, ask for an example or a description of the sequence. “What did you do next?” often reveals more than asking the participant to agree with your explanation. Keep the original answer and append the clarification.

If you discover a misunderstanding after the session, record the correction with its source and date. Do not silently alter an earlier quotation. A traceable correction is more trustworthy than a tidy note that hides how its meaning changed.

Summarize patterns with their limits

A summary can group observations by task, obstacle, workaround, and unanswered question. Keep a route back to the session entries. Distinguish an observation from one participant from a pattern found in several sessions.

Avoid numerical claims that the notes cannot support. “Two participants described switching between files” is different from “most reviewers struggle.” If your sample does not support a population claim, do not make one. A small set of notes can still identify useful questions for further investigation.

Review before sharing

Check quotations, remove unnecessary identifying details, and confirm that the sharing audience is appropriate. A note prepared for a small project team may need a different level of detail from a public article. Redaction should remove the unnecessary content, not merely change its visible formatting.

Use BiNotePads for a harmless working structure if it suits the task, but keep sensitive interview records in the approved system. The final note should let a reader see what the participant reported, what the note taker concluded, and what remains unconfirmed. That separation makes the conversation useful without overstating it.

One useful final check is to hide the interpretation column and read only the answers. Then read the summary. If the summary contains a claim that cannot be connected to an answer or a clearly identified source, narrow it or mark it as a hypothesis. This check is especially helpful when several people have combined their notes and no single reviewer remembers the full conversation.

Use the BiNotePads online notepad to adapt this example. For a separate copy of important work, follow the browser-note backup guide.