RICE Scoring

RICE is a prioritization framework that scores ideas with Reach, Impact, Confidence, and Effort. The classic formula is (Reach × Impact × Confidence) ÷ Effort. It forces teams to quantify tradeoffs instead of debating whoever argues loudest in the planning meeting. Used well, RICE creates a shared language for “why this, not that.”

Reach estimates how many users or events you will affect in a period. Impact rates how much it moves the needle for those people (often a simple scale). Confidence discounts shaky assumptions. Effort captures person-months or t-shirt sizes so cheap experiments can beat heroic projects when the upside is similar.

RICE sits on top of customer feedback, not instead of it. Votes and interviews inform Reach and Confidence; Impact still needs product judgment about strategic fit; Effort comes from engineering. A feedback board without scoring becomes a popularity contest; scoring without feedback becomes opinion with math cosplay.

Common pitfalls: fake precision (pretending you know Reach to the person), inconsistent scales across teammates, and never revisiting scores when learning arrives. Calibrate as a group on a few examples, write down definitions, and treat scores as decision aids — not immutable law. Strategy themes can override a mid-ranked RICE item when positioning demands it; just say so explicitly.

After scoring, communicate outcomes on the roadmap. Items that win get planned statuses; items that lose get a clear “not now” so requesters are not left guessing. When winners ship, changelog notes complete the story. Upwip helps by keeping the feedback demand signal next to roadmap prioritization, while guides like RICE remain your decision framework.

Start with a lightweight sheet or board fields for the four inputs on your top twenty candidates. Rank, discuss outliers, then commit a short list. Re-score monthly as data improves. RICE will not remove hard choices — it will make them explainable to founders, engineers, and customers alike.