What is the RICE framework?

A prioritization method using Reach, Impact, Confidence, and Effort to compute a comparable score for backlog items and reduce bias in decisions.

How do I define Reach credibly?

Use funnel math and historical usage to estimate the number of users affected per period. Document assumptions and avoid double counting across items.

How do I score Impact consistently?

Adopt a standard scale (0.25/0.5/1/2/3) with examples of each level for your product’s metrics. Align the team on what a “1” means before scoring.

What should Confidence reflect?

Evidence quality: research depth, experiment results, user signals. Penalize speculative ideas; raise confidence as validation accrues.

How do I estimate Effort correctly?

Estimate total person‑months across engineering, design, and QA. Sanity‑check with historical velocity and similar items; include hidden work like analytics and rollout.

How do I prevent score inflation?

Use forced distributions, cap the share of high‑impact scores, require evidence for high confidence, and run sensitivity checks on Effort.

What does the RICE score mean for sequencing?

It informs order but doesn’t override dependencies, themes, or strategic bets. Use it to start conversations and reveal trade‑offs.

Should I run sensitivity analysis on RICE?

Yes. Vary Effort and Confidence to see if ranking is robust. If small changes flip order, highlight risk and consider phased delivery.

How does RICE relate to ICE or Impact/Effort?

ICE is faster but rougher; Impact/Effort is visual but coarse. Use RICE for quarterly planning when stakes are higher and inputs are knowable.

Feature Prioritization (RICE)

RICE scoring framework for feature prioritization

planningPopularintermediateRICEPrioritization Matrix800-1200 words

Customize Your Prompt

Fill in the variables to generate your personalized prompt

Features to Prioritize

Additional Context (Optional)

Preview

See how your prompt will look with the current variables

You are an experienced Product Manager using the RICE framework to prioritize these features: [Features to Prioritize]

For each feature, provide:

## RICE SCORING BREAKDOWN

### Feature Name
**Reach** (users/quarter):
- Estimated number of users impacted
- Justification for estimate
- Confidence level

**Impact** (scale: 0.25=minimal, 0.5=low, 1=medium, 2=high, 3=massive):
- Expected impact on key metrics
- User value delivered
- Strategic importance

**Confidence** (percentage):
- Problem validation confidence
- Solution confidence
- Execution confidence
- Overall percentage

**Effort** (person-months):
- Engineering effort
- Design effort
- QA effort
- Total estimate

**RICE Score**: (Reach × Impact × Confidence) / Effort

## PRIORITIZED RANKING
List all features ranked by RICE score with:
1. Feature name - Score: [X]
2. Key insights about priority
3. Dependencies or constraints
4. Recommended sequencing

## STRATEGIC RECOMMENDATIONS
- Top 3 features to build now
- Features to defer or descope
- Resource allocation suggestions
- Risk mitigation strategies

## SENSITIVITY ANALYSIS
- **Effort Variance**: What if effort estimates are ±50% off?
  - Show how rankings change with optimistic/pessimistic effort
  - Identify which items are stable vs volatile in ranking
- **Confidence Calibration**: 
  - Only 20% of items should score 8+ on any single dimension
  - Flag if scoring appears inflated (too many high scores)
- **Monte Carlo Simulation**: Run scenarios with:
  - Best case: High confidence, low effort
  - Expected case: Current estimates
  - Worst case: Low confidence, high effort
- **Dependencies Impact**: How do item dependencies affect priority?

## SCORING CONSTRAINTS
- **Forced Distribution**: Maximum 20% of items can score 8-10 on Impact
- **Evidence Requirement**: Confidence >7 requires supporting data/research
- **Effort Reality Check**: Compare to historical velocity data

Provide specific numbers and clear justification for each score. Include confidence level for each assessment.

## Important Guidelines

### Confidence Scoring
For all assessments and recommendations, provide confidence levels:
- **High Confidence (>80%)**: Based on clear data, established patterns, or widely accepted best practices
- **Medium Confidence (50-80%)**: Based on reasonable assumptions, limited data, or emerging trends
- **Low Confidence (<50%)**: Based on speculation, very limited information, or untested hypotheses

### Accuracy Requirements
- Mark assumptions with **[ASSUMPTION]**
- Mark estimates with **[ESTIMATE: methodology used]**
- Mark uncertainties with **[UNCERTAIN: reason]**
- Never invent company names, statistics, or case studies
- When data is unavailable, explicitly state what information would improve the analysis
- Distinguish between facts, inferences, and recommendations

### Source Attribution
- General knowledge: "Based on industry standards..."
- Inferences: "This suggests that..."
- Speculation: "One possibility is..."
- Best practices: "Common approaches include..."

What Is RICE?

A pragmatic way to stack‑rank work using four inputs: Reach, Impact, Confidence, and Effort. It forces trade‑offs and reduces politics—when used honestly.

How to Calculate (Without Gaming It)

• Reach: users/period you can actually touch. Base on funnel math, not wishes.
• Impact: use a standard scale (0.25, 0.5, 1, 2, 3). Define what a “1” looks like in your context.
• Confidence: penalize hand‑wavy ideas. Evidence raises confidence; opinions don't.
• Effort: estimate in person‑months for the whole team (eng/design/QA). Sanity check vs velocity.
• Score = (Reach × Impact × Confidence) ÷ Effort. Then run a quick sensitivity check.

What the Score Means

Stack ranking guides sequencing—not guarantees. Respect dependencies and themes.

Sensitivity shows fragile ranks. If small effort changes flip order, discuss risk buffers.

Communication improves: stakeholders can debate inputs instead of opinions.

How to Use This Prompt