RICE Score Batch Prioritization Matrix
Compare multiple product initiatives side by side in a RICE matrix with impact-effort quadrant visualization for roadmap planning.
Formula
RICE Score = (Reach × Impact × Confidence%) / Effort
RICE score multiplies Reach (users affected per quarter), Impact (0.25-3 value scale per user), and Confidence (0-100% certainty), then divides by Effort (person-months to complete). This normalizes value across initiatives. Example: Feature A reaches 10,000 users, impact 2, 80% confidence, 5 months effort. RICE = (10,000 × 2 × 0.8) / 5 = 3,200. Feature B reaches 1,000 users, impact 3, 100% confidence, 1 month effort. RICE = (1,000 × 3 × 1.0) / 1 = 3,000. Despite B's higher per-user impact, A wins due to 10× reach. The formula works because it captures value-per-effort: initiatives generating most value for least cost score highest. Confidence factor prevents optimism—speculative high-impact idea with 30% confidence gets penalized: (10,000 × 3 × 0.3) / 10 = 900 vs. validated lower-impact (10,000 × 1.5 × 0.9) / 5 = 2,700. RICE favors proven, efficient bets over speculative, expensive ones.
Worked Examples
Example 1: Product Roadmap Prioritization
Problem:4 initiatives: Mobile redesign (5K reach, 3 impact, 80% confidence, 8 effort), Email campaign (10K reach, 2 impact, 90% confidence, 2 effort), Payment method (3K reach, 3 impact, 70% confidence, 5 effort), Performance (8K reach, 2 impact, 95% confidence, 3 effort). Prioritize.
Solution:RICE Calculation: 1. Mobile Redesign: RICE = (5,000 × 3 × 0.8) / 8 = 12,000 / 8 = 1,500 2. Email Campaign: RICE = (10,000 × 2 × 0.9) / 2 = 18,000 / 2 = 9,000 ← Highest 3. Payment Method: RICE = (3,000 × 3 × 0.7) / 5 = 6,300 / 5 = 1,260 4. Performance: RICE = (8,000 × 2 × 0.95) / 3 = 15,200 / 3 = 5,067 Ranking: 1. Email Campaign (9,000) - High priority 2. Performance (5,067) - High priority 3. Mobile Redesign (1,500) - Medium priority 4. Payment Method (1,260) - Medium priority Analysis: - Email wins: 10K reach, 90% confident, minimal effort (2 months) - Performance: Strong reach, high confidence, low effort (quick win) - Mobile: High impact (3) but expensive (8 effort), moderate confidence - Payment: Moderate all-around Recommendation: Q1: Ship Email (2 month
Result:Email Campaign (RICE 9,000) > Performance (5,067) > Mobile (1,500) > Payment (1,260) | Ship email + performance first (high ROI, low effort)
Frequently Asked Questions
What is RICE prioritization?
RICE scores initiatives by: Reach (how many people), Impact (how much per person, 0.25-3), Confidence (certainty %, 0-100%), Effort (person-months). Formula: (Reach × Impact × Confidence%) / Effort. Higher score = higher priority. Example: Feature reaches 10,000 users, 2 impact, 80% confidence, 5 effort = (10,000 × 2 × 0.8) / 5 = 3,200. Created by Intercom (2016), now standard in product management.
What do Impact values mean in RICE?
Impact is per-person effect: 3 = Massive (game-changing), 2 = High (significant), 1 = Medium, 0.5 = Low, 0.25 = Minimal. Subjective but calibrated. Examples: 3 = Feature enables new use case (Slack threads), 2 = Major improvement (50% faster load time), 1 = Nice enhancement (dark mode), 0.5 = Minor fix (typo correction). Align team on definitions—prevents score inflation (everyone claims 3). Conservative scoring is better than optimistic.
Should I use RICE for everything?
RICE works for: Product features, marketing campaigns, process improvements (measurable reach/impact). Doesn't work for: Technical debt (no reach, but enables future velocity), infrastructure (diffuse benefits), experimentation (unknown impact). Use different frameworks: ICE (Impact, Confidence, Ease) for experiments, Cost-of-Delay for time-sensitive, Value vs. Effort matrix for simple 2×2. RICE is great for customer-facing initiatives with measurable impact.
How do I handle dependencies between initiatives?
Dependencies complicate RICE. Feature B requires Feature A. Options: (1) Bundle (score as single initiative), (2) Score separately but note dependency (build A first), (3) Increase confidence on B to 0% until A is done. Don't: Score B without acknowledging A dependency (creates false priority). Example: Advanced analytics (B) requires data pipeline (A). Build pipeline (RICE 500), then analytics (RICE 800). Or bundle as 'Analytics stack' (combined effort, higher reach from full solution).
What's the difference between RICE and ICE?
ICE = Impact × Confidence / Ease. No Reach component. Use for: Experiments (reach unknown), internal tools (user count unclear). RICE includes Reach for customer-facing features. Example: Growth hack reaching 100K users (high reach) scores better in RICE. Internal tool benefiting 3 employees scores same in ICE. Choose: RICE for roadmap prioritization (reach matters), ICE for experiment prioritization (test fast, measure impact).
How often should I recalculate RICE scores?
Recalculate when: New data changes inputs (reached 50K users instead of 10K—update reach), confidence increases (user research validates), effort estimates refined (discovery reveals complexity). Frequency: Quarterly roadmap planning (re-score all), monthly for active projects (effort updated as you learn). Don't: Constantly tweak scores to justify pet projects. Do: Update based on new information objectively.
Can RICE scores be gamed?
Yes, risks: (1) Inflating impact (everyone claims 3), (2) Optimistic reach (counting unlikely users), (3) Underestimating effort (sandbagging to boost score), (4) Confidence bias (100% without evidence). Prevention: Calibration sessions (align team on examples), peer review (challenge estimates), retrospectives (compare estimated vs. actual reach/impact after shipping), independent estimates (PM + Engineering separately score, then discuss). Transparency and honesty matter more than perfect scores.