Prioritization & decisions · Scoring model

RICE

Compare initiatives using reach, impact, confidence, and effort on a common time horizon.

Beginner30 minPlanning · Growth
Learn in 5 minutesWork my problem

Start here · 5-minute visual lesson

Estimate how many people an initiative reaches, how much it changes the outcome, how sure you are, and how much team effort it consumes.

Think of it like this: A disciplined value-per-effort estimate with an explicit penalty for weak evidence.

Without the framework

A clever idea wins because it is exciting or backed by the loudest stakeholder.

With the framework

Every candidate exposes audience size, expected change, evidence quality, and total cross-functional cost.

Learn by deciding

Three onboarding ideas enter the room

1

A checklist reaches 4,000 users; concierge setup reaches 200. Why does that matter?

2

The team calls every idea “high impact.” What is broken?

3

The highest score conflicts with a contractual dependency. What wins?

01 · Understand

In plain English

RICE estimates total impact per unit of team effort and explicitly discounts uncertain bets.

Origin and context

Intercom developed RICE from its own prioritization practice. Sean McBride’s 2018 write-up specifies the four factors, common impact and confidence scales, and person-month effort.

The problem it solves

Teams overweight exciting ideas, personal preferences, or easy work. RICE makes assumptions legible and comparable—without pretending the score is a decision.

The concepts, explained

Learn the vocabulary first. Each concept changes a decision you will make when using the framework.

Reach

How many people, accounts, or transactions the initiative will affect during one shared time period.

Impact

The expected change for each person reached, scored with one consistent scale tied to the outcome.

Confidence

A discount for uncertainty. Strong behavioral evidence earns more confidence than opinion or enthusiasm.

Effort

The total cross-functional work required, usually measured in person-months—not engineering time alone.

RICE score

Reach × impact × confidence ÷ effort. Use the result to expose assumptions and compare options, not to automate the final decision.

02 · Deep dive

Go beyond the definition

Follow the reasoning inside RICE, then challenge it before you use it.

1 of 4mental model

The mental model

What changes in the way you see the problem

01

Reach per fixed period

Use this concept to examine the problem from a distinct RICE perspective.

02

Impact per reached unit

Use this concept to examine the problem from a distinct RICE perspective.

03

Confidence in the estimates

Use this concept to examine the problem from a distinct RICE perspective.

04

Effort in person-months

Use this concept to examine the problem from a distinct RICE perspective.

05

Score = Reach × Impact × Confidence ÷ Effort

Use this concept to examine the problem from a distinct RICE perspective.

03 · Apply

How to use RICE

  1. 01

    Define the outcome and one time horizon for every candidate.

  2. 02

    Estimate reach from observed funnel or usage data.

  3. 03

    Choose a consistent impact scale tied to the outcome.

  4. 04

    Rate confidence from evidence quality, not enthusiasm.

  5. 05

    Estimate total cross-functional person-months.

  6. 06

    Calculate, sort, and inspect surprising scores.

  7. 07

    Apply explicit constraints, dependencies, strategy, and risk before deciding.

04 · See it work

A worked example

Three onboarding initiatives use one quarter. Guided import: 1,200 reach × 2 impact × 80% confidence ÷ 3 person-months = 640. Welcome checklist: 4,000 × 0.5 × 100% ÷ 1 = 2,000. Concierge migration: 200 × 3 × 50% ÷ 2 = 150. The checklist ranks first, but an enterprise contract dependency may still justify migration work.

Business case study

Illustrative fictional scenario

A B2B analytics team scores onboarding bets with invented figures, records evidence beside every factor, and reserves 20% capacity for reliability work outside RICE. The scenario demonstrates judgment around the score; it is not a claim about a real company.

Across company types

Startups can use broad ranges and sensitivity checks; enterprises can add a separate mandatory-work lane. Use units consistently across B2B accounts, B2C users, or marketplace transactions.

05 · Work your problem

Turn the framework into a result

Framework workbench

Work RICE on your problem

Paste the situation as you know it. The Atlas will turn your inputs into a framework-specific decision draft.

Runs locally

Explore the mechanics

RICE score: 640
Copy the working template
Initiative,Reach (per quarter),Impact (3/2/1/.5/.25),Confidence (1/.8/.5),Effort (person-months),RICE score,Decision note

06 · Use judgment

Where it helps—and where it breaks

Use when

  • Candidates share an outcome and horizon
  • Reach differs meaningfully
  • You can estimate cross-functional effort

Do not use when

  • Safety, legal, or contractual obligations are being ranked
  • Initiatives pursue incompatible outcomes
  • Inputs are fabricated to justify a favorite

Advantages

  • Simple and auditable
  • Confidence exposes evidence quality
  • Normalizes by effort

Limitations & criticisms

  • Impact scale is subjective
  • False precision can hide weak inputs
  • Dependencies and strategy are outside the formula

Common failure modes

  • Mixing monthly and quarterly reach
  • Counting engineering effort only
  • Automatically accepting the sorted order

Often confused with

ICE omits reach and usually uses impact, confidence, and ease; RICE uses effort as a divisor and is better when audience size varies.

Practical checklist

Reflection questions

  • Which input could reverse the ranking?
  • What important obligation is intentionally outside the score?

07 · Check

Five-question knowledge check

1. What divides the RICE numerator?
2. Confidence should represent…
3. Can the highest score be rejected?
4. Reach requires…
5. Person-months include…

Key takeaways

  • Compare initiatives using reach, impact, confidence, and effort on a common time horizon.
  • Simple and auditable
  • Impact scale is subjective

08 · Go deeper

Sources and further reading

  1. RICE: Simple prioritization for product managersSean McBride · Intercom · 2018-01-05

    RICE factors, scales, formula, and intended use.

  2. RICE Scoring ModelProductPlan · ProductPlan

    Independent explanation of the four factors, person-month effort, and use in roadmap prioritization.