Systematically validate your business hypotheses before building anything. Master Steve Blank's Customer Development methodology that became the foundation of Lean Startup and YC's approach.

• Starting a new venture to avoid building something nobody wants
• Before writing a line of code to validate problem-solution fit
• Pivoting decisions to systematically test new directions
• Early-stage fundraising to prove market validation
• Product roadmap planning to prioritize based on validated customer needs
• Entering new markets to understand unfamiliar customer segments

1. Documents business hypotheses - Turns assumptions into testable statements
2. Designs validation experiments - Creates tests that can prove you wrong
3. Structures customer conversations - Gets real insights, not false positives
4. Evaluates problem-solution fit - Determines if you should proceed, pivot, or stop
5. Creates learning roadmap - Prioritizes what to validate first
6. Tracks validation progress - Maintains evidence-based decision making

• P1: Fatal if wrong + Low confidence → Validate FIRST
• P2: Major if wrong + Low/Med confidence → Validate SOON
• P3: Minor if wrong OR High confidence → Validate LATER

• Customer Interviews (Problem Discovery)
• Solution Interviews (Solution Validation)
• Landing Page Test (Demand Validation)
• Concierge MVP (Solution Validation)
• Smoke Test (Demand Validation)

• Validated: 8+ of 10 customers describe this exact problem unprompted
• Invalidated: Fewer than 5 of 10 mention this problem

• Minimum: [Number] customers
• Target segment: [Description]

• Start: [Date]
• End: [Date]
• Go/No-Go Decision: [Date]

---

1. Context (5 min): Their role, background, day-to-day
2. Problem Exploration (15 min): Deep dive into the problem area
3. Existing Solutions (5 min): What they use today
4. Impact (5 min): How the problem affects them
5. Wrap-up (5 min): Referrals, next steps

• "Tell me about your biggest challenge with [area]..."
• "Walk me through the last time you dealt with [problem]..."
• "What solutions have you tried? What worked/didn't work?"
• "How much time/money does this cost you?"
• "If this magically disappeared, what would change?"

• Pitch your solution
• Ask leading questions
• Talk more than 30% of the time
• Ask "would you use/pay for..."

• You've talked to 10+ potential customers
• Clear problem patterns emerged
• Problems are severe and frequent enough
• Customers are actively seeking solutions

1. Recap (3 min): Confirm the problem you heard
2. Solution Demo (10 min): Show concept/prototype
3. Reaction (10 min): Their honest feedback
4. Commitment (5 min): Would they try/buy/refer?

• "Does this solve the problem you described?"
• "What's missing?"
• "What would you pay for this?"
• "Would you be willing to pilot this?"
• "Who else should see this?"

---

"I want to build HR onboarding software for mid-size companies. Help me set up Customer Discovery."

• Target: 15 HR managers at 100-500 employee companies
• Method: 30-minute phone interviews
• Questions:
  1. "Walk me through what happens when you hire someone..."
  2. "What's the biggest headache in that process?"
  3. "How much time does onboarding take per new hire?"
  4. "What tools are you using today?"
  5. "What's the cost when onboarding goes poorly?"

• Validated if: 10+ of 15 describe manual, time-consuming process; 8+ mention specific pain points
• Invalidated if: Most say "onboarding is fine" or <4 hours per hire

Opening: "I'm researching how mid-size companies handle employee onboarding.
Not selling anything - just learning. Mind if I ask some questions?"

Problem Exploration:
1. "When you hired your last employee, walk me through the onboarding process..."
2. "What took the most time?"
3. "Where do things typically go wrong?"
4. "Tell me about a time onboarding didn't go well..."

Current State:
5. "What tools or systems are you using for this?"
6. "What do you like about your current process?"
7. "What's frustrating about it?"

Impact:
8. "How does onboarding quality affect employee retention?"
9. "If you could wave a magic wand, what would change?"

Close:
10. "Who else should I talk to about this?"
11. "Can I follow up in a few weeks to share what I'm learning?"

"I did 12 customer discovery interviews. Here's my summary. Evaluate my progress."

• 12 interviews with working parents, ages 30-45
• 10/12 said they want to exercise more
• 8/12 said lack of time is the main barrier
• 6/12 have tried fitness apps before
• Only 2/12 are currently paying for any fitness solution
• 4/12 said they'd "probably" use a new app

