RICE Scoring
Reach × Impact × Confidence ÷ Effort gives you a number — but the number only means something if the conversation behind it was honest.
Why PMs should care
RICE's main value is that it gives stakeholders a shared vocabulary for disagreeing. The real win isn't the final score; it's the conversation you're forced to have about what each word means.
What does reach actually count here — users who see the feature, users affected by it, or users who finish the new flow? What does impact mean — revenue, retention, activation, or something qualitative? And confidence, the column most teams underuse — a weak signal should feel different from a strong one, even when the final score is the same.
Treat RICE as a thinking tool that happens to produce a number, not a number that happens to produce thinking. Two projects with identical scores often need very different plans, and the framework helps you see that — if you let it.
Example in product work
Two features come up at the quarterly review, both scoring 14 on RICE.
Feature A: New onboarding video (Reach 100%, Impact 2, Confidence 90%, Effort 13).
Feature B: AI portfolio coach (Reach 60%, Impact 3, Confidence 30%, Effort 4).
The equal scores suggest a tie. The framework says: A is a safe incremental bet, B is a long-shot with asymmetric upside. You should not ship them in the same quarter the same way — A needs a rollout plan and a success metric; B needs a 2-week spike to move the confidence number before it's a real roadmap item.
The scores were identical. The decisions couldn't be more different.
What to do when you see it
- RICE's real value is the conversation it forces, not the final number.
- Define what each term means before you score: Reach as what? Impact by which metric? Confidence based on what evidence?
- Confidence is the most underused column. A 30% score and a 90% score with the same total are very different bets.
- Two items with the same RICE score can still need completely different plans. Use the framework to expose that.
Sources & further reading
- RICE: Simple prioritization for product managers — Intercom, Sean McBride, 2018The original article where Sean McBride, then at Intercom, introduced the RICE framework.
- RICE Scoring Model — ProductPlanA concise, practical explainer covering the four factors, the formula, and common pitfalls.