---
title: "Roadmap Prioritization Frameworks Compared"
description: "RICE, ICE, MoSCoW, Kano, value vs effort and weighted scoring compared side by side: what each needs as input, what it is best for, and how each one fails."
canonical_url: "https://builderscamp.com/guides/other/roadmap-prioritization-frameworks-compared"
date_published: "2026-10-05"
date_modified: "2026-10-05"
author: "Andre Albuquerque"
publisher: "Builders Camp"
guide_class: "other"
---

# Roadmap Prioritization Frameworks Compared

**TL;DR:** Use RICE to rank a shortlist when you have usage data, ICE for a fast first pass on a long idea list, MoSCoW to cut scope inside a fixed release, Kano to learn which features customers expect, a value versus effort matrix for a quick visual trade-off, and weighted scoring when leadership has fixed the criteria. The frameworks answer different questions, so the choice depends on the decision you are making, not on which one is most rigorous.

Every roadmap prioritization framework is a way to replace one loud argument with a few named inputs, and each one picks different inputs. RICE, built at Intercom, is the most numeric: [Sean McBride's original Intercom article](https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/) scores Impact on a scale from 3 for massive down to 0.25 for minimal, Confidence at 100, 80 or 50 percent, and Effort in person-months. Even so, McBride writes that "RICE scores shouldn’t be used as a hard and fast rule." That caveat applies to every framework on this page, and it is the reason the useful question is which framework fits which decision, not which one is correct.

## How do the six frameworks compare side by side?

The table below compares the six frameworks product teams most often reach for on three practical questions: what you have to feed in, what decision the output supports, and how the method most often goes wrong.

| Framework | Inputs you need | Best for | Typical failure mode |
|---|---|---|---|
| [RICE](https://builderscamp.com/guides/other/rice-prioritization-framework) | Reach per period, Impact on a fixed scale, Confidence percentage, Effort in person-months | Ranking a shortlist of ideas that differ a lot in size, when you have usage data | Precise-looking scores built on guessed Impact and Reach |
| [ICE](https://builderscamp.com/guides/other/ice-scoring-framework) | Impact, Confidence and Ease, each on a simple 1 to 10 scale | A fast first pass over a long list of ideas or growth experiments | Hides scale: an idea for ten users and one for ten thousand can score the same |
| [MoSCoW](https://builderscamp.com/guides/glossary/moscow-method) | A fixed timebox and a list of requirements for one release | Cutting scope so a deadline holds | Run across a whole backlog, everything becomes a Must have |
| [Kano](https://builderscamp.com/guides/other/kano-model-explained) | Customer answers to paired questions about each feature | Learning which features are expected, which scale satisfaction, and which delight | Treated as a ranking formula when it is a research input |
| [Value vs effort matrix](https://builderscamp.com/guides/glossary/prioritization-matrix) | A rough value and effort placement for each idea | A workshop where stakeholders need to see the trade-offs at a glance | Placement by gut feel, so the loudest voice still decides the quadrant |
| Weighted scoring | A list of criteria, a weight for each, and a score per idea per criterion | Judging ideas against strategy criteria leadership has already agreed | Weights tuned after the fact until a favourite idea wins |

RICE, ICE and weighted scoring rank ideas, MoSCoW scopes a release, Kano classifies features, and the matrix makes trade-offs visible. Teams that treat all six as rivals end up arguing about the tool instead of the roadmap.

## When does RICE beat the faster scoring methods?

RICE earns its extra effort when your candidate ideas differ wildly in how many people they touch. McBride built it to correct specific biases he listed in the Intercom article, including that "It’s satisfying to work on pet ideas you’d use yourself, instead of projects with broad reach." Reach is the factor that catches that bias, and it is the factor ICE drops.

The cost is data. A Reach estimate needs real usage numbers, and the Confidence factor only does its job if the team scores it honestly. McBride's own scale labels anything below 50 percent a "total moonshot". If most of your ideas would land there, RICE gives you a precise ranking of guesses, and a faster method costs you nothing.

## Where does ICE fit, and what did Sean Ellis design it for?

ICE comes out of growth teams running many small experiments a week. Sean Ellis, founder of GrowthHackers, described the method in a [SaaStr session transcript](https://www.saastr.com/sean-ellis-founder-ceo-of-growthhackers-building-a-company-wide-growth-culture-video-transcript/): "Impact, if this thing works, is it going to be really high impact or is it something that’s just going to move the needle a little bit?" He scores each of Impact, Confidence and Ease on a scale of 1 to 10.

ICE suits a backlog of cheap, reversible tests, where a wrong ranking costs a week rather than a quarter. For a roadmap of large, expensive bets, the missing Reach factor and the subjective Ease score make it too coarse to settle a real disagreement. Use ICE to shortlist, then run RICE or weighted scoring on what survives.

## Why is MoSCoW a scoping tool rather than a ranking tool?

MoSCoW belongs to DSDM, a project framework in which time is fixed and work is planned in Timeboxes, and its categories only mean something relative to a deadline. The [Agile Business Consortium's DSDM handbook](https://www.agilebusiness.org/dsdm-project-framework/moscow-prioritisation.html) defines Must Haves as the "Minimum Usable SubseT (MUST) of requirements which the project guarantees to deliver" and sets a ceiling: "The safe percentage of Must Have requirements, in order to be confident of project success, is not to exceed 60% Must Have effort."

The 60 percent figure is DSDM's rule of thumb for timeboxed delivery, not a measured threshold for every team. It still makes the main point: MoSCoW only works when most of the work is not a Must have. Ask "Must have for what release?" before anyone sorts anything, and use a ranking method first to decide which feature goes into that release.

## What does the Kano model add that scoring frameworks miss?

Kano is the only framework here that asks customers directly how a feature changes their satisfaction, rather than asking the team to estimate it. The method comes from Noriaki Kano and colleagues, published in the Japanese Society for Quality Control's journal in 1984, and the [Center for Quality of Management Journal's 1993 compendium on Kano's methods](https://www.walden-family.com/public/cqm-journal/2-4-Whole-Issue.pdf) gives the clearest English example: poor brakes make a car buyer dissatisfied, yet "having good brakes, however, does not raise the level of the customer’s satisfaction."

Brakes are a Must-be feature in Kano's terms. Gas mileage is One-dimensional, where more is better, and a self-lowering radio antenna is Attractive, nice to have and not missed when absent. A RICE score cannot see that difference, so a team relying on RICE alone can underinvest in table stakes that score low on Impact until they break. The limitation is cost: Kano needs a questionnaire and real respondents, and it classifies features without telling you the build order.

## When are a value vs effort matrix or weighted scoring the better choice?

A value versus effort two-by-two is the fastest framework to run in a room. Plotting ideas into quick wins, big bets, fill-ins and money pits gets stakeholders to see the trade-off in minutes, which makes it a good opening move for a planning workshop. The weakness is that placement is a judgement call, so it works best after a scoring pass has given each idea a defensible position.

Weighted scoring is the right choice when leadership has already decided what matters this year, for example strategic fit, revenue and risk reduction, and wants every idea judged against the same list. Writing the weights down before scoring is the whole value of the method. Weights adjusted after the scores come in turn it into a way to justify a decision that was already made.

## Which framework should you use for which decision?

The decision in front of you picks the framework, not the other way around:

- **Ranking many ideas against each other:** ICE for a first pass, then RICE (with usage data) or weighted scoring (with agreed strategy criteria) on the shortlist.
- **Cutting scope to hit a date:** MoSCoW, inside one release, with Must haves kept well under the timebox.
- **Not knowing what customers expect:** Kano research first, before any scoring.

The full step-by-step sequence, with a worked example, is in [how to prioritize features](https://builderscamp.com/guides/other/how-to-prioritize-features).

## What is the strongest case against using any framework at all?

The strongest objection is that every input is a guess, so a framework mostly launders opinion into a number that looks objective. That criticism is fair, and McBride's own article concedes it: choosing an impact number "may seem unscientific." His answer is the right one for all six methods, "remember the alternative: a tangled mess of gut feeling." A framework does not make the decision correct. It makes each assumption visible, so the one input driving a ranking can be challenged, tested with research, or changed. When a stakeholder still pushes a low-scoring item, the scores give you a specific, checkable reason to [say no](https://builderscamp.com/guides/other/how-to-say-no-to-stakeholders).

Choosing a framework is the smaller decision; deciding which bets the roadmap exists to serve is the larger one. Builders Camp's Product Strategy bootcamp, part of the [Product Leadership Track](https://builderscamp.com/tracks/product-leadership), runs 2 weeks with 4 live sessions and covers strategic choices and trade-offs, including using frameworks to decide bets and avoid strategy-by-committee, then roadmapping as a strategy execution tool that turns those bets into sequencing, milestones and measurable outcomes.

[See the Product Strategy bootcamp](https://builderscamp.com/bootcamps/product-strategy?utm_source=guide&utm_medium=organic&utm_campaign=roadmap-prioritization-frameworks-compared)

## Frequently asked questions

### Which roadmap prioritization framework is best?

None wins across the board, because they answer different questions. RICE and ICE rank competing ideas, MoSCoW cuts scope inside a fixed release, Kano tells you which features customers expect versus which ones delight them, a value versus effort matrix makes trade-offs visible in a workshop, and weighted scoring ranks ideas against criteria leadership has agreed in advance. Pick the one whose question matches the decision in front of you.

### What is the difference between RICE and ICE?

RICE has four factors and divides by Effort measured in person-months. ICE has three factors, Impact, Confidence and Ease, each scored 1 to 10 in Sean Ellis's version, and drops Reach entirely. ICE is faster to fill in; RICE is better at telling apart an idea that touches ten users from one that touches ten thousand.

### Can MoSCoW be used to prioritize a whole roadmap?

It works poorly for that. MoSCoW comes from DSDM, a framework built around fixed timeboxes, and it sorts requirements within one release or increment. Applied to a whole backlog, every requester defends their item as a Must have and the categories stop meaning anything.

### Is the Kano model a prioritization framework?

Kano is a research method that feeds prioritization rather than a ranking formula. A paired questionnaire asks customers how they feel if a feature is present and how they feel if it is absent, then sorts the feature into a category such as Must-be, One-dimensional or Attractive. You still need another method to decide the build order.

### When should a team use weighted scoring instead of RICE?

When leadership has already named the criteria that matter, for example strategic fit, revenue potential and risk reduction, and wants every idea judged against the same list. Weighted scoring makes those criteria and their weights explicit. RICE is better when the main question is reach and effort and you have usage data to estimate them.

### Should a team use more than one framework?

Usually, yes, in sequence. A common pattern is a fast ICE pass to shortlist a long idea list, RICE on the shortlist, then MoSCoW to scope the winner into a release. Kano research sits upstream of all three when you do not yet know which features customers treat as table stakes.

### Do scoring frameworks remove opinion from prioritization?

No. Every input in RICE, ICE and weighted scoring is an estimate someone made. What the frameworks do is turn one vague argument into several named numbers that can be challenged and checked, which is a real improvement but not objectivity.

## Sources

- [Intercom: RICE, Simple prioritization for product managers (Sean McBride)](https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/)
- [SaaStr: Sean Ellis, Founder and CEO of GrowthHackers, Building a Company Wide Growth Culture (transcript)](https://www.saastr.com/sean-ellis-founder-ceo-of-growthhackers-building-a-company-wide-growth-culture-video-transcript/)
- [Agile Business Consortium: MoSCoW Prioritisation, DSDM Project Framework Handbook](https://www.agilebusiness.org/dsdm-project-framework/moscow-prioritisation.html)
- [Center for Quality of Management Journal: Kano's Methods for Understanding Customer-defined Quality (Fall 1993)](https://www.walden-family.com/public/cqm-journal/2-4-Whole-Issue.pdf)

## How this guide was made

Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.