RICE Prioritization Framework
Reach, Impact, Confidence, Effort — one score, one ranked backlog.
Scoring · 5 min
●●●
RICE = (Reach × Impact × Confidence) ÷ Effort
- Inputs
- Reach (users/qtr) · Impact (0.25–3) · Confidence (0–1) · Effort (person-months)
- Output
- A single comparable score per initiative
- When to use
- Weekly backlog grooming for a single product team that needs a fast, defensible rank.
- Replaces
- Gut-feel priority calls and stakeholder volume contests.
RICE is the product prioritization framework Intercom popularised: rank every initiative by (Reach × Impact × Confidence) ÷ Effort. It is the fastest defensible way to take a forty-item backlog and produce a ranked list the whole team can debate from. This guide walks the formula, the rubrics for each input, the worked example most teams need, and the failure modes that send teams looking for FVI or NPV instead.
Interactive
RICE Score Calculator
Score one initiative end-to-end. The output updates live as you change the inputs.
RICE Score
1,600
(4,000 × 1 × 0.8) ÷ 2 = 1,600
The RICE formula
RICE Score = (Reach × Impact × Confidence) ÷ Effort. Reach is the number of people affected per time period (usually per quarter). Impact is a five-point multiplier — 0.25 minimal, 0.5 low, 1 medium, 2 high, 3 massive. Confidence is the percentage of how sure you are about the other three numbers (50%, 80%, 100%). Effort is total person-months across product, design, and engineering. Run the math; the highest score ships first.
Scoring Reach
Reach is concrete: users, signups, transactions, support tickets per quarter. Anchor it to an actual analytics number, not a percentage of the user base. If a change touches 3,000 active users per quarter, Reach is 3,000 — not 'most of our users'.
Scoring Impact
Impact is the per-user lift on the goal you actually care about: activation, retention, conversion, revenue. Use the five-point scale (0.25, 0.5, 1, 2, 3) so the room can't smuggle false precision into the score. If two initiatives look like they should both be a 3, you do not have enough information yet.
Scoring Confidence
Confidence is the haircut. 100% means you have data — an A/B test, a benchmark, a working prototype. 80% means you have a reasonable analogy. 50% means you are guessing. Anything lower, kill the score and go gather more evidence before bringing it back.
Scoring Effort
Effort is total person-months across PM, design, and engineering combined — not engineer-only weeks. Round to the half-month. If you cannot estimate it within a 2× range, the initiative needs a spike, not a score.
Worked example
Redesigning the empty-state of the inbox. Reach = 4,000 users/qtr. Impact = 1 (medium lift on activation). Confidence = 80% (we have a benchmark from a similar redesign). Effort = 2 person-months. RICE = (4,000 × 1 × 0.8) ÷ 2 = 1,600. Compared head-to-head against a 'new AI summarizer' at Reach 8,000 × Impact 2 × Confidence 0.5 ÷ Effort 6 = 1,333, the unsexy empty-state work wins.
Where RICE breaks
RICE outputs an abstract number, not a dollar amount. The moment finance asks 'how much money is that?' the framework runs out. RICE also bundles Reach and Impact into a single multiplier that can hide a 10× swing in dollar value. For team-level grooming, RICE is enough; for board-level prioritization, switch to FVI (dollar-denominated) or NPV (time-discounted dollar value).