What Product Discovery Actually Is
Discovery is not just requirements gathering. It's alignment — between business goals, user needs, and technical reality.
Week 1: Understand the Problem
Days 1–2: Stakeholder Interviews
- Interview 3–5 stakeholders minimum
- Ask "what does success look like in 12 months?"
- Map competing priorities and hidden assumptions
Days 3–4: Market Research
- Competitive landscape: 5–8 direct competitors
- Feature matrix: what exists vs. what's missing
- User reviews of competitor products (App Store, G2, Trustpilot)
Day 5: Synthesis
- Affinity mapping of insights
- Opportunity areas identified
- Initial risk register created
Week 2: Define the Solution
Technical Feasibility
- Architecture options with trade-offs
- Integration requirements
- Data privacy and compliance considerations
MVP Scoping
- Feature prioritization using RICE scoring
- User story mapping
- Rough effort estimation
Output Deliverables
- Product Requirements Document (PRD)
- Technical Architecture Decision Record
- Prioritized Feature Roadmap
- Project Estimation & Timeline
A well-run Discovery phase eliminates 80% of project risk before a single line of code is written.