RICE is fine. Here is what it quietly leaves out.

RICE — Reach, Impact, Confidence, Effort — is the default prioritization framework for a reason. It is simple, auditable, and forces you to be explicit about your assumptions. We use it. We also know its failure modes well enough to compensate for them.

What RICE measures well

• Comparing items within the same category of work
• Forcing your team to write down their confidence level rather than assuming certainty
• Giving stakeholders a number to push back on instead of a gut feeling

What RICE systematically undercounts

The framework has three blind spots we patch manually:

• Strategic alignment: A high RICE score on a feature that pulls you away from your core positioning is a trap.
• Reversibility: A low-effort item that is hard to undo deserves a penalty that RICE does not apply.
• Second-order effects: Some features unlock a whole category of follow-on work. RICE values each item in isolation.

A scoring framework gives you a ranked list. It does not give you a roadmap. Those are different things.

The one column we always add

Next to the RICE score we add a “veto flag” column. Any item can be flagged by any team member for a synchronous conversation. The flag does not override the score — it just creates a forcing function to discuss the things the framework cannot see.