Problem Discovery & User Thinking
Finding Problems Worth Solving
The most expensive bug in software isn't a crash — it's building the wrong thing. Problem discovery is the skill of figuring out what to build before you build it.
The Discovery Mindset
Stop asking "What should we build?" and start asking:
- What's the user's actual workflow?
- Where do they get stuck, frustrated, or give up?
- What workarounds have they invented?
- What would "magical" look like for them?
User Interview Basics
You don't need a research team. You need 5 conversations and the right questions.
Good questions:
- "Walk me through the last time you did X"
- "What's the hardest part about doing X?"
- "What have you tried to solve this?"
- "If you had a magic wand, what would you change?"
Bad questions:
- "Would you use a feature that does X?" (leading)
- "Do you like our product?" (vanity)
- "What features do you want?" (wish list, not problems)
The Problem Statement Formula
A good problem statement follows this format:
[User segment] needs a way to [do something] because [insight/pain point].
Example: "Mid-level engineers applying for PM roles need a way to demonstrate product thinking because coding skills alone don't show business impact."
Signals That You've Found a Real Problem
- Users have built workarounds (spreadsheets, scripts, manual processes)
- Multiple users describe the same pain unprompted
- The problem connects to a measurable outcome (time saved, revenue, retention)
- Users get emotional when describing it (frustration, resignation)
Framework: Opportunity Score
Rate each problem you discover:
| Factor | Score (1-5) |
|---|---|
| Frequency — how often does this happen? | |
| Severity — how painful is it? | |
| Alternatives — are there good workarounds? (inverse) | |
| Market size — how many users are affected? |
Opportunity Score = Frequency × Severity × (6 - Alternatives)
Focus on problems with the highest opportunity score.
Exercise: Problem Safari
Pick an app you use daily. Spend 10 minutes using it and write down:
- Three moments of friction (however small)
- One workaround you've built
- The underlying problem behind each friction
Key Takeaway: The best product ideas come from observing behavior, not asking for feature requests.