Thematic Synthesis & Evidence-Based Insights

After conducting 5 to 10 user interviews, you are left with hours of audio and pages of handwritten notes. The fatal mistake is immediately writing an executive summary based on what you remember.

The Atomic Evidence Process:

1. Extract Single Observations: Transcribe distinct user quotes, observed struggles, or emotional reactions onto individual sticky notes.
2. Preserve the User's Voice: Write verbatims ('I couldn't tell if my file was encrypted') rather than team interpretations ('User wants an encryption badge').
3. Tag Metadata: Attribute each note to the participant ID (P1, P2) so you can verify breadth across participants.

When grouping sticky notes, teams often fall into the Topic Bucket Trap:

• 'Search', 'Navigation', 'Account Settings'

Topic buckets organize nouns, but they generate zero insights. An insight is an explanatory claim about user behavior.

Transforming Buckets into Claims:

• Bucket: 'Billing' (Passive label, no decision power)
• Insight Claim: 'Freelancers delay upgrading because invoice terms are withheld until credit card entry.' (Clear cause, effect, and actionable design intervention).

Research that does not change decisions is wasted budget. To transition from insight to action, frame findings using the Opportunity Matrix:

1. User Problem: What friction does the user experience?
2. Evidence Base: Which participants exhibited this behavior and in what context?
3. Business Impact: How does this friction harm retention, conversion, or support costs?
4. How Might We: Open-ended generative questions that invite cross-functional engineering and design collaboration.