RICE prioritization without the false precision

A useful score starts with a shared question and honest estimates. Here’s a practical way to use one.

A backlog can contain ten sensible ideas and still leave a team unsure what to do next. Before scoring anything, write down the outcome you want to improve and the period you are planning for. Comparing ideas against different goals creates a tidy table with a confused answer.

Use one set of units Intercom’s RICE framework combines reach, impact, confidence, and effort: reach × impact × confidence ÷ effort. Reach needs a consistent time window. Effort should include everyone involved and use the same unit across ideas. Confidence is entered as a percentage and converted to a fraction in the calculation.

Make the assumptions inspectable Imagine two fictional improvements. One reaches 400 people, has impact 1, confidence 80%, and effort 2 person-months. Its score is 160. Another reaches 100 people, has impact 2, confidence 50%, and effort 1. Its score is 100. These are planning estimates, not measured future returns.

Ask what evidence would change either estimate. A support log might clarify the first idea’s reach. A small usability study might change the second idea’s assumed impact. Keep those questions beside the score so that disagreement can lead to a useful investigation.

Review the order together A dependency or essential baseline capability can justify doing a lower-scoring item first. Record the reason and revisit estimates as evidence changes.