opportunity-solution-tree

An opportunity solution tree structures product discovery by mapping a desired outcome to customer opportunities, testable solutions, and experiments. It guides teams to identify problems and validate hypotheses before committing development resources.

To turn vague stakeholder requests into a structured product discovery plan, you extract a desired outcome, map customer opportunities, propose solutions, and select a preliminary Proof of Concept (POC) to test hypotheses.

You select a proof of concept (POC) by evaluating proposed solutions against feasibility, impact, and market fit. This process recommends a starting POC and defines a specific experiment design for validation.

Yes, you can use opportunity mapping for early-stage product initiatives to avoid feature-first bias. It aligns discovery efforts with measurable outcomes by focusing on customer problems before proposing specific solutions.

The best way to prioritize exploration efforts is by generating an opportunity solution tree to evaluate solutions by feasibility, impact, and market fit, ultimately recommending a preliminary POC with a defined experiment.

You should not use an opportunity solution tree when your initiative already has a fully validated outcome and committed development resources, as the OST process is designed for early-stage discovery and hypothesis testing.