• Strong problem confirmation (want to exercise, no time)
• Consistent pattern across interviews

• Only 17% paying for anything (low willingness to pay)
• "Probably use" is weak signal (opinions, not commitment)
• 6 tried apps, only 2 still paying (high churn)

• How severe is the pain? (scale 1-10)
• What have they tried recently?
• What would they pay? (past behavior, not predictions)

• People SAY they want this but don't PAY for it
• High awareness but low conversion/retention
• "Nice to have" not "must have"

1. "Tell me about a fitness product you actually paid for and kept using..."
2. "What made you stop using [previous app]?"
3. "What's different about the 2 of you who are paying now vs. when you weren't?"
4. "If I told you this app costs $20/month, what's your reaction?"
5. "What would make fitness a MUST instead of NICE TO HAVE?"

"Problem validated: Small business owners hate bookkeeping. But when I showed my automated bookkeeping tool, response was lukewarm. 3 of 10 were excited. Should I pivot?"

1. Who were the 3 excited customers?
   • What made them different?
   • Same problem, different intensity?
   • Different sub-segment?
2. Why were 7 NOT excited?
   • Wrong solution to right problem?
   • Right solution, wrong positioning?
   • Problem not severe enough for them?
   • Already have adequate solution?
3. What specifically was lukewarm?
   • "Too complex"
   • "Already have something"
   • "Doesn't solve my real problem"
   • "Price too high"

┌─────────────────────────────────────────────────────────┐
│                 SOLUTION FAILED                          │
│                                                          │
│  Is the problem still validated?                         │
│  └── YES → Solution Pivot (keep problem, change solution)│
│                                                          │
│  Were some customers excited?                            │
│  └── YES → Segment Pivot (narrow to excited segment)     │
│                                                          │
│  Did feedback suggest different problem?                 │
│  └── YES → Problem Pivot (keep customer, find new problem)│
│                                                          │
│  Is there any signal at all?                             │
│  └── NO → Consider stopping or major pivot               │
└─────────────────────────────────────────────────────────┘

1. Interview the 3 excited customers deeply
   • What specifically excited them?
   • What would they pay?
   • Would they commit to pilot?
2. Understand the 7 "no"s
   • What would have made them excited?
   • What are they using instead?
3. Consider these pivots:
   • Segment Pivot: Target the excited segment only
   • Solution Pivot: Same problem, different solution (maybe simpler?)
   • Channel Pivot: Same solution, different delivery
4. Before building anything:
   • Get 3 paying pilots or LOIs
   • "I'll build this if you prepay $X"

• Business Model Canvas hypotheses documented
• P1 hypotheses identified (highest risk)
• Target customer segment defined
• Interview questions drafted
• 15+ potential interviews scheduled

• Committed to learning, not selling
• Ready to hear "your idea is wrong"
• Willing to pivot based on evidence
• No code written yet (or willing to throw away)

• 2-4 weeks allocated for discovery
• Note-taking system ready
• Team aligned on validation criteria

---

• Interviews completed: __/15
• Problem confirmed: __%
• Solution fit (if applicable): __%
• Commitments received: __

---

• PROCEED: Build MVP / Start selling
• ITERATE: More interviews needed, adjust approach
• PIVOT: Change [customer/problem/solution]
• STOP: No viable market here

• Structuring persuasive content
• Applying copywriting frameworks
• Creating draft variations
• Analyzing competitor approaches

• Guarantee conversion rates
• Replace brand voice development
• Know your specific audience
• Make final approval decisions

• Blank, Steve. "The Four Steps to the Epiphany" (2005) - Original methodology
• Blank, Steve & Dorf, Bob. "The Startup Owner's Manual" (2012) - Expanded playbook
• Ries, Eric. "The Lean Startup" (2011) - Build-Measure-Learn context
• Fitzpatrick, Rob. "The Mom Test" (2013) - Interview techniques
• Osterwalder, Alex. "Business Model Generation" (2010) - BMC framework
• Maurya, Ash. "Running Lean" (2012) - Lean Canvas approach

• mom-test - Interview techniques for honest feedback
• lean-canvas - One-page business model documentation
• jobs-to-be-done - Understanding customer progress
• problem-interview - Deep dive on problem discovery
• solution-interview - Testing solution fit