Discovery Frameworks
Structured approaches to problem discovery and analysis
Your Progress
Section 4 of 5Structured Discovery
Frameworks bring structure to discovery. They help you dig deeper, stay systematic, and avoid missing critical insights.
No single framework fits all situations. Learn multiple frameworks and apply the right one for each discovery challenge.
Discovery Frameworks
Discovery Frameworks
❓5 Whys
Dig to the root cause by asking "why" five times
Understanding why a problem exists
- 1.Observe a problem or symptom
- 2.Ask "why does this happen?"
- 3.For each answer, ask "why?" again
- 4.Repeat 5 times to reach root cause
- 5.Address the root, not symptoms
Users abandon checkout → Why? Shipping is expensive → Why? Only one carrier → Why? Haven't integrated others → Root: Need more shipping options
When to Use Each Framework
Early Discovery
- • 5 Whys → Root cause analysis
- • Problem Statement Canvas → Definition
- • Customer Forces → Understand switching
Mid-Late Discovery
- • Opportunity Solution Tree → Ideation
- • Prioritization Matrix → Decision-making
- • Problem Brief → Documentation
End-to-End Discovery Process
Discovery Process
A 4-phase process for systematic problem discovery
Phase 1: Listen
1-2 weeksGoal: Understand user context and surface problems
- •10-15 user interviews
- •Support ticket analysis
- •Session recording review
- •Competitor user research
List of 20-30 potential problems
Move to qualification
Frameworks Are Tools, Not Rules
Don't rigidly follow frameworks. Adapt them to your context, combine them creatively, and focus on learning truth—not checking boxes.
Key Takeaways
- •Use 5 Whys to find root causes, Problem Statement Canvas to define clearly, and Opportunity Solution Tree to generate ideas.
- •Follow a 4-phase process: Listen → Qualify → Validate → Document for systematic discovery.
- •Frameworks bring structure but adapt them—focus on learning, not rigid process adherence.
- •Discovery takes 4-6 weeks total but saves months of building the wrong thing.