Validate that the problem you want to solve is real, painful, and worth solving before building anything. Master Cindy Alvarez's structured approach to problem discovery interviews.

• Before solution interviews to confirm the problem exists
• Early customer discovery to understand the problem space
• Pivoting to find new problems worth solving
• Market expansion to understand problems in new segments
• Feature prioritization to validate which problems matter most
• Hypothesis testing to validate or invalidate problem assumptions

1. Structures problem exploration - Systematic approach to understanding pain points
2. Identifies problem severity - Distinguishes "nice to have" from "must solve"
3. Discovers existing solutions - Understands what people do today
4. Validates problem frequency - How often does this problem occur?
5. Finds problem context - When and where does the problem happen?
6. Generates solution hints - What would ideal look like?

• If fewer than [X%] mention this problem unprompted
• If the problem happens less than [frequency]
• If severity rating is below [threshold]
• If people aren't spending time/money to solve it

---

1. Understand the CONTEXT where the problem occurs
2. Measure the SEVERITY of the problem
3. Discover EXISTING SOLUTIONS they use
4. Identify FREQUENCY of the problem
5. Find the COST (time, money, emotion) of the problem

• "Tell me about your role and what you're responsible for..."
• "Walk me through a typical day/week..."
• Goal: Understand their world before diving into problems

• "What are the biggest challenges you face with [area]?"
• "Tell me about the last time [problem] happened..."
• "What was the hardest part about that?"
• "How often does this happen?"
• Goal: Deep dive into problem, frequency, severity

• "How do you handle this today?"
• "What have you tried in the past?"
• "What works? What doesn't?"
• "What do you wish existed?"
• Goal: Understand competitive landscape from customer view

• "How much time/money does this cost you?"
• "If this problem disappeared, what would change?"
• "Who else deals with this that I should talk to?"
• Goal: Quantify impact, get referrals

---

• "What's the most frustrating part of [area]?"
• "Walk me through the last time you dealt with [problem]..."
• "What keeps you up at night about [area]?"

• "How often does [problem] happen?"
• "When was the last time? The time before that?"
• "Is this daily? Weekly? Monthly?"

• "On a scale of 1-10, how painful is this?"
• "What happens if you don't solve this?"
• "How does this affect your [work/life/business]?"

• "How does it feel when this happens?"
• "What emotions come up when you deal with this?"
• "What would it mean to you to solve this?"

• "How do you handle this today?"
• "What tools/processes do you use?"
• "Walk me through your current workflow..."

• "What have you tried before?"
• "What worked? What didn't?"
• "Why did you stop using [previous solution]?"

• "If you had a magic wand, what would you change?"
• "What would the perfect solution look like?"
• "What would need to be true for this to be solved?"

• "How much time do you spend on this per week?"
• "How much does this cost you?" (direct and indirect)
• "What's the opportunity cost of not solving this?"

• "Is solving this a priority? Why/why not?"
• "What would make it urgent?"
• "Have you looked for solutions recently?"

• "How much time do you spend on this?"
• Convert to $ (hourly rate × time)

• Direct costs (tools, services, fixes)
• Indirect costs (opportunity cost, delays)

• Frustration level
• Impact on job satisfaction
• Stress and worry

• They brought up the problem before you asked
• They got emotional when describing it
• They've already spent money trying to solve it
• They can quantify the impact precisely
• They asked if you have a solution

• Only mentioned when directly asked
• Vague about impact ("it's kind of annoying")
• Never tried to solve it
• Can't quantify the cost
• No urgency in their voice

---

• "[Verbatim quote about the problem]"
• "[Quote about severity/impact]"

• Frustrated [ ] Stressed [ ] Resigned [ ] Energized when discussing
• No emotional reaction (weak signal)

• 7+ of 10 mentioned problem unprompted
• Average severity > 7/10
• Multiple people already spending on solutions
• Clear patterns in problem description
• Consistent emotional response

• Fewer than 5 of 10 recognize the problem
• Severity consistently < 5/10
• No one is actively trying to solve it
• Wide variance in problem descriptions
• "Nice to have" language dominates

• Mixed signals (some strong, some weak)
• Different sub-segments show different patterns
• Problem exists but may not be the ONE to solve

---

"I want to validate that marketing managers struggle with tracking campaign ROI across channels. Create a problem interview script."

1. "Tell me about your role. What are you responsible for?"
2. "How does your company measure marketing success?"
3. "What tools are in your marketing stack?"

1. "How do you handle this today? Walk me through your process..."
2. "What tools do you use for reporting?"
3. "What's good about your current approach?"
4. "What's frustrating about it?"
5. "Have you tried other solutions? What happened?"

1. "If you had perfect visibility into ROI, what would change?"
2. "Is solving this a priority for you right now? Why or why not?"
3. "What would need to be true for this to become urgent?"
4. "Who else on your team deals with this that I should talk to?"

• Listen for: emotional language, specific examples, quantified impact
• Red flags: vague answers, "it's fine," no urgency
• Strong signals: they've tried to solve it, they can quantify the cost

"I did 12 problem interviews about freelancer financial planning. Here's my summary. Is the problem validated?"

• 9/12 said they "should" be better at finances
• 6/12 mentioned tax season stress
• 4/12 currently use any tool
• Most said they use spreadsheets or nothing
• Average severity: 5.5/10
• Only 2 were actively looking for solutions

• People RECOGNIZE they have a problem (9/12)
• There's a specific pain point (tax season)
• Low tool adoption = opportunity exists

• Severity is too low (5.5 vs. 7+ target)
• Very few actively seeking solutions (2/12)
• Language was "should" not "must" (obligation, not urgency)

• The 6 who mentioned tax season stress: dig deeper
• Is there a specific trigger moment where it becomes urgent?
• "Walk me through what happened last April 14th..."
• Maybe the problem is "tax season panic" not "financial planning"

• The 2 actively seeking: who are they? What's different?
• High-earning freelancers (more at stake)?
• Freelancers who just got a tax surprise?
• Find the segment where severity IS 8+

• What else did they say was painful?
• Maybe financial planning isn't the problem
• Maybe "irregular income stress" or "late invoices" is more acute

1. Interview 5 more people who just went through tax season
2. Interview the 2 who were actively looking—understand why
3. Ask: "What's the MOST stressful financial moment you've had this year?"

"In my problem interviews, people say 'yeah, that's annoying' but I'm not sure if it's severe enough. How do I probe deeper?"

• Structuring audio production workflows
• Providing technical guidance
• Creating quality checklists
• Suggesting creative approaches

• Replace audio engineering expertise
• Make subjective creative decisions
• Access or edit audio files directly
• Guarantee commercial success

• Alvarez, Cindy. "Lean Customer Development" (2014) - Problem interview methodology
• Fitzpatrick, Rob. "The Mom Test" (2013) - Questioning techniques
• Blank, Steve. "The Four Steps to the Epiphany" (2005) - Customer development
• Torres, Teresa. "Continuous Discovery Habits" (2021) - Ongoing discovery

• mom-test - Questioning techniques for honest answers
• solution-interview - Next step after problem validation
• customer-discovery - Broader validation framework
• persona-generator - Understanding who has the problem
• jobs-to-be-done - Understanding the underlying need

• Mode: cyborg

name: problem-interview
category: validation
subcategory: customer-research
version: 1.0
author: MKTG Skills
source_expert: Cindy Alvarez
source_work: Lean Customer Development
difficulty: beginner
estimated_value: $1,500 customer research training
tags: [validation, interviews, customer-discovery, problems, startups, YC]
created: 2026-01-25
updated: 2026-01-25