A structured discovery phase de-risks ideas through user validation, market analysis, and technical feasibility checks. Begin with problem framing: define the user, pain point, and success criteria. Use research methods—interviews, surveys, competitive teardowns—to triangulate insights. Build lightweight prototypes to test assumptions early. Document findings in a decision memo that outlines go/no-go criteria. Keep the cycle time-boxed and cross-functional to maintain focus and momentum.
Related FAQs
How long should a discovery phase last? Typically 2–6 weeks, depending on initiative scale and risk. Set clear exit criteria, not fixed dates.
📚 推荐资源
PM面试通关手册 — Product Sense · Metrics · Behavioral · Strategy 四大题型系统攻略
Thousands of candidates have used this exact approach to land offers. The complete framework — with scripts and rubrics — is in The 0→1 PM Interview Playbook (2026 Edition).
Who should be involved in discovery
Who should be involved in discovery? Core trio: PM, designer, and engineering lead. Include researchers and data analysts as needed.
What deliverables come out of discovery? Problem statement, validated assumptions, user journey insights, prototype learnings, and a recommendation with rationale.