---
title: RICE Prioritization · Scoring What to Build Next · RGM Frameworks
url: https://realgrowthmatters.com/learn/frameworks/rice-prioritization-framework/
updated: 2026-06-10
source_html: https://realgrowthmatters.com/learn/frameworks/rice-prioritization-framework/
---

**Original concept & attribution.** RICE was developed and published by Sean McBride at Intercom in 2016 as an internal scoring model for prioritizing product roadmap bets. Intercom published the framework openly and it has since become standard in product management. This article reviews the model and adds the gotchas we've seen in practice.

## The formula

RICE scores each candidate initiative on four factors and combines them into a single number:

**RICE Score = (Reach × Impact × Confidence) ÷ Effort**

- **Reach.** How many people will this affect in a given time period? Estimated in absolute units (users per month, transactions per quarter, etc.).
- **Impact.** How much will it affect each of those people? Intercom uses a 0.25 / 0.5 / 1 / 2 / 3 scale (minimal / low / medium / high / massive).
- **Confidence.** How confident are you in the Reach and Impact estimates? Percentage (50% / 80% / 100%).
- **Effort.** Person-months required to ship.

Higher scores get priority. Lower scores get cut or deferred.

## Why it works

Keep going · Free training

### Measurement & Attribution

Concepts only go so far. Operate them — RGM's measurement training covers GA4 setup, attribution model selection, MMM basics, and incrementality testing. Hands-on, free.

[Start the training →](/training/)

Most prioritization conversations devolve into HiPPO (highest-paid person's opinion) or politics. RICE forces a structured argument: every initiative needs explicit numbers for each factor. The math reveals trade-offs that intuition hides — a high-impact, low-reach initiative often loses to a medium-impact, high-reach one once you do the math.

It also forces explicit confidence. If your team can't agree on whether something is 50% or 80% confidence, that's itself a signal — go research the question before you build.

## Where RICE breaks

The framework assumes you can estimate the four factors. For exploratory bets, novel features, or strategic moves with second-order consequences, the estimates are guesses dressed up in numbers.

It also weights short-term thinking. Effort is in the denominator, so multi-quarter foundational work always scores worse than quick wins. Teams that run RICE strictly end up over-investing in optimization and under-investing in platform.

**RGM operator perspective.** We use RICE for tactical roadmap decisions inside a quarter. We do not use it for strategic decisions across quarters. Long-horizon strategic work needs its own frame.

## The operator-side adjustments

**Separate strategic bets from optimization.** Don't score them against each other. Run RICE inside the optimization track only. Strategic bets get their own conversation.

**Use confidence honestly.** A 100% confidence score should be rare. Most well-researched initiatives are 70–80% confidence at best. When everything is 100%, the team is gaming the score.

**Re-score quarterly.** Initiatives that scored well in Q1 might score differently in Q3 because the world changed. Treat scores as snapshot, not permanent.

## Alternatives worth knowing

**ICE Scoring** (Sean Ellis): Impact × Confidence × Ease, all on 1–10 scales. Simpler than RICE, useful for high-volume A/B test backlogs.

**PIE**: Potential × Importance × Ease. Used in CRO contexts (Bryan Eisenberg).

**Weighted shortest job first (WSJF)**: From SAFe (Scaled Agile Framework). Cost of delay ÷ job size.

**Kano model**: Categorizes features as basic, performance, or delighters. Less score-driven, more strategic.

### Related on RGM

- [OKRs](/learn/frameworks/operating-cadence-okrs/) — what RICE prioritization rolls up into.
- [Growth loops](/learn/frameworks/compounding-growth-systems/) — context for what to score against.
- [Tools](/tools/) — calculators that feed RICE inputs.

Sources & further reading

1. McBride, S. (2016). *RICE: Simple Prioritization for Product Managers*. Intercom blog. [intercom.com/blog/rice-simple-prioritization-for-product-managers](https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/)
2. Ellis, S. (various). On ICE scoring methodology — referenced in *Hacking Growth* (2017).
3. Eisenberg, B. PIE framework — origin in Future Now / Buyer Legends work.
4. Leffingwell, D. SAFe documentation on WSJF.
5. RGM operator notes 2023–2026.