🎯 The Product Discovery Playground

Your interactive 30-minute crash course into Product Discovery. No fluff — just hands-on practice with real frameworks.

⏱️ ~30 min | 7 Modules | For PMs transitioning into Discovery
Module 1 of 7: Let us begin!
1
The Discovery Mindset Shift
From "Build it and they will come" to "Learn first, build later"

🧠 What is Product Discovery?

Product Discovery is the process of figuring out what to build before you build it. It is where you reduce uncertainty about problems, users, and solutions.

Core Principle: In Discovery, you are not validating your idea — you are discovering if there is a problem worth solving, and if your solution actually works.

🔄 The Big Shift: Delivery vs. Discovery

As a PM, you have probably lived in "Delivery mode." Here is how Discovery is different:

📦 Delivery Mode
• Focus on outputs
• Roadmaps with dates
• "When will it ship?"
• Success = on time
🔍 Discovery Mode
• Focus on outcomes
• Hypotheses to test
• "Should we build this?"
• Success = learning

✅ Quick Self-Assessment

Which of these best describes your current situation?

2
Problem Discovery
Finding problems worth solving (not solutions looking for problems)

🎯 The Problem Statement Canvas

Before brainstorming solutions, articulate the problem clearly. Use this framework:

When [situation], I want to [motivation], so I can [expected outcome], but [obstacle/frustration].

📝 Your Turn: Craft a Problem Statement

Think of a problem your users face. Fill in the blanks below.

🔍 Problem Discovery Techniques

🗣️ User Interviews
1-on-1 conversations focused on past behaviors. Ask "Tell me about the last time you..."
📊 Support Ticket Analysis
Mine support tickets, NPS verbatims, and churn surveys for recurring pain points.
🔬 Jobs-to-be-Done Interviews
Focus on the "job" the user hired your product to do.

💼 Mini Scenario: The Feature Request Trap

Your biggest customer asks for a "dark mode" feature. What do you do?

3
User Research & Personas
Understanding who you are building for (beyond demographics)

👤 The Persona Canvas

Forget age and job title. In Product Discovery, we care about behaviors, goals, and pain points.

📝 Build a Behavioral Persona

🎤 Interview Tips for PMs

The Mom Test Rules:
  • Talk about their life, not your idea
  • Ask about specific past experiences, not hypotheticals
  • Listen more than you talk (aim for 80/20)
  • "Tell me more about that" is your best friend

📋 Research Checklist

  • I have a clear research goal
  • I have recruited 5-8 participants
  • I have an interview guide with open-ended questions
  • I have planned how to synthesize findings
  • I have a note-taker or recording setup
4
Opportunity Scoring
Prioritizing what to explore (not everything is worth solving)

📊 The RICE Framework (Adapted for Discovery)

🎯 Reach
How many users experience this problem?
💡 Impact
How painful is this problem? (1-10)
✅ Confidence
How sure are we this is a real problem?
⚡ Effort to Learn
How hard is it to validate this?

🎮 Interactive Opportunity Scorer

🌳 The Opportunity Solution Tree

Outcome (top) → Opportunities (branches) → Solutions (leaves)

This keeps your team aligned on the desired outcome while exploring multiple paths.
5
Solution Ideation & Validation
Generating ideas and testing them cheaply

💡 Ideation Without Ego

🎯
Problem Validated
We know it is real
→
💡
Ideate Solutions
Many ideas, no attachment
→
🧪
Validate Solution
Does it actually work?

🧪 Validation Techniques (Cheapest to Most Expensive)

📝
Concierge Test — Do it manually for one user
Cost: $0 | Time: 1-2 days | Confidence: Low-Medium
🎨
Mockup/Wizard of Oz Test — Fake the backend, test the UI
Cost: $ | Time: 3-5 days | Confidence: Medium
🛠️
Prototype Test — Clickable prototype with real users
Cost: $$ | Time: 1-2 weeks | Confidence: Medium-High
🚀
Pilot/MVP — Build the real thing for a small group
Cost: $$$ | Time: 2-4 weeks | Confidence: High

💼 Mini Scenario: The Dashboard Dilemma

Your team wants to build an analytics dashboard. Users say they "want more visibility." What is the cheapest way to validate?

6
Prototype & Test
Running effective experiments and learning from them

🧪 The Experiment Canvas

We believe that [doing this/building this feature]
for [these users/personas]
will achieve [this outcome]
We will know we are right when we see [this signal/metric]
within [this timeframe]

📝 Draft Your Experiment

📏 Success Metrics vs. Guardrail Metrics

⚠️ Common Trap: Only measuring success metrics. You also need guardrail metrics to ensure you are not breaking things.
✅ Success Metrics
• Task completion rate
• Time to complete
• User satisfaction (CSAT)
• Feature adoption
🛡️ Guardrail Metrics
• Error rates
• Support tickets
• Page load time
• Churn/retention

🎯 Usability Testing in 5 Steps

  1. Define tasks — Give users realistic scenarios, not instructions
  2. Recruit 5 users — You do not need 50; 5 will find 85% of issues
  3. Observe silently — Resist the urge to help!
  4. Note behaviors, not opinions — "They clicked back 3 times" > "They did not like it"
  5. Synthesize patterns — Look for trends, not outliers
7
Go/No-Go & Discovery Metrics
Making the decision and measuring your discovery practice

🚦 The Decision Matrix

🟢 GO
Problem validated ✓
Solution validated ✓
Build it!
🟡 PIVOT
Problem validated ✓
Solution failed ✗
Try a different solution
🔴 KILL
Problem not real ✗
Solution irrelevant ✗
Move on to next opportunity
🔵 LEARN MORE
Unclear problem ✗
Unclear solution ✗
Run more research

📊 Measuring Your Discovery Practice

Discovery Velocity
How many experiments per quarter?
Target: 2-4/month
Assumption Kill Rate
What % of assumptions are proven wrong?
Target: 30-50%
Time to Insight
How long from "I wonder..." to "We know..."?
Target: <2 weeks
Feature Success Rate
What % of shipped features meet their goals?
Target: >70%

🎓 Your Discovery Commitment

🎉

You have Completed the Playground!

You have practiced the core skills of Product Discovery. Here is what you accomplished:

7
Modules Completed
3+
Frameworks Practiced
∞
Mindset Shift Started

📚 Keep Learning:

  • "Continuous Discovery Habits" by Teresa Torres
  • "The Mom Test" by Rob Fitzpatrick
  • "Inspired" by Marty Cagan
  • "Jobs to be Done" by Tony Ulwick