product-discovery

Product Discovery Skill

Transform vague ideas into actionable specifications through structured questioning.

Core Methodology

Questioning Frameworks

Five Whys - Reach root problems:

1. "Why is this a problem?" → Surface answer
2. "Why does that matter?" → Deeper impact
3. Continue until you reach the core motivation

MECE (Mutually Exclusive, Collectively Exhaustive):

• Cover all aspects without overlap
• Users, features, constraints, success criteria

Socratic Probing:

• Never accept surface-level answers
• "Can you give me a specific example?"
• "What would happen if...?"

Discovery Phases

Phase 1: Vision

Key Questions:

• "What moment made you think 'someone should build this'?"
• "If this existed perfectly, walk me through using it tomorrow"
• "Fast forward one year - what changed in the world?"

Phase 2: Core Problem

Key Questions:

• "If you could only solve ONE aspect, which unlocks the most value?"
• "What's the smallest thing that would make one person genuinely grateful?"
• "What part do you understand best? What's still fuzzy?"

Scope Control:

• "If you had budget for only 3 features, which would they be?"
• "Now pick just ONE to prove the concept"

Phase 3: Users

Key Questions:

• "Think of one specific person who needs this. What's their name? Their story?"
• "What do they do immediately before/after using your software?"
• "Which user type would be easiest to satisfy? Hardest?"

Phase 4: Technical

Key Questions:

• "What could you hardcode for MVP that becomes dynamic later?"
• "Which technical decisions can wait until concept is validated?"
• "What existing tools could you leverage instead of building?"

Phase 5: Validation

Key Questions:

• "How would you know, objectively, that MVP is working?"
• "What number would make you confident to continue? What would make you pivot?"
• "What feedback would change your direction most dramatically?"

Phase 6: Scoping

Effort-Based Framing (NOT time-based):