continuous-discovery

To validate product problems before building solutions, map an opportunity solution tree to structure desired outcomes and customer needs, then test your riskiest assumptions using small experiments before proceeding to design or implementation.

An opportunity solution tree structures the relationship between desired business outcomes, underlying customer needs, and potential solutions. It ensures breadth of thought during product discovery by visually aligning the problem space before any feature development begins.

Identify the riskiest assumptions for a new feature by evaluating desirability, viability, feasibility, and usability. Test these critical assumptions first using small, cheap experiments to gather evidence before committing to software design or coding.

Yes, you can shift your team from output to outcome metrics by applying outcome-over-output principles. This process frames product discovery around achieving measurable customer or business results rather than simply shipping predefined feature outputs.

Use continuous product discovery at the front-end of the software development lifecycle whenever you have a new project goal. It prevents building unnecessary features by rigorously interrogating the problem space and executing small-bet experiments before design.