Feature Prioritization Matrix

RICE is a prioritization framework developed by Intercom to help product teams make objective decisions about what to build next. Instead of relying on gut feelings or the loudest voice in the room, RICE provides a quantifiable way to compare features, bugs, and initiatives.

The framework scores each item across four dimensions: Reach (how many users will be affected), Impact (how much will it improve their experience), Confidence (how certain are we about these estimates), and Effort (how much work will it take).

The formula is simple: (Reach × Impact × Confidence) / Effort. Higher scores indicate better candidates for your roadmap. The beauty is in forcing explicit tradeoffs - a feature might have massive impact but require so much effort that simpler wins should come first.

Every PM faces the same challenge: too many ideas, not enough engineering time. Without a framework, prioritization becomes political - whoever argues loudest or has the most senior stakeholder backing wins, regardless of actual impact.

RICE creates a common language for prioritization discussions. When a sales leader pushes for their favorite feature, you can show the math: “This scores 24, while these three quick wins score 40+ each. Let's revisit after we ship those.”

It also surfaces hidden gems. Features that seem boring often score surprisingly high when you calculate the reach. Fixing that one annoying bug affecting 80% of users might beat the shiny new feature that only 5% will ever use.

Reach: Estimate the number of users who will interact with this feature per time period (typically per quarter). Use real data when possible - check analytics for page views, feature usage, or support ticket volume. Express it as an absolute number, not a percentage.

Impact: Score on a scale from 0.25 (minimal) to 3 (massive). Be conservative - most features are a 1 (medium) or 0.5 (low). Reserve 3 for game-changers that will fundamentally improve the user experience. When in doubt, go lower.

Confidence: This is your honesty check. Score 100% only if you have real data backing your estimates. 80% if you have some evidence, 50% if it's educated guessing, and lower if you're just speculating. Low confidence items need validation before building.

Effort: Estimate in person-weeks or person-months. Include design, development, QA, and deployment time. Ask engineers for estimates rather than guessing. Use historical data from similar features when available.

RICE vs ICE: ICE (Impact, Confidence, Ease) is simpler but doesn't account for reach. RICE is better for products with diverse user bases where different features affect different segments.

RICE vs MoSCoW: MoSCoW (Must have, Should have, Could have, Won't have) is more qualitative and often leads to everything being labeled “Must have.” RICE forces actual tradeoffs through numerical scoring.

RICE vs Value/Effort Matrix: The 2x2 matrix is great for visualization but RICE provides more granular scores. Use the matrix for communication with stakeholders, RICE for actual prioritization decisions.