The RICE framework explained: RICE scoring as Reach × Impact × Confidence ÷ Effort, what each scale means, a worked example with six ideas and common traps.
By Sergey BruhPublished 9 min read
A free course for PMs and marketers: short lessons, real product data and exercises with instant feedback.
Start the free courseThe RICE framework is a prioritization framework that ranks ideas by Reach × Impact × Confidence ÷ Effort: how many people an idea affects in a given period, how much it changes things for each of them, how sure you are about those two estimates and how much work it takes. The result is a rough "value per unit of effort" number that puts very different ideas on one scale. More importantly, it makes the reasoning behind a priority visible, so people argue about the estimates instead of about whose idea it is. Treat it as a tool for a better conversation, not a machine that makes the decision for you.
The first three multiply value; effort divides it. Double the effort and the score halves; halve the confidence and it halves too.
Reach and effort are counts. Impact and confidence use fixed steps, so nobody can quietly score an idea "2.7":
Three rules keep the numbers comparable. Use the same period for every item's reach. Score impact against one goal, the objective on your roadmap, not "value" in general. And agree in advance what "high" impact means, with an example from past work. An idea below 50% confidence is a bet, not a plan: run a cheap experiment first.
A Ukrainian B2B SaaS helps about 4,000 small online shops manage orders and deliveries. This year's objective is to keep more shops paying, measured by the share of new shops still paying after 90 days. The team has six candidates for next quarter. Reach is shops per quarter; impact is how much an idea moves a shop it reaches towards staying.
Scores 4 and 6 are rounded (266.67 and 93.75). To score your own list, the free RICE calculator does the arithmetic and ranks the ideas. Here is one row in full, bulk labels:
Where the estimates came from:
The top two are clear: small, well understood and backed by evidence. Below them, the gaps are smaller than they look. Every score multiplies four estimates, so a difference of 400 against 267 says less than the digits suggest. A useful habit: treat scores that are close as ties and let other arguments decide.
Then ask which single estimate would change the order. If the onboarding checklist takes 3 person-months instead of 1, its score drops from 1,200 to 400, level with abandoned-cart messages. That effort estimate is the one to check before committing. If a quick prototype raised confidence in marketplace sync to 80%, its score would go from 150 to 240: still below the dashboard's 267, so, practically, a tie. A cheap experiment that raises confidence is often worth more than another meeting about the scores.
The mobile app's score also does a job: it turns a loud request into an explainable "not now". Saying no is easier when the reasons are on the table.
A score of 266.67 looks exact, but it's the product of four guesses. Round the scores, group them into bands (high, medium, low) and never argue about decimals.
Whoever wants an idea tends to rate its impact a 3 and its confidence 100%. Guard against it: define the scale with real examples, score as a group rather than alone, ask for evidence behind any confidence above 50%, and compare estimates with actual results after launch, so the team's guesses get better over time.
RICE ranks items that serve the same goal. Put a retention feature, a legal requirement, a database upgrade and a bet on a new market on one scale and the ranking means nothing: a law you must follow isn't "impact 2". Sort work into buckets first. Must-dos (legal, security, enabling work) go ahead by definition; split the remaining capacity between buckets; use RICE inside each one. Watch for reach bias too: RICE favors ideas that touch many people over deep value for a small but important segment, such as your largest customers.
RICE has no time dimension. A seasonal window or a contract deadline is invisible to it, which is why cost of delay exists (see below).
On an outcome-based roadmap, RICE works at two levels. Inside a theme, it helps choose which candidate solution to try first; in the example, all six ideas serve one objective. Across themes, it can order the queue in the Next column of a Now Next Later roadmap, as long as every theme is scored against the same objective. In both cases, estimate impact against the theme's signal, and the scores stay tied to a result instead of to opinions.
Reach, Impact, Confidence and Effort. The first three estimate the value of an idea and how sure you are about it; effort is the cost. The score is the first three multiplied together and divided by effort.
There is no absolute benchmark. A score only means something compared with other ideas scored by the same team, with the same scales, the same reach period and the same goal. A 960 in one team and a 960 in another aren't comparable.
Not automatically. The ranking is a starting point for a discussion: check which estimates are shakiest, what would change the order and whether something urgent or mandatory sits outside the scoring. Then decide, and write down why.
Start with the free lesson What a roadmap is (and isn't): a CEO asks for every feature with a month next to it, and you practice answering with direction instead of dates. Module 4 of the free course Outcome-Based Product Roadmaps is about prioritizing: Why gut feeling fails covers criteria and bias, Scoring frameworks walks through value vs effort and RICE, and Trade-offs and saying no shows how to turn a ranking into a decision people accept.
