ICE, RICE, Kano: the score is theater. The argument it forces is the real output.

Every product team reaches for a prioritization framework the moment the backlog gets longer than the roadmap. The promise is that a formula will turn a pile of competing opinions into a clean ranked list.

It will, sort of.

But anyone who has filled one of these in honestly knows the dirty secret. You usually decide what you want to do first, then pick the numbers that get you there. The framework is real and useful, just not for the reason most people think.

ICE, fast and rough

ICE scores each idea on three things from one to ten. Impact (how much it moves the metric), Confidence (how sure you are), and Ease (how cheap it is to do). Multiply the three for a score, sort descending. Sean Ellis popularized it for growth teams running a lot of experiments. It is quick, it is blunt, and it is genuinely good when you have a long list of small bets and need to triage fast.

Its weakness is its strength. Three soft numbers, multiplied, hide a lot of guessing.

RICE, slower and defensible

RICE, from the team at Intercom, adds rigor. You score Reach, Impact, and Confidence, then divide the whole thing by Effort. The division matters. It punishes expensive ideas and rewards cheap-but-broad ones, which is exactly the bias you want when resources are tight.

RICE is slower to fill in and it asks for real numbers like reach, which forces you to look things up instead of vibing. Use it when you have to defend your cuts to other people.

Kano, what delights versus what's expected

Kano is not a scoring formula, it is a way of classifying features by how they change satisfaction. Basic needs are the things customers do not notice when present but rage about when missing. Performance features are the ones where more is straightforwardly better. Delighters are the unexpected touches that create loyalty.

Plot a feature and you learn something ICE and RICE cannot tell you, whether you are about to build something that wins love, or just something people already assumed was there.

The score is theater

Here is the part nobody puts in the template. Hand the same feature to three people and you get three different scores, because Impact and Confidence are feelings dressed as integers.

The formula does not remove the subjectivity, it hides it inside a number that looks objective. When a team argues about a roadmap, the spreadsheet becomes the weapon, and whoever is most comfortable inflating an Impact score wins.

That is not prioritization, it is politics with a math costume.

So treat the output as evidence, not a verdict. The genuine value of running ICE or RICE is that it forces everyone to put their private assumptions on the table in a comparable shape. The moment two smart people score the same idea a 9 and a 3, you have found the real conversation, and it is worth more than any ranking. The framework is a forcing function for the disagreement you were going to have anyway, just usually too late and in a hallway.

Stuck on what to build next?

Book a 1:1 with a product mentor who has run this prioritization a hundred times. One membership, unlimited calls, every mentor included.

Find a mentor

How to use them without fooling yourself

• Score as a group, not solo. The disagreement between scorers is the signal. Average it away and you have thrown out the only useful part.
• Treat a wide spread as a flag, not noise. When one person scores a 9 and another a 3, stop and talk. That gap is where the risk or the insight is hiding.
• Make Confidence do real work. A high Impact at low Confidence is a guess. Force people to say what would raise their confidence, and you have found your next cheap experiment.
• Re-score after you ship. Compare what you predicted to what happened. A team that never checks its old scores never learns whether its instincts are any good.

They've run this a hundred times

A prioritization argument is hard to win from inside it. These product mentors have made the calls, shipped the roadmap, and seen which scores lied.

Dimitris Farmakis

Founder and principal consultant. Product management and operations across real roadmaps.

Book a call

David Kelly

GM of AppSumo Originals. Product management and go-to-market at scale.

Book a call

Morgan Schofield

Head of Growth. Product-market fit and the experiments that move the metric.

Book a call

Product mentors who've made the call

The score is not the decision.
Someone who has shipped the roadmap is.

Use the framework to surface the argument. For the call you cannot get wrong, talk to a product mentor who has made it before, and keep them for the next planning cycle.

Talk to a mentor