What does it mean?
Start with a desired outcome and map the customer needs that could help you reach it. Explore possible solutions under those needs, then test the assumptions behind each solution.
Make it concrete.
Illustrative example: A team trying to improve first-week retention explores confusing setup and unclear value before choosing solutions.
A common mistake.
Treating the tree as proof that an untested solution will work.
When should you use it?
When a team has a target outcome but too many competing feature ideas.
Explore the source.
Product Talk — Opportunity Solution Trees ↗A reference for further learning, not an endorsement or verbatim quotation.