RICE vs cost of delay: two prioritization frameworks compared
· 5 min read
Every team has more good ideas than capacity. Without a method, the roadmap goes to whoever argues longest or asked most recently. Two frameworks cover most situations: RICE for choosing what is worth doing, and cost of delay for deciding what to do first.
RICE: value for effort
RICE scores an initiative as Reach × Impact × Confidence ÷ Effort.
- Reach: how many users or events it affects in a period.
- Impact: a scaled estimate of the effect on each — for example 0.5 for small, 1 for medium, 2 for large.
- Confidence: a percentage that discounts guesswork.
- Effort: person-months of work.
An idea reaching 2,000 users with an impact of 2, 50% confidence and four person-months of effort scores 2,000 × 2 × 0.5 ÷ 4 = 500. On its own that number means nothing. Against other scores it produces a ranking.
RICE is good at exposing weak ideas. A loudly supported feature with low reach and shaky evidence scores badly, and the score makes the reason visible. Its weakness is that it ignores time. It tells you what is worth doing, not whether one thing is more urgent than another.
Cost of delay: what waiting costs
Cost of delay asks what each week without this is worth. Divide that by the duration of the work and you get CD3 — cost of delay divided by duration. Do the highest score first.
Two projects compete for one team. A is worth $40,000 a week once live and takes eight weeks. B is worth $15,000 a week and takes two. A looks bigger. But A's CD3 is 5,000 and B's is 7,500.
Check it by adding up what is lost while waiting. B first: B waits two weeks ($30,000) and A waits ten ($400,000), a total of $430,000. A first: A waits eight weeks ($320,000) and B waits ten ($150,000), a total of $470,000. Doing the smaller project first saves $40,000, with the same work and the same team.
Where each one fails
- RICE invites false precision. The inputs are estimates, so treat close scores as ties.
- RICE undervalues work with no direct user reach: infrastructure, security, compliance.
- Cost of delay needs a money figure, which is hard for early or exploratory work.
- Both ignore dependencies. A low-scoring item that unblocks three others may still come first.
Which to use
Use RICE when you have a long list of candidate ideas and need to cut it down. Use cost of delay when you have a short list of committed work and need to sequence it, especially when deadlines or revenue are involved. Many teams use both: RICE each quarter to choose, CD3 each sprint to order.
Neither replaces judgment. Their value is that they make the reasoning visible, so that a disagreement becomes a discussion about an input — is the reach really 2,000? — rather than a contest of opinions.
