Roadmap Prioritization: Beyond RICE

RICE—Reach, Impact, Confidence, Effort—is the most widely adopted prioritization framework in product management. It is also widely misapplied. This paper examines the structural limitations of RICE, proposes a layered prioritization model that addresses those limitations, and offers practical guidance for teams navigating complex roadmap decisions under uncertainty.

1. Where RICE Works—and Where It Doesn't

RICE was developed at Intercom to bring rigor to feature prioritization decisions that had previously been made on intuition and political influence. For this purpose—comparing discrete feature candidates within a defined product scope—it works reasonably well. It creates a shared vocabulary for tradeoffs and forces teams to make their assumptions explicit.

The problems emerge at scale and at the strategic level. Specifically, RICE struggles in four situations:

• Platform and infrastructure work: Foundational investments often have low measurable reach in the near term but enable disproportionate future value. RICE systematically underweights them.
• Strategic bets: Entering a new market or building toward a multi-year vision requires a different frame than optimizing existing metrics. RICE has no mechanism for encoding strategic intent.
• Dependencies: RICE treats each item as independent. In practice, many features are sequentially dependent. Prioritizing item B over item A is meaningless if A must ship first for B to be possible.
• Team capacity and specialization: A high-RICE item that requires a skill set not currently available in the team should not automatically win. Capacity constraints are a real prioritization input.

2. A Layered Prioritization Model

The alternative I advocate is a three-layer model. Each layer operates at a different level of abstraction and on a different time horizon. Decisions at each layer constrain and inform the layers below.

Layer 1: Strategic Themes (Quarterly / Annual)

Before scoring individual items, leadership must establish the strategic themes that will guide the roadmap. A theme is a high-level area of investment aligned to company strategy—for example, "reduce time-to-value for new users" or "build enterprise compliance capabilities." Themes should be outcome-oriented, not feature-oriented.

Allocate capacity across themes before evaluating individual items. If 40% of engineering capacity this quarter is allocated to enterprise readiness, that allocation is a strategic decision, not a RICE output. Items outside the allocated themes should not be considered in the current cycle regardless of their RICE scores.

Layer 2: Item Scoring (Within Themes)

Within each theme, RICE (or a similar scoring model) is appropriate for comparing items of similar type and scope. At this layer, the model is operating on a level playing field—items have already been pre-selected for strategic relevance, so the comparison is genuinely apples-to-apples.

One important modification: decompose the Impact score into two sub-components—user impact (how much does this improve the experience for affected users?) and business impact (how does this move a metric that the business cares about?). Conflating the two leads to scores that obscure rather than illuminate.

Layer 3: Feasibility and Sequencing Checks

After scoring, apply two filters before finalizing the roadmap:

• Dependency sequencing: Map dependencies explicitly. Items that are blocked by unscheduled work should either trigger the scheduling of their dependencies or be deferred. Do not schedule a dependent item without scheduling its prerequisite.
• Capacity validation: Check that the proposed roadmap is achievable given team composition, known leave, and realistic velocity. A roadmap that requires capabilities the team does not have is a wish list, not a plan.

3. Making Tradeoffs Visible

The most valuable output of any prioritization process is not the ranked list—it is the explicit record of the tradeoffs made. For every item that was deprioritized, document why. This serves three functions: it reduces the cost of recurring debates about the same items, it creates accountability for the assumptions underlying the decisions, and it provides a learning record when outcomes differ from expectations.

A simple tradeoff log with four columns—Item, Why Deprioritized, Conditions for Reconsideration, and Last Reviewed—takes thirty minutes to maintain and saves hours of re-litigation in future planning cycles.

4. Communicating Prioritization Decisions

Prioritization decisions are organizational commitments. They affect not just what gets built but what does not get built—and the people who advocated for those deprioritized items deserve a clear, respectful explanation. The framing that works best is not "your idea scored lower" but "here is the bet we are making this quarter and the reasoning behind it." Outcome-oriented framing depersonalizes the decision and invites engagement with the underlying logic rather than the score.

Conclusion

RICE is a useful instrument, but it is a scalpel being asked to do the work of a map. Effective roadmap prioritization operates at multiple levels simultaneously: strategic at the theme level, analytical at the item level, and pragmatic at the sequencing level. Teams that conflate these levels—applying a single scoring model to all decisions—tend to produce technically rigorous roadmaps that are strategically incoherent. The layered model described here is an attempt to provide structure at each level without sacrificing the flexibility required to make sound decisions under genuine uncertainty.