Purpose
Guide product managers through a complete discovery cycle—from initial problem hypothesis to validated solution—by orchestrating problem framing, customer interviews, synthesis, and experimentation skills into a structured process. Use this to systematically explore problem spaces, validate assumptions, and build confidence before committing to full development—avoiding "build it and they will come" syndrome and ensuring you're solving real customer problems.
This is not a one-time research project—it's a continuous discovery practice that runs in parallel with delivery, typically 1-2 discovery cycles per quarter.
Key Concepts
What is the Discovery Process?
The discovery process (Teresa Torres, Marty Cagan) is a structured approach to exploring problem spaces and validating solutions before building. It consists of:
- Frame the Problem — Define what you're investigating and why
- Conduct Research — Gather qualitative and quantitative evidence
- Synthesize Insights — Identify patterns, pain points, and opportunities
- Generate Solutions — Explore multiple solution options
- Validate Solutions — Test assumptions through experiments
- Decide & Document — Commit to build, pivot, or kill
Why This Works
- De-risks product decisions: Tests assumptions before expensive builds
- Customer-centric: Grounds decisions in real customer problems, not internal opinions
- Iterative: Builds confidence progressively through small experiments
- Fast learning: Discovers "no-go" signals early, saves wasted effort
Anti-Patterns (What This Is NOT)
- Not waterfall research: Discovery runs continuously, not once before dev
- Not user testing: Discovery validates problems; testing validates solutions
- Not a substitute for shipping: Discovery informs delivery, doesn't replace it
When to Use This
- Exploring new product/feature areas
- Investigating retention or churn problems
- Validating strategic initiatives before roadmap commitment
- Continuous discovery (weekly customer touchpoints)
When NOT to Use This
- For well-understood problems (move to execution)
- When stakeholders have already committed to a solution (address alignment first)
- For tactical bug fixes or technical debt (no discovery needed)
Facilitation Source of Truth
When running this workflow as a guided conversation, use workshop-facilitation as the interaction protocol.
It defines:
- session heads-up + entry mode (Guided, Context dump, Best guess)
- one-question turns with plain-language prompts
- progress labels (for example, Context Qx/8 and Scoring Qx/5)
- interruption handling and pause/resume behavior
- numbered recommendations at decision points
- quick-select numbered response options for regular questions (include
Other (specify)when useful)
This file defines the workflow sequence and domain-specific outputs. If there is a conflict, follow this file's workflow logic.
Application
Use template.md for the full fill-in structure.
This workflow orchestrates 6 phases over 2-4 weeks, using multiple component and interactive skills.
Phase 1: Frame the Problem (Day 1-2)
Goal: Define what you're investigating, who's affected, and success criteria.
Activities
1. Run Problem Framing Canvas
- Use:
skills/problem-framing-canvas/SKILL.md(interactive - MITRE) - Participants: PM, design, engineering lead
- Duration: 120 minutes
- Output: Problem statement + "How Might We" question
2. Create Formal Problem Statement
- Use:
skills/problem-statement/SKILL.md(component) - Participants: PM
- Duration: 30 minutes
- Output: Structured problem statement with hypothesis
3. Define Proto-Personas (If Needed)
- Use:
skills/proto-persona/SKILL.md(component) - When: If target customer segment is unclear
- Duration: 60 minutes
- Output: Hypothesis-driven personas
4. Map Jobs-to-be-Done (If Needed)
- Use:
skills/jobs-to-be-done/SKILL.md(component) - When: If customer motivations are unclear
- Duration: 60 minutes
- Output: JTBD statements
Outputs from Phase 1
- Problem hypothesis: "We believe [persona] struggles with [problem] because [root cause], leading to [consequence]."
- Research questions: 3-5 questions to answer through discovery
- Success criteria: What would validate/invalidate the problem?
Decision Point 1: Do we have enough context to start research?
If YES: Proceed to Phase 2 (Research Planning)
If NO: Gather existing data first:
- Review support tickets, churn surveys, NPS feedback
- Analyze product analytics (drop-off points, usage patterns)
- Review competitor research, market trends
- Time impact: +2-3 days
Phase 2: Research Planning (Day 3)
Goal: Design research approach, recruit participants, prepare interview guide.
Activities
1. Prep Discovery Interviews
- Use:
skills/discovery-interview-prep/SKILL.md(interactive) - Participants: PM, design
- Duration: 90 minutes
- Output: Interview plan with methodology, questions, biases to avoid
2. Recruit Participants
- Target: 5-10 customers per discovery cycle (Teresa Torres: continuous discovery = 1 interview/week)
- Segment: Focus on personas from Phase 1
- Recruitment channels:
- Existing customers (email, in-app prompts)
- Churned customers (exit interviews)
- Cold outreach (LinkedIn, communities)
- Incentive: $50-100 gift card or product credit
- Duration: 2-3 days (parallel with Phase 1)
3. Schedule Interviews
- Format: 45-60 min per interview (30-40 min conversation + buffer)
- Timeline: Spread across 1-2 weeks
- Recording: Get consent, record for synthesis
Outputs from Phase 2
- Interview guide: 5-7 open-ended questions (Mom Test style)
- Participant roster: 5-10 scheduled interviews
- Synthesis plan: How you'll capture and analyze insights
Phase 3: Conduct Research (Week 1-2)
Goal: Gather qualitative evidence through customer interviews.
Activities
1. Conduct Discovery Interviews
- Methodology: From
skills/discovery-interview-prep/SKILL.md(Problem validation, JTBD, switch interviews, etc.) - Participants: PM + optional observer (design, eng)
- Duration: 5-10 interviews over 1-2 weeks
- Focus areas:
- Past behavior (not hypotheticals): "Tell me about the last time you [experienced this problem]"
- Workarounds: "How do you currently handle this?"
- Alternatives tried: "Have you tried other solutions? Why did you stop?"
- Pain intensity: "How much time/money does this cost you?"
2. Take Structured Notes
- Template:
- Participant: [Name, role, company size]
- Context: [When/where they experience problem]
- Actions: [What they do, step-by-step]
- Pain points: [Frustrations, blockers]
- Workarounds: [Current solutions]
- Quotes: [Verbatim customer language]
- Insights: [Patterns, surprises]
3. Review Support Tickets & Analytics (Parallel)
- Support tickets: Tag by theme (onboarding, feature confusion, bugs)
- Analytics: Identify drop-off points, feature usage, cohort behavior
- Surveys: Review NPS comments, exit surveys, feature requests
Outputs from Phase 3
- Interview transcripts: Recorded sessions + detailed notes
- Support ticket themes: Top 10 issues by frequency
- Analytics insights: Quantitative data on behavior (e.g., "60% abandon onboarding at step 3")
Decision Point 2: Have we reached saturation?
Saturation = same pain points emerge across 3+ interviews, no new insights
If YES (saturated after 5-7 interviews): Proceed to Phase 4 (Synthesis)
If NO (still learning new things): Schedule 3-5 more interviews
- Time impact: +1 week
Phase 4: Synthesize Insights (End of Week 2)
Goal: Identify patte