opportunity-solution-tree

To map customer problems to testable solutions during product discovery, you build an Opportunity Solution Tree by defining a desired outcome, identifying underlying user problems, branching solutions, and selecting a Proof-of-Concept for validation.

An opportunity solution tree is a framework that maps desired outcomes to customer problems and potential solutions. You need it during continuous discovery to prevent the feature factory trap and ensure problem-solution fit before committing development resources.

To validate a solution hypothesis with a proof of concept, define your desired outcome, identify target opportunities, brainstorm solutions, and design experiments to test the selected POC with users before full-scale implementation.

Turn vague stakeholder feature requests into validated product opportunities by using an opportunity solution tree to first clarify the desired outcome, uncover the underlying customer problem, and explore multiple solution paths before selecting a POC to test.

The best way to structure hypothesis driven development for a new initiative is creating an opportunity solution tree that connects measurable outcomes to problem opportunities, specific solutions, and targeted POC validation experiments.

Yes, you can use an opportunity solution tree for continuous discovery without prior coding. It is a discovery framework focusing on problem validation, solution hypothesis mapping, and experiment design rather than technical implementation.