Turn notes into insights by preserving each participant's context, extracting observed events and decisions, coding comparable evidence, and grouping patterns without losing exceptions. An insight explains a meaningful pattern and why it matters to a product decision. It includes source links, confidence limits, and the next question or action.
Who this is for: Product teams that have customer interview notes or recordings and need evidence strong enough to guide discovery priorities.
- Normalize notes into comparable evidence units while retaining participant, event, and source context.
- Build themes from observed similarities and differences, not from the loudest quotation or preferred feature.
- Write insights with evidence, implication, limits, and a decision connection so others can challenge them.
Prepare trustworthy evidence
Consolidate notes, transcripts, recordings, and artifacts according to consent and retention rules. Label participant, role, segment, interview date, relevant event, and source location. Correct transcription errors that change meaning, but do not polish customers' language into the team's vocabulary. Mark gaps where note quality is too weak for interpretation.
Separate observations from interpretations. 'Participant copied invoice IDs into a personal spreadsheet after search returned no result' is an observation. 'Search is unusable' is an interpretation. Both can be recorded, but visible labels preserve the reasoning path and let teammates offer alternative explanations without disputing what occurred.
Create evidence units
Break stories into units containing situation, trigger, action, obstacle, workaround, consequence, and relevant quotation. Keep each unit understandable outside the full transcript. Avoid fragmenting so aggressively that sequence disappears. A hesitation before approval may mean little without knowing that the participant had already made an expensive permission mistake.
Apply a lightweight coding scheme tied to the research question. Codes might cover uncertainty, handoff, missing information, trust, delay, or workaround. Define each code and permit multiple labels. Start with a sample, compare coding among teammates, and revise ambiguous definitions before processing the full set.
Find patterns and contrasts
Group related units, then inspect the context around them. Ask which participants encountered the pattern, under what conditions, which action followed, and which cases differed. Contradictions often reveal segmentation or a hidden variable. New users may fear irreversible edits while experienced users want faster bulk actions, making one average theme misleading.
Frequency in a small qualitative sample is descriptive, not a market estimate. Use wording such as 'five of eight interviewed administrators' and state how they were recruited. Pair interview patterns with analytics, support volume, or a survey when prevalence affects the decision. Preserve rare severe problems even when they should not define the dominant theme.
Write an actionable insight
A useful insight combines pattern, mechanism, consequence, evidence, and implication. For example, administrators delay bulk invitations because they cannot preview permission effects, which slows workspace activation and suggests testing reversible review before adding more invitation channels. This statement is more useful than 'users want better permissions.'
Attach representative and contradictory evidence, confidence, sample limits, and an owner for the next step. Link the insight to an opportunity tree, experiment, roadmap decision, or unresolved question. Synthesis should narrow or redirect action, not produce a wall of sticky notes that nobody can trace after the workshop.
Synthesize renewal interviews
Eight team administrators discussed why they renewed or considered canceling a collaboration service.
- Tag each event with company size, renewal role, trigger, observed behavior, alternative considered, and transcript location.
- Extract evidence units for value recognition, procurement friction, teammate adoption, and workarounds.
- Cluster units and notice that value is clear only after administrators assemble usage evidence for finance.
- Inspect two contradictory cases where finance already had direct dashboard access and document that contextual difference.
- Write an insight about evidence assembly, verify account patterns in analytics, and add the opportunity to discovery planning.
Insight evidence card
Create one card per decision-relevant pattern and link every claim back to source material.
- Pattern: concise statement of repeated behavior, situation, trigger, and affected participants.
- Mechanism and consequence: why the behavior appears to occur and what it changes for customers.
- Evidence: participant references, source locations, artifacts, counts within the sample, and behavioral data.
- Limits: recruitment, missing perspectives, contradictory cases, alternative explanations, and confidence.
- Implication: opportunity, decision affected, next evidence check, accountable owner, and review date.
Common mistakes
- Removing participant context until quotations from different situations appear to support one theme.
- Counting mentions in a small recruited sample and reporting them as customer population percentages.
- Writing insights as feature requests that skip the behavior, mechanism, and consequence found in evidence.
Try one
Three customers ask for exports, two describe copying data to satisfy auditors, and one needs a personal backup. What insight can and cannot be claimed?
A sound answer avoids declaring that all customers need exports. It identifies at least two underlying situations, keeps audit evidence and personal backup separate, and traces each to participants. It may propose an opportunity around assembling audit evidence, while noting sample and prevalence limits. Further interviews and usage data should test reach before selecting a solution.
Sources
- Product Talk interview snapshotPrimary Product Talk method for capturing specific customer stories from interviews.
- Nielsen Norman Group UX research cheat sheetResearch-based overview of behavioral and attitudinal methods across development stages.