Page 169 · Module 07, Operate with Precision · this screen continues that page

All 108 frameworks
7.5IntermediateModule 07 · Operate with Precision

RICE Scoring

Prioritise your product roadmap with four numbers that matter

The prompt

Copy & paste ready
7.5RICE Scoring
Act as a product prioritisation consultant using the RICE framework. Product context : [WHAT THE PRODUCT DOES, STAGE, KEY METRIC] Time period for scoring : [MONTH / QUARTER] Score each feature / initiative using RICE: REACH : Users affected in the time period (real number) IMPACT : 3=massive / 2=high / 1=med / 0.5=low / 0.25=min CONFIDENCE : % certain this impact will happen (100/80/50%) EFFORT : Person-months to build and ship RICE = (Reach × Impact × Confidence) ÷ Effort Initiatives to score: [LIST YOUR 5–8 FEATURES OR INITIATIVES] After scoring: 1. Rank by RICE Score 2. Flag any item where Effort is the swing factor, would a smaller version change the ranking? 3. Identify the highest-RICE item that is being deprioritised for non-RICE reasons RICE Scoring — Effort Divides, Not Just Adds Reach Impact Confidence Effort Idea A High RICE RICE Score Idea B Low RICE
LabelsReplace theseSwap the role below

LabelsReplace theseSwap the role below

Pro tip, from the book

The most important RICE output is the item that is being deprioritised for non-RICE reasons. Politics, founder preference, and squeaky wheels all suppress high-RICE items. When you see a high-scoring item consistently skipped, that is where organisational dysfunction is most visible and most expensive.

Who should run this prompt

Module role profile

Who should audit and improve your operations? Operations problems hide in plain sight — in the handoffs nobody notices, the processes nobody has documented, and the decisions nobody has questioned. The roles on this page bring the discipline of people who have built systems that run without heroics. Use them to find what is broken before it breaks you, and to build what scales before you need it to.

Choose any role to drop it into the prompt above. Only the highlighted opening clause changes — the rest of the prompt stays exactly as printed.

Internal rolesThink from inside the organisation
Outside perspectivesChallenge your blind spots

◆◆◆◆◆ → ◆ seniority, board level down to specialist outside the organisation

How to make any role sharper

  1. Add years of experience: "...with 15 years in enterprise SaaS" produces different depth than just the title.
  2. Add what they care most about: "You care most about [X]" shapes every word of the output.
  3. Add their communication style: "Be direct. Flag risks first. No jargon." changes the tone entirely.
See also: 1.3 Role Prompting - The Expert Chair

Use this when

The problem it solves

Your product roadmap is driven by whoever has the most compelling story in the room. Engineering estimates don't account for how many customers will actually be affected. You're building things that feel important but don't move the metrics.

How the framework works

From the printed page

RICE was developed by the Intercom product team as a more rigorous alternative to ICE for product decisions. It scores across four dimensions: Reach (how many people will this affect in a given time period?), Impact (how much will it move the metric per person scored 0.25 to 3x), Confidence (how sure are we, as a percentage?), and Effort (how many person-months to build?). RICE Score = (Reach × Impact × Confidence) ÷ Effort. Dividing by Effort is the key difference from ICE it ensures that a small, high-impact feature beats a large, medium-impact one if the effort difference is significant.

The method, in four moves

Do these in order
1

Use real data for Reach, not projections. If you don't know, use Confidence to discount it.

2

Impact uses a fixed scale: 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal.

3

Effort should be in person-months, not story points it forces cross-team thinking.

4

Run RICE in a 30-minute team session group scoring removes individual advocacy bias. RICE looks like math, but Confidence and Impact are opinions with decimal points. Group scoring reduces bias, it doesn't remove it. Don't let the formula outrank your judgment on what the customer actually needs. A Score Feels More Objective Than It Is

Where the framework comes from

Intercom product team — RICE Scoring framework, 2016

When this page changes, your copy of the book does not have to.

The book prints the framework. This page keeps it — and keeps the prompt current, because prompting technique moves faster than print does. When it moves, this page is rewritten and the code in your copy keeps pointing at it. No second edition, no replacement purchase, no account.

If something here looks wrong — a prompt that does not match its framework, a figure that reads oddly — tell Raphy. That correction reaches every printed copy at once.

Framework7.5 of 108
Printed onPages 168169
Prompt extracted18 Sept 2026
Costs to readNothing, no account

Copying is free. An account keeps them.

Nothing on this page is behind a login and nothing ever will be. Save any prompt to your own list, pick up on another device, and send a colleague a link with your name on it. No card, no trial, no paywall on the prompts themselves.

See how it works
Save this framework to your own list
Pick up where you left off on another device
Send a colleague a link with your name on it