Yes. Every guide is free to read, with no account and no credit card. If we ever charge for something, it will be a product — never the library.

How long does validating an idea take?

Most founders get to a defensible verdict in two to four weeks: a dozen interviews, three tested assumptions, and one scored decision.

What if the verdict says pivot?

Then you saved months. The pivot guide walks you through which part to keep — usually the customer, rarely the feature.

Do I need a technical co-founder to use this?

No. Everything here happens before code: conversations, evidence, and one honest score.

The complete guide. It's one long read that links out to jobs & journeys, the evidence engine, personas and the launch kit.

How to Synthesize Interview Data Into Actionable Product Insights

You've done 15 interviews. You have hundreds of notes, recordings, transcripts.

Now what?

Most founders stare at the pile of data and feel overwhelmed. They don't know how to extract signal from the noise.

This guide walks you through turning raw interview data into concrete product decisions.

The Synthesis Process: From Raw Data to Insight

The process has 5 steps:

Organize: Compile all interview data in one place
Tag: Mark patterns and themes as you read
Cluster: Group similar observations together (affinity mapping)
Rank: Prioritize patterns by frequency and importance
Translate: Convert patterns into product implications

Let's walk through each.

Step 1: Organize Your Data

Create a simple spreadsheet with columns for each interview:

Interview #	Name	Role	Company	Problem Stated	Current Solution	Workaround	Urgency (1-10)	Mentions [Topic A]	Mentions [Topic B]	Would Pay
1	Sarah	VP Mktg	Series B SaaS	"Can't correlate retention to features"	Mixpanel + GA	Manual pivot tables	8	✓		$200-300
2	David	Analytics Mgr	Mid-market	"Spend 4 hours/week on reports"	Looker	Spreadsheets	7	✓	✓	$100-150
etc.

Now you can:

Scan a row and see one person's story
Scan a column and see where the consensus is
Quickly identify who has similar patterns

Step 2: Tag Your Data

As you read through interview notes, tag observations. Tags are keywords that describe what someone said.

Common tags:

#problem-[X]: Specific problem mentioned
#workaround-[X]: Current solution or hack
#frustration-[X]: Something that specifically bothers them
#urgent: High urgency
#nice-to-have: Lower priority need
#willingness-to-pay: Explicit pricing signal
#decision-maker: This person has buying authority
#blocker: A potential deal-breaker

Example from an interview: "We spend about 3-4 hours a week manually reconciling data from three different tools. #problem-data-silos #frustration-manual-work #workaround-spreadsheets It's not a huge priority for us since ... it only happens quarterly. #nice-to-have Our CEO cares more about accuracy. #decision-maker-cares-about-accuracy I'd pay maybe $50-100 a month. #willingness-to-pay"

Once you tag everything, you can search for tags and see pattern frequency.

Step 3: Affinity Mapping (Clustering)

Affinity mapping is where you group similar observations into themes.

Simple affinity mapping (for 1-2 people): Print interview notes or open them in Google Docs. Highlight similar themes with the same color.

Sophisticated affinity mapping (for teams): Create digital "sticky notes" (Miro, Figma, or even a Google Doc) where each observation is a card. Then drag cards into groups.

How to group:

Read one note/quote at a time
Ask: "What theme does this fit into?"
Create clusters: "Workflow friction," "Integrations," "Trust/Security," "Price sensitivity," etc.
Move similar observations into the same cluster

After clustering, you might find groups like:

Cluster A: Data integration is the top frustration (7/15 people)
Cluster B: Reporting takes too long (9/15 people)
Cluster C: They don't trust automatic categorization (5/15 people)
Cluster D: Price sensitivity at $50-100/month (8/15 people)

Step 4: Rank by Frequency and Importance

Not all patterns are equal. Rank by:

Frequency: How many people mentioned this?
Intensity: How strongly did they feel about it?
Urgency: Is this blocking them today or a future problem?

Ranking matrix:

Theme	# Mentions	Intensity	Urgency	Priority
Data integration	12/15	High	High	P0
Reporting speed	9/15	Medium	Medium	P1
Automatic categorization falters	5/15	High	Low	P2
No Salesforce integration	6/15	Medium	Medium	P1

P0 = Build first P1 = Build second P2 = Build later P3 = Don't build (or revisit)

Step 5: Translate Into Product Implications

Once you've ranked, translate each finding into a product requirement:

Interview finding (P0): "12/15 people struggle with data silos. They manually combine data from 3-5 tools weekly. It's error-prone and takes 2-3 hours."

Product implication: "Build integrations with top 5 tools [GA, Mixpanel, Salesforce, Stripe, Hubspot]. Auto-sync data hourly. Goal: Reduce manual data combining from 3 hours to 15 minutes."

Feature prioritization:

Integrate with top 3 tools (Salesforce, GA, Mixpanel) — 3 weeks
Add syncing automation — 2 weeks
Build unified dashboard view — 3 weeks

Real Example: From Raw Data to Roadmap

Raw data from 15 interviews:

12/15 say "data integration is a pain"
9/15 say "reporting takes forever"
6/15 mention "Salesforce integration specifically"
8/15 would pay $100-200/month
5/15 say "I need it to connect to my existing tools"

Affinity clusters:

Data silos: Multiple sources (GA, Mixpanel, Salesforce, Stripe) don't talk
Reporting friction: Custom reports take hours
Integrations missing: Specific gaps (Salesforce, Hubspot, Stripe)

Prioritization:

P0: Salesforce + GA + Looker integration (most mentioned)
P1: Auto-reporting dashboard
P2: Expand to more integrations

Translated to roadmap:

Weeks 1-4: Salesforce + GA connectors, hourly sync
Weeks 5-6: Dashboard with pre-built report templates
Weeks 7+: Additional integrations, custom report builder

This roadmap is driven by data, not guessing.

Tools for Synthesis

For startup/solo:

Google Sheets (tracking)
Google Docs (notes + tagging)
Miro (affinity mapping)

For teams:

Airtable (structured data + multiple views)
Miro (collaborative affinity mapping)
Dovetail (purpose-built interview analysis)

Most founders use Google Sheets + Miro. It's free and effective.

Common Mistakes

Mistake #1: Over-interpreting small sample sizes

"2 people mentioned X, therefore X is important"
Fix: Look for patterns across 30%+ of interviews. 2/15 is an outlier.

Mistake #2: Missing the underlying need

Observation: "They want better charts."
Actual need: "They can't explain data to their CEO."
Fix: Dig deeper. Ask "Why?" until you find the real job.

Mistake #3: Weighting recent interviews too heavily

Your last 3 interviews anchor your thinking
Fix: Synthesize data from all interviews equally

Mistake #4: Not tracking intensity alongside frequency

"5 people mentioned this" could mean 5 casual mentions or 5 desperate pleas
Fix: Track both frequency (how often) and intensity (how much they care)

The Synthesis Workflow

After each interview: Transcribe or summarize notes within 24 hours. Tag as you go.
After 5-7 interviews: Do a preliminary affinity map. Any patterns emerging?
After 10-15 interviews: Full synthesis and ranking.
Output: Prioritized product roadmap + personas

Connection to Research Chain

Interview synthesis is the bridge between customer research → and building your MVP →.

Without synthesis, research is just data. With it, research becomes action.

Ready to synthesize?

The beauty of this process is that it's simple once you start. Most founders find that after one affinity mapping session, patterns jump out immediately.

Use Edmired to organize interview data, run affinity mapping, and extract product prioritization in one place. Join the beta.