opportunity-solution-tree

To turn vague stakeholder requests into validated product discovery, convert the asks into an opportunity solution tree. This structures discovery by aligning requests with measurable outcomes, evidence-backed opportunities, and solution hypotheses before committing to development.

The best way to map opportunities to desired business outcomes is through outcome-driven framing. This process unpacks why a metric matters, explores the problem space by generating multiple evidence-backed customer opportunities, and ensures discussions focus on the result rather than premature features.

To evaluate solution feasibility and market fit before writing requirements, apply solution scoring during product discovery. This process scores proposed solutions against impact and market fit, then recommends the best proof-of-concept experiment, such as a manual concierge or A/B test, to validate the hypothesis.

You should use an opportunity solution tree for product discovery when you receive ambiguous feature asks from stakeholders. It prevents premature solutioning by forcing a structured discovery process that surfaces measurable outcomes, validated opportunities, and specified experiments before development.

To choose the right proof-of-concept experiment for a solution hypothesis, evaluate the solution's feasibility, impact, and market fit. Based on this scoring, select the most appropriate experiment type—whether a manual concierge test, a prototype, or an A/B test—to prove the product decision.