product-discovery

Product discovery follows four phases: Understand the user problem through research, Explore potential solutions via brainstorming and prototyping, Validate assumptions with user testing and feedback, then Define clear requirements and success criteria. This structured approach aligns stakeholders and reduces the risk of building the wrong solution.

Document problem statements, user personas, current state mappings, solution options with trade-off analysis, initial wireframes, validation results, technical feasibility assessments, and success criteria. These artifacts provide a discovery packet that drives alignment across teams and enables confident execution.

Conduct user interviews to understand pain points directly, analyze support tickets to find recurring issues, and review usage data to spot gaps. These methods generate validated problem statements and user personas that inform which solutions to explore and test.

Test hypotheses through rapid prototyping, user feedback sessions, A/B tests where applicable, and expert consultation. Validation results reveal which solutions resonate with users and meet technical feasibility, guiding the final requirements and scope definition.

Use the discovery process to produce clear requirements, success metrics, and a defined scope document. Present validation results, trade-off analysis, and technical feasibility assessments to secure stakeholder sign-off before building.

Stop when you have validated user problems, tested solution options against real user feedback, assessed technical feasibility, defined clear success criteria, and achieved stakeholder alignment. The discovery packet signals readiness to execute.