Candidate 1
Unnamed candidate
Leave blank to inherit the shared decision horizon.
Relative to this decision's named outcome and horizon, not a universal score.
No evidence-quality judgment has been entered yet.
Product prioritization · decision under constraints
Product Prioritization Tool: choose what gets scarce capacity, and what does not
Compare genuinely competing product investments under the same outcome, strategy, horizon, and constraints. Make evidence quality, effort uncertainty, dependencies, opportunity cost, and decision sensitivity visible, then record the human choice instead of letting a hidden score choose the roadmap.
Prioritization is not ranking. It is choosing what receives scarce capacity, and therefore what does not. RICE, ICE, MoSCoW, Kano, WSJF, or an impact/effort view can inform that choice; none is a substitute for decision context and accountable judgment.
1 · Frame the decision
What are you choosing between, and what is actually scarce?
Prioritization starts before scoring. Define the decision, the outcome, strategy, horizon, and scarce capacity so every candidate is judged inside the same context.
Write the choice that must be made now, not a broad backlog theme.
Impact is interpretable only relative to a named outcome.
A strategic-fit score without the strategy itself is just a feeling.
Use one period so impact and reach-like signals are comparable.
The tool does not auto-stamp an approval date.
2 · Choose the decision lens
Match the framework to the job, do not blend formulas
RICE, ICE, MoSCoW, Kano, and WSJF encode different assumptions. Use them side by side when useful; never average them into a composite magic score.
Decision-under-constraints workspace
Use the workspace below to compare a genuinely comparable set, expose evidence and uncertainty, inspect opportunity cost and dependencies, pressure-test assumptions, then record the human decision.
Use the workspace below3 · Build a comparable set
Compare evidence and trade-offs, not a hidden master rank
Keep discretionary candidates at the same decision level when possible. A customer problem, a solution, an experiment, and a mandatory migration are different objects; the quality review below flags mixed sets instead of pretending the numbers make them comparable.
Candidate 2
Unnamed candidate
Leave blank to inherit the shared decision horizon.
Relative to this decision's named outcome and horizon, not a universal score.
No evidence-quality judgment has been entered yet.
Dependencies, alternatives, constraints, and benefit overlap
4 · Check decision quality
Fix comparability problems before interpreting the result
These are diagnostics, not a score. They flag missing context, mixed decision levels, hidden uncertainty, unsupported constraints, dependency effects, benefit overlap, and missing opportunity cost.
No decision question
State what must be chosen now before comparing candidates.
Outcome undefined
Impact has no shared meaning until the intended outcome is named.
Strategic context missing
Do not ask candidates to feel 'strategic' without stating the current choice or bet they should advance.
Decision horizon missing
Use one comparable period such as this quarter, the next six months, a release, or an experiment cycle.
Scarce resource not defined
Prioritization is a capacity choice. Name what is scarce: engineering, design, research, traffic, launch slots, capital, or operations.
5 · Analysis view
Advisory signals, deliberately not a ranked list
Candidate order stays the order you entered. Signals explain what the current inputs imply; they do not automatically select, defer, or sequence work.
Name at least one discretionary candidate to see advisory signals.
6 · Decision drivers
Put the two finalists side by side
Pairwise comparison is often more useful than sorting a long backlog. This view deliberately shows differences without declaring a winner.
Choose two different discretionary candidates to inspect the decision drivers.
7 · Human decision
Select, learn, sequence, defer, mandate, or reject, and record why
Tool signals stay advisory. A transparent override is healthy: if a framework ranks A higher and the team chooses B because of dependency, timing, risk, reversibility, or uncaptured evidence, record that reason instead of hiding it.
Name at least one candidate before recording a decision.
8 · Decision record
Export the choice, exclusions, assumptions, and revisit triggers
Markdown and CSV keep the tool assessment separate from the final human decision. The export includes context, evidence, uncertainty, constraints, dependencies, opportunity cost, override rationale, and what should reopen the decision.
Next step: if strategy is unclear, go backward to Strategy. If the decision is made, move the selected bets into a Roadmap; use Product Brief / PRD only when a chosen bet is ready for deeper definition.
Framework router
RICE vs ICE vs MoSCoW vs Kano vs WSJF: different jobs, different assumptions
Current prioritization search results commonly lead with framework lists, scoring dimensions, or prioritization matrices. Those are table stakes. The more important question is whether the method exposes the trade-off you actually need to make, and whether the candidates are comparable in the first place.
RICE
Use when: Reach, impact, confidence, and effort are meaningful enough to compare across the same time horizon.
Watch for: Keep reach on one period, define the impact scale, ground confidence in evidence, and remember that the original RICE guidance explicitly allows dependencies or table-stakes work to happen out of score order.
Intercom RICE source ↗ICE
Use when: You need a lightweight relative comparison of ideas or experiments and detailed reach modeling is not worth the overhead.
Watch for: Define the scales before scoring. Fast scoring is useful, but subjectivity can create precise-looking noise if impact, confidence, and ease mean different things to different people.
MoSCoW
Use when: You are negotiating scope inside a defined release, deadline, or capacity constraint.
Watch for: A Must should survive a real failure test. Stakeholder preference is not enough, and mandatory outcome does not imply unlimited implementation scope.
Agile Business Consortium source ↗Kano
Use when: You need to study how capability presence and absence affect customer satisfaction and expectations.
Watch for: Kano can inform the customer-response dimension. It does not by itself answer strategic fit, effort, opportunity cost, dependencies, or sequencing.
WSJF
Use when: Economic sequencing matters and relative cost of delay plus job size are meaningful in the planning system you actually use.
Watch for: WSJF solves a sequencing job. CraftUp does not currently expose a standalone WSJF calculator, so do not blend it into RICE/ICE or invent an owner inside this page.
SAFe WSJF source ↗Impact / effort matrix
Use impact versus effort as a transparent conversation aid when only a few comparable options matter. High-impact / low-effort is a useful discussion signal, not an automatic first commitment; low-impact / low-effort can still become distracting “snacking” once context switching, testing, support, and maintenance are included.
Decision quality
Better inputs matter more than prettier rankings
Prioritization usually fails upstream: the decision is vague, options use different horizons, evidence and assumptions are mixed together, effort looks more precise than it is, or opportunity cost disappears. Fix those problems before asking a framework to sort anything.
Comparable decision set
Compare options that genuinely compete for the same decision and scarce resource. A customer problem, a solution, an experiment, and a mandatory migration are not automatically equivalent backlog items.
Outcome + impact
Name the outcome before estimating relative impact. A 5 means potentially material for this decision and horizon, not universally important across products or planning cycles.
Evidence + uncertainty
Record what supports the claim and what remains unknown. Evidence may establish a problem without proving a proposed solution will create the expected effect.
Effort + enduring cost
Include material engineering, design, data, legal, operations, migration, support, complexity, and maintenance costs. Small build effort is not the same as free ongoing cost.
Strategy + rationale
State the actual strategic choice first, then explain how each candidate advances or fragments it. Strategic fit is not a self-evident number.
Opportunity cost
If you choose this, what likely gets delayed or excluded? Prioritization without a visible displaced alternative is usually wish-list ordering.
Dependencies + alternatives
Sequence enablers without confusing sequence with value. Mark mutually exclusive solutions as alternatives and flag overlapping benefit so upside is not double-counted.
Hard constraints
Keep verified regulatory, security, contractual, incident, mandatory-migration, dependency, or continuity work outside normal value ranking, while still challenging the minimum scope needed.
Worked example · fictional
A framework can rank A first while the team responsibly acts on B first
Imagine a fictional B2B collaboration product trying to improve first-team activation this quarter. The team has limited onboarding capacity and is comparing solution mechanisms after identifying an onboarding problem. All evidence below is illustrative, not benchmark data or a real-company result.
A · Guided integration setup
A RICE-style pass could put guided setup first if its reach and impact assumptions are accepted. But it is a larger bet, depends on reliable setup instrumentation, and overlaps with another mechanism aimed at the same activation outcome.
Human call: keep it as a serious candidate, but sequence it after the critical activation mechanism is better understood.
B · Sample workspace learning test
The sample-workspace mechanism may rank lower in a reach-heavy model, but a small reversible test can cheaply answer whether users need to experience value before integration. The team allocates discovery capacity to B first because information value changes the larger A decision.
Human call: Learn First, an explicit framework override with rationale, not a failure of prioritization.
Mandatory work · reporting export
A fictional signed reporting obligation is handled in reserved constrained capacity rather than being ranked as the #1 value bet. The team still challenges the minimum compliant outcome so “mandatory” does not expand into a full admin redesign.
Not now · dashboard theme
No current evidence connects visual customization to the target activation outcome, and it fragments focus. The team rejects it under the present decision rather than keeping a zombie backlog item with no revisit rule.
Load the same fictional decision inside the workspace above to inspect candidate evidence, opportunity cost, dependencies, pressure tests, final human decisions, override rationale, and revisit triggers.
Why “highest score wins” fails
The candidates are different decision objects or use different horizons.
The input numbers are guesses, defaults, or inconsistent scales.
Evidence supports the problem but not the proposed solution mechanism.
Two candidates depend on each other, so sequence differs from underlying value.
Mutually exclusive solutions are treated as independent investments.
A high-scoring item fragments the current strategy or displaces a more important capacity choice.
A verified regulatory, security, contractual, incident, or migration constraint sits outside ordinary value ranking.
Effort looks precise while migration, support, maintenance, or operational cost remains uncertain.
Several initiatives claim the same benefit and their upside is double-counted.
A cheap reversible test can resolve the assumption driving a much larger commitment.
Small input changes reverse the advisory signal, revealing a sensitive decision.
The final choice copies the sort order without recording why the team believes it.
Workflow boundary
Strategy → Prioritization → Roadmap → Product Brief / PRD
These are different decisions. Strategy chooses where to play and what choices matter. Prioritization allocates scarce capacity inside that direction. Roadmap communicates selected bets and sequence. Product Brief / PRD deepen one chosen investment only after it has earned attention.
1. Strategy
Clarify target customer, diagnosis, choices, bets, non-goals, and the outcome the team is trying to move.
Product Strategy One-Pager2. Prioritize
Choose which comparable opportunities or bets receive scarce capacity, what must be learned first, and what is explicitly not happening now.
Use this workspace3. Communicate sequence
Carry selected bets, uncertainty, dependencies, and exclusions into an outcome-oriented roadmap.
Product Roadmap Template4. Define selected work
Use a Product Brief for lightweight alignment or a PRD when the chosen bet needs deeper product behavior and requirements.
Product Brief TemplateIf the problem itself is weak, go backward to the Problem Statement Generator or customer discovery. If several solutions are being compared before a credible opportunity is chosen, use the Opportunity Solution Tree to restore the decision level.
Learn the method, practice the judgment, then make the real decision
Prioritization frameworks guide
Deeper methodology for RICE, ICE, Kano, MoSCoW, Value vs Effort, and WSJF. The guide teaches framework choice; this tool owns the live decision.
PM prioritization exercises
Practice on fictional scenarios before exposing yourself to the reasoning guide and alternative defensible paths.
Product Manager skills
Diagnose the broader prioritization capability alongside discovery, strategy, metrics, and execution.
Product Management Foundations
Build the concepts behind evidence, trade-offs, outcomes, strategy, and roadmap decisions.
Product operations
Turn decisions into operating cadence and traceable context without turning process into the decision itself.
Prioritization interview guide
Hiring-format practice is a separate job: learn how to explain prioritization reasoning under interview constraints.
Product prioritization FAQ
What is the best product prioritization framework?
There is no universally best framework. RICE is useful when reach, impact, confidence, and effort are comparable; ICE is faster for rough relative comparison; MoSCoW is for release-scope negotiation under a real constraint; Kano studies satisfaction response; and WSJF is an economic sequencing method when cost of delay and job size are meaningful. Match the method to the decision instead of blending them into one score.
Should the highest prioritization score always win?
No. A score is an input to judgment. Dependencies, strategic choices, hard constraints, opportunity cost, reversibility, weak evidence, or a cheaper learning step can justify choosing a lower-ranked option first. Record the reason rather than hiding the override.
How should confidence be scored?
Treat confidence as evidence quality for a specific claim, not optimism. Evidence may support problem existence while leaving solution impact uncertain. This workspace therefore uses qualitative evidence states and asks for the source and major uncertainty instead of multiplying a decorative confidence number into a master score.
Should I prioritize problems or features?
Prioritize problems or opportunities before solutions whenever possible. If the problem is not credible, a precise feature score can create false confidence. Once a problem deserves investment, compare alternative solution mechanisms separately.
What happens to mandatory security, regulatory, or contractual work?
Verified hard constraints should be handled in constrained capacity rather than ranked as the highest-value work. Confirm the source, deadline, and minimum outcome that satisfies the constraint so mandatory work does not become unlimited scope.
What is prioritization sensitivity analysis?
Sensitivity asks whether a plausible change in an assumption changes the decision signal. This workspace can pressure-test one change at a time, lower impact, weaker evidence, larger effort, or weaker strategy alignment, and labels the current signal as sensitive or robust to that specific test without pretending to estimate probability.
What is the difference between prioritization and a product roadmap?
Strategy defines the direction and choices; prioritization chooses which comparable investments deserve scarce capacity under current evidence and constraints; a roadmap communicates the selected bets and sequence. A roadmap should not be used as a substitute for making the prioritization decision first.
Need another PM workflow? Browse all Product Management tools.