Every roadmap gets hijacked — by the highest-paid person's opinion, by whatever shipped at a competitor, by the shiniest idea in the room. RICE cuts through it with one comparable number per initiative: Reach × Impact × Confidence, divided by Effort. It makes the trade-off explicit and arguable, and — crucially — the Confidence term quietly drags over-hyped, low-evidence bets down the list where they belong. Score a few initiatives below and watch the order sort itself out.
Reach = how many people it touches (per quarter). Impact = how much it moves the needle for each of them. Confidence = how sure you actually are (the honesty discount). Effort = the cost in person-months. Drag the dials — the score recomputes and the ranking re-sorts live. Watch what happens to the hyped feature when you tell the truth about its confidence.
| # | Initiative | Reach/qtr | Impact | Confidence | Effortmo | RICE |
|---|
Plenty of teams already sort by "value vs effort". RICE adds the two things that intuition skips: Reach (how many people, not just how much you care) and Confidence (a built-in discount for hype and thin evidence). Here's where it sits among the usual methods.
| Method | What it weighs | Best for | Blind spot |
|---|---|---|---|
| Gut / HiPPO | Whoever's most senior or loudest | Nothing, really | Confuses conviction with evidence |
| Value vs Effort 2×2 | Rough value, rough effort | A quick first cut | Ignores reach and confidence |
| RICE | Reach × Impact × Confidence ÷ Effort | Comparing many initiatives fairly | False precision if you fake the inputs |
| MoSCoW | Must / Should / Could / Won't | Scoping a release | No sense of magnitude within a bucket |
| Kano | Delight vs basic expectation | Understanding satisfaction | Not a throughput ranking |
The Confidence term is the point. A dazzling idea you have no evidence for gets multiplied by a small number and falls down the list — exactly where a cheap experiment, not a big build, belongs.
Plot the same initiatives on value (Reach × Impact × Confidence) against effort. The top-left is the promised land — high value, low effort. It updates live as you tune the dials above, so you can watch an initiative slide between quadrants.
Four situations product teams meet every planning cycle.
Loud, senior, and everyone assumes it's next. Score it honestly and its low confidence and narrow reach drop it below a boring bug fix that touches every user.
Potentially huge, but you're guessing. RICE says: don't build it yet — run a cheap experiment to raise the confidence term first, then re-score.
Exciting demo, months of work, tiny reach. The effort denominator sinks it — the score protects the quarter from a vanity project.
A one-week fix that helps everyone. Unglamorous, so it never gets airtime — until it tops the RICE ranking and becomes impossible to ignore.
RICE isn't a machine that decides for you; it's a shared language that makes the trade-offs visible so a team can argue about the right things — the inputs — instead of the loudest voice. Getting honest about reach and confidence is where the real discipline lives, and it's the work we do with the product teams we coach.
Talk to us about product coachingThe term everyone drops is the one that keeps you honest. Low evidence, low score — go get evidence before you build.
A transparent score turns "because I said so" into "let's argue about the reach number" — a far better argument to have.
Cheap, high-reach fixes rarely get airtime. The ranking drags them to the top where they belong.