The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
loading…
product, ux & customer framework
Use a tree metaphor to discuss product roots, trunk, branches and leaves.
quick answer
Prune the Product Tree is a tree / hierarchy for Product visioning. It turns the decision into named fields, evidence, and a visible prune the product tree worksheet / visual.
The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
Use a tree metaphor to discuss product roots, trunk, branches and leaves.
Use Opportunity Solution Tree when its output is closer to the conversation you need: Map desired outcome to opportunities, solutions and experiments.
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.
A filled example so you can see the shape before applying Prune the Product Tree to your own context.
A filled example so you can see the shape before applying Prune the Product Tree to your own context.
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 Prune the Product Tree to my situation. Context: [Decision, audience, options, evidence, and constraints.] Use the Prune the Product 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 prune the product tree worksheet / visual makes clearer.
Write the concrete product visioning 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 prune the product 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 Prune the Product 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
Map desired outcome to opportunities, solutions and experiments.
Map page/category hierarchy and navigation relationships.
Define a guiding metric and input metrics that capture customer value and business value.
faq
Use a tree metaphor to discuss product roots, trunk, branches and leaves.
Business context; objectives; available evidence; stakeholder judgment
Prune the Product Tree worksheet / visual
Use Prune the Product Tree when the decision matches this job: Use a tree metaphor to discuss product roots, trunk, branches and leaves.
Avoid it when you need Opportunity Solution Tree's output instead: Map desired outcome to opportunities, solutions and experiments.
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 prune the product tree worksheet / visual to choose the next move, name the riskiest assumption, or decide what evidence would change the call.
Use Opportunity Solution Tree when the real output you need is closer to: Map desired outcome to opportunities, solutions and experiments.
Yes. Describe your context and Ask PL can ask for missing inputs, render the tree / hierarchy, and explain what decision it should change.