The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
loading…
product, ux & customer framework
Map desired outcome to opportunities, solutions and experiments.
quick answer
Opportunity Solution Tree is a tree / hierarchy for Product discovery. It turns the decision into named fields, evidence, and a visible opportunity solution tree worksheet / visual.
The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
Map desired outcome to opportunities, solutions and experiments.
Use Prune the Product Tree when its output is closer to the conversation you need: Use a tree metaphor to discuss product roots, trunk, branches and leaves.
worked example
A filled example is easier to understand than a blank template. Use it to see the shape before applying the framework to your own case.
The tree keeps outcomes, customer opportunities, and solution options separate so the team does not jump to one feature.
The tree keeps outcomes, customer opportunities, and solution options separate so the team does not jump to one feature.
generate yours
Start Ask PL with the framework, required inputs, and your context. It will ask for missing details, render the tree / hierarchy, and explain what decision the output should change.
Apply Opportunity Solution Tree to my situation. Context: [Decision, audience, options, evidence, and constraints.] Use the Opportunity Solution Tree structure: - Root question: - mutually exclusive branches: - sub-issues: - hypotheses: Ask only for missing inputs that would change the output. Then render the tree / hierarchy and name the decision it should change.
how to use it
Use the framework to change a decision, not to fill a worksheet. Start narrow, add evidence, then inspect what the opportunity solution tree worksheet / visual makes clearer.
Write the concrete product discovery choice, tradeoff, or conversation the framework should change.
Fill the important slots: Root question, mutually exclusive branches, sub-issues, hypotheses.
Mark what is measured, what comes from customers, and what is still judgment.
End with the next move, the riskiest assumption, or the evidence that would change the opportunity solution tree worksheet / visual.
quality check
Use this check after the artifact is filled. Blank fields are not failure; they are the next research question. Look for concrete evidence, missing constraints, and assumptions that would change the next move.
The framework needs a concrete decision. Broad intent turns it into a worksheet, not a decision aid.
Good framework output makes assumptions visible enough for someone else to challenge.
The diagram is useful only if it changes the next product conversation.
common mistakes
Do not use Opportunity Solution Tree as a worksheet. Name the choice, conversation, or tradeoff the output should change.
Separate measured facts, customer evidence, and leadership judgment so weak assumptions stay visible.
If the diagram does not match the decision, switch frameworks instead of stretching the boxes.
The framework should clarify the next move. It should not replace strategy, sequencing, or judgment.
use something else when
Use a tree metaphor to discuss product roots, trunk, branches and leaves.
Map page/category hierarchy and navigation relationships.
Define a guiding metric and input metrics that capture customer value and business value.
faq
Map desired outcome to opportunities, solutions and experiments.
Business context; objectives; available evidence; stakeholder judgment
Opportunity Solution Tree worksheet / visual
Use Opportunity Solution Tree when the decision matches this job: Map desired outcome to opportunities, solutions and experiments.
Avoid it when you need Prune the Product Tree's output instead: Use a tree metaphor to discuss product roots, trunk, branches and leaves.
It is both: a structure for thinking and a visible tree / hierarchy that makes the decision easier to inspect.
A good input names the real decision, uses concrete evidence, and separates facts from assumptions.
Use the opportunity solution tree worksheet / visual to choose the next move, name the riskiest assumption, or decide what evidence would change the call.
Use Prune the Product Tree when the real output you need is closer to: Use a tree metaphor to discuss product roots, trunk, branches and leaves.
Yes. Describe your context and Ask PL can ask for missing inputs, render the tree / hierarchy, and explain what decision it should change.