Problem Validation

Confirming that the problem exists, people care about it, and they'll pay to solve it, before building anything.

Why Problem Validation Matters

The #1 startup killer: Building something nobody wants.

Most founders:

1. Fall in love with their solution
2. Build for months
3. Launch to crickets
4. Realize the problem wasn't real or painful enough

Better approach:

1. Validate the problem first
2. Understand it deeply
3. Then build the solution
4. Launch to waiting customers

The insight: If the problem is real and painful, any decent solution will sell. If the problem isn't real, even a great solution won't.

The Mom Test

The core principle: Don't ask people if your idea is good. Ask about their life.

Bad Questions (Get Lies)

❌ "Would you use an app that helps you budget?" ❌ "Do you think this is a good idea?" ❌ "Would you pay for this?" ❌ "What features would you want?"

Why they're bad:

• Hypothetical (people are bad at predicting future behavior)
• Leading (people want to be nice)
• About your idea (not their problem)
• Generic (no useful data)

Good Questions (Get Truth)

✅ "Tell me about the last time you tried to budget." ✅ "What's the hardest part about managing money?" ✅ "How do you currently solve this problem?" ✅ "What have you tried in the past?" ✅ "How much does this problem cost you?"

Why they're good:

• Specific past behavior (factual)
• Open-ended (no leading)
• About their life (not your solution)
• Reveals real pain (or lack thereof)

The Interview Framework

Goal

Understand:

• Do they have the problem?
• How painful is it?
• What do they currently do?
• Would they pay to solve it?

Not:

• Do they like your solution?
• What features do they want?
• Would they use your product?

Structure (30-45 minutes)

1. Introduction (5 min)

• Who you are
• Why you're talking to them
• Permission to record
• Emphasize: You want honest feedback, not validation

2. Their Context (10 min)

• What's their role/situation?
• What does a typical day look like?
• What are their main responsibilities?

3. Problem Discovery (15 min)

• "Tell me about the last time [problem scenario]"
• "What's the hardest part about [process]?"
• "What have you tried?"
• "How do you currently handle this?"
• "What frustrates you most?"

4. Current Solutions (10 min)

• "What tools/methods do you use now?"
• "What works about them?"
• "What doesn't work?"
• "What workarounds have you created?"
• "How much do you spend on this?"

5. Prioritization (5 min)

• "On a scale of 1-10, how big a problem is this?"
• "What are your top 3 problems in [domain]?"
• "If you could wave a magic wand..."

6. Close

• "Who else should I talk to?"
• "Can I follow up?"
• "Would you be interested in testing an early solution?"

Critical Rules

Don't pitch your solution

• The moment you pitch, you get polite lies
• They'll try to make you feel good
• You learn nothing

Talk less, listen more

• You should talk 20%, they talk 80%
• Silence is powerful, let them fill it
• Avoid leading questions

Take notes obsessively

• Exact phrases matter
• Patterns emerge across interviews
• You'll forget details quickly

Record if possible

• Ask permission first
• Captures nuance you'll miss
• Lets you focus on conversation

What You're Listening For

Strong Signals (Problem Is Real)

✅ They describe the problem before you mention it ✅ They've tried multiple solutions ✅ They've spent money addressing it ✅ They get emotional describing it ✅ They've built workarounds/hacks ✅ It's a frequent problem (weekly or more) ✅ They can quantify the cost/impact ✅ They ask when your solution will be ready

Weak Signals (Problem Might Not Be Real)

⚠️ They say "that's interesting" (means nothing) ⚠️ They need prompting to describe the problem ⚠️ They haven't tried solving it ⚠️ They shrug when asked about priority ⚠️ They can't remember last time it happened ⚠️ They say "nice to have" not "must have"

