← All use cases · Full directory
Product Decision Trees
Product decision trees for MVP scope, feature prioritisation, metric selection, research method, and roadmap trade-offs. Free to run, copy, and embed.
6 published trees in this category. Every one runs as a guided wizard in the browser — no signup — and can be copied as the starting point for your own version.
Trees in this category
Does this product fit my needs and use case?
Public interactive decision tree.
How should I prioritise competing roadmap items?
When engineering capacity is constrained, decide what to prioritise across new features, bug fixes, technical debt, performance improvements, and security or compliance work. Guides product managers through urgency, customer impact, and business risk to make a defensible trade-off call. Use during sprint planning, quarterly roadmap reviews, or whenever a new urgent item competes with committed work.
How should I prioritise this product feature?
Decide whether and how urgently to prioritise a feature request. Works through customer validation, strategic fit, business impact, and effort to route each request to the right outcome. Use this before committing any request to a sprint or quarterly roadmap.
What should I include in my MVP scope?
Determine whether a capability belongs in the MVP or should be deferred to a later release. Guides PMs through the core user journey, customer commitments, differentiation value, and interim workarounds to make a clear scoping call. Use this during feature kickoff and pre-launch scope reviews.
Which product metric should I use to measure this feature?
Determine which type of metric best measures a feature or product area you are responsible for. Guides product managers through primary goal, feature maturity, and actionability to select a metric type that drives meaningful decisions rather than vanity reporting. Use during OKR planning, launch prep, or quarterly business reviews.
Which research method should I use for this study?
Choose the right user research method for your current product question. Guides product managers and researchers through hypothesis clarity, sample size needs, product stage, and behavioural versus attitudinal data requirements. Use at the start of any discovery or validation sprint.
All Product trees
- Does this product fit my needs and use case?
- How should I prioritise competing roadmap items? — When engineering capacity is constrained, decide what to prioritise across new features, bug fixes, technical debt, performance improvements, and security or compliance work. Guides product managers through urgency, customer impact, and business risk to make a defensible trade-off call. Use during sprint planning, quarterly roadmap reviews, or whenever a new urgent item competes with committed work.
- How should I prioritise this product feature? — Decide whether and how urgently to prioritise a feature request. Works through customer validation, strategic fit, business impact, and effort to route each request to the right outcome. Use this before committing any request to a sprint or quarterly roadmap.
- What should I include in my MVP scope? — Determine whether a capability belongs in the MVP or should be deferred to a later release. Guides PMs through the core user journey, customer commitments, differentiation value, and interim workarounds to make a clear scoping call. Use this during feature kickoff and pre-launch scope reviews.
- Which product metric should I use to measure this feature? — Determine which type of metric best measures a feature or product area you are responsible for. Guides product managers through primary goal, feature maturity, and actionability to select a metric type that drives meaningful decisions rather than vanity reporting. Use during OKR planning, launch prep, or quarterly business reviews.
- Which research method should I use for this study? — Choose the right user research method for your current product question. Guides product managers and researchers through hypothesis clarity, sample size needs, product stage, and behavioural versus attitudinal data requirements. Use at the start of any discovery or validation sprint.
How to use these trees
- Run one to see how the questions are ordered and where each path ends.
- Copy the source. Every tree is plain text, so you can lift it and edit the wording for your own organisation. Syntax reference →
- Embed it in your wiki, help centre, or intranet with one snippet that stays current whenever you edit the tree. Embedding guide →