How to Analyze User Interviews With Source-Linked Evidence
Analyze user interviews by reviewing the source, separating observations from interpretations, grouping related moments, and checking the resulting Finding against counter-evidence. A transcript summary helps you navigate a recording; it does not replace the evidence needed for a product decision.
UserTold preserves the Interview record and extracts Evidence after processing. Your job is to verify what those moments support before a draft Finding becomes a reviewed problem.
1. Check the source before the summary
Open the completed Interview. Check its recording, transcript, page context, and processing state. If capture was interrupted or evidence processing failed, preserve that limitation in your analysis. No extracted Evidence does not prove that the experience was problem-free.
Start with moments relevant to the Study's goal. Listen before and after a quote so that a clipped sentence does not reverse the participant's meaning. Where screen recording is available, compare the explanation with the actual workflow.
2. Keep three kinds of information separate
This table is an illustrative analysis example, not a customer result.
| Kind | Example | What it supports |
|---|---|---|
| Participant report | “I thought inviting a teammate was required.” | The participant's stated understanding. |
| Observed behavior | The participant pauses on the invitation screen and leaves setup. | The captured sequence, not its hidden cause. |
| Interpretation | An optional invitation may appear mandatory. | A hypothesis to compare with the interface and other source moments. |
If a quote is missing, do not turn an observed pause into “the user was confused.” If the page was not captured, do not describe an inferred interface state as something the recording proves.
3. Group by the problem, not just the wording
Compare task, user context, expected outcome, obstacle, and consequence. Two mentions of “setup” may describe unrelated problems. Different words can describe the same obstacle.
For example, an invitation screen that appears mandatory is different from an invitation email that never arrives. Grouping both as “fix invitations” hides the decision you need to make.
UserTold can group related Evidence into draft Findings. Open the linked moments and correct, split, or dismiss a grouping when the sources do not support one coherent problem. Repeated quotes from the same episode are not independent participants.
4. Look for counter-evidence
Review smooth completions as well as struggling moments. Ask:
- Did another participant understand the same screen?
- Were the users doing the same task, with the same permissions and product version?
- Did an earlier instruction influence what the participant expected?
- Is an existing product capability already solving the problem?
- Could a capture gap explain the apparent sequence?
Disagreement is useful. It may narrow a Finding to a specific situation instead of disproving the experience or justifying a broad redesign.
5. Write a Finding with a clear boundary
Use this review structure:
Problem: What prevented the intended progress?
Context: Who was doing which task, and under what conditions?
Evidence: Source moments, quotes, behavior, and timestamps.
Interpretation: What might explain those moments?
Counter-evidence: Where did the workflow work, or the explanation differ?
Unknowns: What does the record not establish?
Next decision: Investigate further, defer, dismiss, or consider a change.
Do not treat an extraction confidence score as the probability that a proposed fix will work. It does not establish prevalence, revenue impact, or engineering priority.
6. Review before handing off
A project-aware human or agent checks the Finding against its Evidence and the current product. Marking it reviewed does not send it to an external tracker. Make a separate, explicit decision to send it to Linear intake or GitHub delivery.
See prioritizing fixes with evidence for that decision and interviews to issues for the handoff.
Can AI analyze the whole interview for me?
AI can help extract relevant moments and organize material. You still need to verify source attribution, ambiguous statements, grouping, and the resulting product interpretation. A good workflow makes that verification easy instead of hiding it behind a polished summary.
The AI interviewer also uses a running evidence summary for a planned live debrief. That supports follow-up questions during the session; the post-interview extraction described here is a separate step.
What if I only have one interview?
Record the specific problem and its limits. One interview can expose a reproducible defect or an important experience. It cannot establish that most users share it. Run another focused Study when the uncertainty matters to the decision; use the research templates to choose the next task.