Red Flags (Problem Isn't Real)

🚩 They don't actually have this problem 🚩 Current solution is "good enough" 🚩 They wouldn't pay to solve it 🚩 It's a low-priority problem 🚩 They only care when you bring it up 🚩 Problem happens rarely 🚩 They can't explain why it matters

Finding Interview Subjects

Goal: Talk to 30-50 People

Don't interview:

• Friends and family (too biased)
• People trying to be nice
• People with no budget authority

Do interview:

• People with the problem
• People who would pay
• Decision-makers
• Current users of competitor solutions

Where to Find Them

1. Your Network (First 5-10)

• LinkedIn connections
• Former colleagues
• Industry contacts
• Second-degree connections

2. Cold Outreach (Next 20-30)

• LinkedIn messages
• Twitter DMs
• Industry Slack/Discord
• Reddit communities
• Email from company websites

3. Communities (Next 10-20)

• Industry conferences
• Online forums
• Meetups
• Professional associations
• Facebook groups

The Cold Outreach Template

Subject: Quick question about [their domain]

Body:

Hi [Name],

I'm researching challenges that [job title] face with [problem domain]. 
I noticed you work in this area and would love to hear about your experience.

Would you have 20 minutes for a call? I'm not selling anything, just 
trying to understand the space better.

Thanks,
[Your Name]

Why it works:

• Specific (not spam)
• Respects their time (20 min)
• Not selling (safe)
• Appeals to expertise (flattering)

Response rate: Expect 10-20%. Send 100 messages to get 20 interviews.

Interview Script Template

Opening: "Thanks for taking the time. I'm researching [problem domain] and trying to understand the challenges people face. I'm not selling anything, I genuinely want to learn from your experience. Is it okay if I record this for my notes?"

Context: "Can you tell me a bit about your role and what a typical day looks like?"

Problem discovery: "Tell me about the last time you [relevant scenario]." "What made that difficult?" "How did you handle it?" "How often does this come up?"

Current solutions: "What tools or methods do you currently use for [problem]?" "What do you like about [current solution]?" "What frustrates you about it?" "Have you tried alternatives?" "How much do you spend on this currently?"

Prioritization: "Of all the challenges you face with [domain], where does this rank?" "If you could fix one thing about [process], what would it be?"

Close: "This has been super helpful. Who else do you think I should talk to?" "Would it be okay if I follow up as I learn more?" "If I built something to address this, would you be interested in testing it?"

Analyzing Interview Data

After Each Interview

Immediately write:

• What surprised you?
• What was the biggest pain point?
• Exact quotes that stood out
• What they currently spend
• Whether problem is real/painful enough

After 10 Interviews

Look for patterns:

• Which problems came up repeatedly?
• Which problems are most painful?
• Which have people spending money?
• Which are people actively trying to solve?
• What language do they use? (Use their words, not yours)

After 30 Interviews

Synthesize:

• Create customer persona
• Rank problems by frequency and intensity
• Document current solutions and their gaps
• Identify most promising opportunity
• Calculate willingness to pay

The Problem Validation Matrix

Score each: Weak = 1, Medium = 2, Strong = 3

Results:

• 15-18: Strong problem, proceed to solution validation
• 10-14: Medium problem, might work but risky
• 6-9: Weak problem, find a better one

Success Criteria

After 30 interviews, you should see:

✅ 40%+ say this is a top-3 problem

• If yes: Problem is validated
• If no: Problem isn't painful enough

✅ 60%+ have tried to solve it

• If yes: People care enough to act
• If no: Problem might not be that bad

✅ Average willingness to pay is $X/month

• Calculate from: "What would solving this be worth to you?"
• Discount by 3x (people overestimate)
• Need to be higher than your projected CAC

✅ Clear pattern in feedback

• Same problems mentioned repeatedly
• Similar language used
• Consistent pain points
• Agreement on what's missing

Common Mistakes

Mistake 1: Asking Leading Questions

❌ "Don't you hate how hard it is to [problem]?" ✅ "Tell me about your experience with [process]"

Mistake 2: Pitching Too Early

❌ Describing your solution in minute 5 ✅ Never mentioning your solution until asked

Mistake 3: Talking to the Wrong People

❌ Interviewing anyone who will talk ✅ Screening for target customer profile

Mistake 4: Not Taking Notes

❌ Trusting your memory ✅ Writing exact quotes during call

Mistake 5: Stopping at 5 Interviews

❌ "Everyone I talked to loved it!" ✅ Talk to 30-50 people minimum

Mistake 6: Ignoring Negative Feedback

❌ "They just don't get it" ✅ "Why don't they have this problem?"

Mistake 7: Confusing Interest With Commitment

❌ "That sounds interesting" = validation ✅ "I've tried 3 solutions and spent $2,000" = validation

Red Flags to Kill the Idea

Stop if you see:

🚩 Can't find people with the problem

• You've reached out to 100+ people
• Only 10% even have this problem
• Those who have it don't care

🚩 Problem exists but isn't painful

• "Yeah, it's annoying I guess"
• Ranks as priority #8 or lower
• Haven't tried to solve it
• Happens infrequently

🚩 Current solutions are good enough

• "I just use Excel, it's fine"
• "The free version works for me"
• Can't articulate what's missing
• Workarounds aren't that bad

🚩 Can't identify who would pay

• Users want it but can't pay
• Decision makers don't care
• Budget doesn't exist
• Purchase process is 12+ months

🚩 You're not finding consistent patterns

• Every person has different problem
• No common language
• Pain points vary widely
• Can't build for all of them

If you see 2+ red flags: Pivot or move to a different idea.

Moving to Solution Validation

If problem validation succeeds:

You now know:

• The problem is real and painful
• People have tried to solve it
• Current solutions are inadequate
• Target customers are reachable
• Rough willingness to pay
• The language customers use

Next step: Solution Validation (Chapter 3)

• Will YOUR solution work?
• Will people use it?
• Can you build it?
• Will they actually pay?

Before moving on:

• Document all findings
• Create customer persona
• Write problem statement
• List requirements based on interviews
• Prioritize features by mentioned pain

Problem Validation Checklist

• [ ] Conducted 30-50 customer interviews
• [ ] Interviewed only target customers (not friends/family)
• [ ] Asked about past behavior, not hypotheticals
• [ ] Took detailed notes on every interview
• [ ] Identified clear patterns across interviews
• [ ] 40%+ say this is a top-3 problem
• [ ] 60%+ have tried to solve it
• [ ] Clear willingness to pay emerged
• [ ] Documented the language customers use
• [ ] Created target customer persona
• [ ] Listed gaps in current solutions
• [ ] No major red flags appeared
• [ ] Got commitments to test early solution
• [ ] Have list of next 20 people to talk to

Resources

Books:

• The Mom Test by Rob Fitzpatrick (essential reading)
• Talking to Humans by Giff Constable
• The Lean Startup by Eric Ries

Templates:

• Customer interview script (above)
• Interview analysis spreadsheet
• Problem-solution fit canvas

Tools:

• Calendly (schedule interviews)
• Zoom/Google Meet (remote interviews)
• Otter.ai (transcription)
• Notion/Airtable (organize feedback)