The output is a ranked table of options. Each row gets Reach, Impact, Confidence, Effort, Score, and the assumption most likely to change the order.
loading…
prioritization framework
Prioritize competing product bets when they share one goal, one time window, and one delivery unit.
Score = Reach x Impact x Confidence / Effort
quick answer
RICE is a scorecard for comparable options. It makes reach, impact, confidence, and effort visible so a team can inspect the ranking instead of arguing from taste.
The output is a ranked table of options. Each row gets Reach, Impact, Confidence, Effort, Score, and the assumption most likely to change the order.
Use it when several roadmap bets compete for one customer or business outcome.
Do not use it to compare unrelated goals, strategic choices, or risk commitments that need judgment before scoring.
worked example
For RICE, the useful artifact is a ranked table: one row per option, one shared goal, one reach window, and one assumption to watch.
Improve new-user activation next quarter.
Every option estimates users reached in that quarter.
Pick the first bet and watch the assumption that could change the rank.
RICE ranks comparable options for one goal: Improve new-user activation. Use the scorecard to choose the first bet, then test the assumption most likely to change the order.
Fix onboarding drop-off ranks first because it reaches far more users in the same quarter.
If confidence on onboarding falls, or SSO is tied to a committed enterprise deal, the rank can change.
Use the scorecard to choose the first bet and name the assumption to validate next.
generate yours
Start with one goal, one time window, and the competing options. Ask PL will ask only for missing RICE values, calculate the ranked table, and explain what could change the order.
Use RICE to score these product options. Goal: [What outcome are we optimizing for, and over what time window?] Options: 1. [Option] 2. [Option] 3. [Option] Use one reach window for every option. Ask for any missing Reach, Impact, Confidence, or Effort values before scoring. Then show the ranked RICE table and the assumption most likely to change the order.
how to use it
RICE is useful when it forces a sharper prioritization conversation. The score starts the decision; it does not replace product judgment.
Name the outcome and period every option is competing against, such as activation next quarter.
Keep unrelated strategy, risk, and commitment questions out of the table unless they serve the same goal.
Use the same reach unit, impact scale, confidence meaning, and effort unit for every row.
After sorting by score, name the assumption that would most likely change the ranking.
quality check
Use this check after the scorecard is filled, not as another definition of the acronym. A useful RICE review asks whether the rows are comparable and whether the evidence behind each number is strong enough to make the call.
RICE ranks options only when they are trying to move the same goal.
Reach must use one audience unit and one time window, or the ranking becomes fake precision.
Confidence should reflect evidence quality, not how much the team wants the idea to win.
Include the whole cost of getting the change into customers' hands.
common mistakes
Do not rank activation work, enterprise revenue work, and platform risk in the same table unless one goal clearly wins.
Reach must use the same audience unit and time window for every row.
Confidence should reflect evidence quality, not how much the team wants the idea to win.
Include design, QA, migration, launch, support, and coordination work. Shipping cost is more than build time.
RICE creates a starting rank. Strategy, risk, commitments, and sequencing can still override the table.
use something else when
Use this when reach is unknowable and you still need a quick product-ranking pass.
Use this when the conversation is about commitments, release scope, or must-have requirements.
faq
RICE scoring is a prioritization method that ranks options by Reach, Impact, Confidence, and Effort.
Multiply Reach by Impact and Confidence, then divide by Effort. Use the same reach and effort units for every option.
Reach is the number of users, accounts, deals, incidents, or other units affected in a fixed period. Pick one unit and use it for every option.
Use a small shared scale such as 0.25, 0.5, 1, 2, and 3. The exact scale matters less than using it consistently and explaining the reason behind each score.
Confidence should reflect evidence quality. Measured data should score higher than customer anecdotes, and both should score higher than internal opinion.
Effort should include the whole cost to ship: engineering, design, QA, rollout, migration, support, and coordination. Under-counting effort is the fastest way to distort RICE.
Use RICE when several product options are competing for the same goal and you can estimate audience size, likely impact, evidence quality, and delivery cost.
Avoid RICE when strategy, risk, or sequencing matters more than comparable reach. Consider ICE Scoring if it better matches the decision.
There is no universal good score. A score is only meaningful relative to other options scored with the same units, time window, and effort estimate.
Only if they share the same goal and unit of reach. If one option reduces risk and another grows revenue, use RICE for one lens and add a separate strategic or risk review.
The common mistakes are mixing reach units, inflating confidence, hiding coordination cost inside effort, and treating the rank as a decision instead of a starting point.
ICE uses Impact, Confidence, and Ease. RICE adds Reach and divides by Effort, which makes it better when audience size and delivery cost vary meaningfully.
MoSCoW sorts requirements into Must, Should, Could, and Won’t. RICE produces a relative numeric ranking for comparable options.
Update scores when the goal, reach estimate, evidence, or effort changes. Do not keep old RICE scores around as if they are permanent truth.
Yes. Add your goal and options, then Ask PL can ask for missing inputs, calculate the score table, and render the RICE scorecard for your context.