You ran the interview. You took notes. Now what?
Most PMs dump interview notes into a Google Doc, tag a few themes, and move on. Three months later, nobody can find the insight that should have shaped the next feature.
The problem isn't that you don't talk to users. The problem is that conversations decay into anecdotes.
Pathmode's Evidence Board turns your conversations into structured, searchable, actionable evidence. Here's how.
The Method
Step 1: One Insight, One Card
The most common mistake is writing paragraph summaries. "Sarah had trouble with onboarding, mentioned she liked the dashboard, and asked about team features."
That's three signals crammed into one blob. Pull them apart:
| What you heard | Evidence type | Card |
|---|---|---|
| "I almost gave up during setup" | Friction | Setup flow causes drop-off |
| "The dashboard is the first thing I check every morning" | Quote | Dashboard is primary engagement surface |
| "Can my team see the same data I see?" | Request | Team visibility / shared access |
Each insight gets its own evidence card. One type, one source, one board.
The discipline: If you can't express it in one sentence, you haven't distilled it yet.
Step 2: Type It Correctly
Pathmode uses five evidence types. Interviews generate all of them, but the distribution tells you something:
| Evidence type | What it captures | Interview signal |
|---|---|---|
| Friction | Pain, struggle, failure | "I couldn't...", "It took me forever to...", "I gave up on..." |
| Quote | Exact words worth preserving | Emotional language, surprising framing, pithy summaries |
| Observation | Something you noticed, not something they said | Hesitation, confusion, workarounds they didn't mention |
| Metric | A number they gave you | "We spend 3 hours a week on...", "Only 2 out of 10 people..." |
| Request | Something they asked for | "Can it do...?", "I wish there was...", "What if you added..." |
š” Tip: Observations are the most underused type. What the user does matters more than what they say. If they described a task as "easy" but took four minutes to find the right button, that's a Friction and an Observation, not a positive signal.
Step 3: Resist the Urge to Solve
This is the hardest part for PMs. You hear a problem. You immediately know three ways to fix it. You want to write the solution into the evidence card.
Don't.
Evidence describes what is. Not what should be. The moment you inject a solution, you've biased every future reader of that card ā including yourself.
ā Wrong: "User can't find export ā we should add it to the toolbar"
ā Right: "User spent 2 minutes looking for export. Checked Settings, then Help, then found it under File menu."
The solution comes later, when you've seen the full pattern across multiple users. That's what Synthesize Intent is for.
Step 4: Tag the Source
Every card needs a source. Not "user interview" ā that's useless in two weeks. Be specific:
- Who: Role, segment, or anonymized ID ("Enterprise PM, Trial Day 3")
- When: Date of the interview
- Context: What you were testing or exploring
This matters when you're staring at a cluster of 8 evidence items and asking "is this pattern real or did I just talk to one angry user twice?"
Step 5: Board It Immediately
Process your notes the same day as the interview. Not next week. Not "when I have time." The day of.
Why? Because your memory of tone, hesitation, and body language is perishable. The difference between "she mentioned export" and "she visibly frustrated when trying to export" is context that evaporates within 48 hours.
A 30-minute interview should produce 5ā10 evidence cards. If you're getting fewer than 3, you're summarizing instead of decomposing.
The Payoff: Patterns You Can Act On
After 5ā8 interviews processed this way, your Evidence Board stops being a collection and starts being a map. You'll see:
- Clusters: Four people hit the same friction in onboarding ā that's a real problem
- Gaps: Everyone mentions collaboration but you have zero evidence on permissions ā that's your next research question
- Surprises: Users love a feature you were about to deprecate ā that's a strategy input
The clusters point to your next Intent Spec. The gaps point to your next round of interviews.
Anti-Patterns
ā The Transcript Dump: Pasting entire interview transcripts onto the board. Evidence is distilled signal, not raw data.
ā The Solution Interview: You asked leading questions ("Would you use a feature that...?") and now your evidence is contaminated with hypothetical demand. Evidence should capture real behavior and real pain.
ā The Batch Processor: You ran 12 interviews over two weeks and are now trying to process them all at once. Half the nuance is gone. Process same-day.
ā The Solo Board: Only you add evidence. Get your designer, your engineer, your support lead adding cards from their own sources. The best patterns emerge at the intersection of multiple perspectives.
Next Steps
- Run the play: After your next user interview, process the notes using this method and add evidence to your product area.
- Look for clusters: Once you have evidence from 5+ sources, switch to Stage View and start grouping. See Evidence Board 101 for the clustering technique.
- Synthesize: When a cluster is dense enough, synthesize it into an Intent Spec that your team can build against.