Problem Validation

Confirm the problem exists, people care about it, and they will pay to solve it, before you build anything.

Why Problem Validation Matters

The number-one startup killer: building something nobody wants.

Most founders:

1. Fall in love with their solution
2. Build for months
3. Launch to crickets
4. Realise the problem was not 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 is not real, even a great solution will not.

The Mom Test

The core principle from Rob Fitzpatrick's The Mom Test: do not 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 fail:

• Hypothetical (people are bad at predicting future behaviour)
• 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 is 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 work:

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

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 are talking to them
   • Permission to record
   • Make clear: you want honest feedback, not validation

2. Their context (10 min)

   • What is their role or 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 is 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 or methods do you use now?"
   • "What works about them?"
   • "What does not work?"
   • "What workarounds have you created?"
   • "How much do you spend on this?"

5. Prioritisation (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

Do not pitch your solution.

• The moment you pitch, you get polite lies
• They will 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 will forget details quickly

Record if possible.

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

What You Are Listening For

Strong Signals (Problem Is Real)

They describe the problem before you mention it
They have tried multiple solutions
They have spent money addressing it
They get emotional describing it
They have built workarounds and hacks
It is a frequent problem (weekly or more)
They can quantify the cost or 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 have not tried solving it
They shrug when asked about priority
They cannot remember the last time it happened
They say "nice to have" not "must have"

Red Flags (Problem Is Not Real)

They do not actually have this problem
Current solution is "good enough"
They would not pay to solve it
It is a low-priority problem
They only care when you bring it up
Problem happens rarely
They cannot explain why it matters

Finding Interview Subjects

Goal: Talk to 30-50 People

Do not 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 and 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]

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?"

Prioritisation:
"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 really 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?"

Analysing Interview Data

After Each Interview

Write immediately:

• What surprised you?
• What was the biggest pain point?
• Exact quotes that stood out
• What they currently spend
• Whether the problem is real and 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

Synthesise:

• Create customer persona
• Rank problems by frequency and intensity
• Document current solutions and their gaps
• Identify the 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, the problem is validated. If not, the problem is not painful enough.
• 60%+ have tried to solve it. If yes, people care enough to act. If not, the problem might not be that bad.
• Average willingness to pay is $X/month. Calculate from "what would solving this be worth to you?", then discount by 3x (people overestimate). The number must be higher than your projected CAC.
• Clear pattern in feedback: same problems mentioned repeatedly, similar language, consistent pain points, agreement on what is missing.

Common Mistakes

Mistake 1: Asking Leading Questions

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

Mistake 2: Pitching Too Early

Bad:  Describing your solution in minute 5
Good: Never mentioning your solution until asked

Mistake 3: Talking to the Wrong People

Bad:  Interviewing anyone who will talk
Good: Screening for target customer profile

Mistake 4: Not Taking Notes

Bad:  Trusting your memory
Good: Writing exact quotes during the call

Mistake 5: Stopping at 5 Interviews

Bad:  "Everyone I talked to loved it!"
Good: Talk to 30-50 people minimum

Mistake 6: Ignoring Negative Feedback

Bad:  "They just don't get it"
Good: "Why don't they have this problem?"

Mistake 7: Confusing Interest With Commitment

Bad:  "That sounds interesting" = validation
Good: "I've tried 3 solutions and spent $2,000" = validation

Red Flags to Kill the Idea

Stop if you see:

Cannot find people with the problem.

• You have reached out to 100+ people
• Only 10% even have this problem
• Those who have it do not care

Problem exists but is not painful.

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

Current solutions are good enough.

• "I just use Excel, it's fine"
• "The free version works for me"
• Cannot articulate what is missing
• Workarounds are not that bad

Cannot identify who would pay.

• Users want it but cannot pay
• Decision makers do not care
• Budget does not exist
• Purchase process is 12+ months

You are not finding consistent patterns.

• Every person has a different problem
• No common language
• Pain points vary widely
• Cannot 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

Before moving on:

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

Problem Validation Checklist

[ ] Conducted 30-50 customer interviews
[ ] Interviewed only target customers (not friends or family)
[ ] Asked about past behaviour, 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 (organise feedback)

Next Steps

Continue to 03-market-research.md to size the market, map the competition, and find your wedge.