Overview
RICE is a prioritization framework that calculates a score for each task or project based on four factors: Reach, Impact, Confidence, and Effort. This quantitative approach removes emotion from prioritization and helps make objective decisions about where to spend your time.
RICE Score = (Reach × Impact × Confidence) / Effort
Higher scores = higher priority
The Four Factors
Reach (Number of People/Tasks Affected)
- How many people will this benefit?
- How often will this be used?
- Personal: How many areas of life does this impact?
Scoring: Actual number or estimate
- Learning Python: 100 (affects all future projects)
- Organizing desk: 1 (affects only you, once)
- Improving morning routine: 365 (daily impact)
Impact (Degree of Effect)
- How much will this improve things?
- What's the magnitude of benefit?
Scoring Scale:
- 3 = Massive impact
- 2 = High impact
- 1 = Medium impact
- 0.5 = Low impact
- 0.25 = Minimal impact
Confidence (How Sure Are You?)
- How certain are you about Reach and Impact estimates?
- Based on data, research, or gut feeling?
Scoring Scale:
- 100% = High confidence (strong data)
- 80% = Medium confidence (some data)
- 50% = Low confidence (assumptions)
Effort (Time/Resources Required)
- How much time will this take?
- What resources are needed?
Scoring: Person-hours, days, or weeks
- 0.5 = Half day
- 1 = One day
- 5 = One week
- 20 = One month
Example Calculations
Task A: Learn Touch Typing
- Reach: 250 (work days per year)
- Impact: 2 (high - saves time daily)
- Confidence: 80%
- Effort: 20 (hours to learn)
- Score: (250 × 2 × 0.8) / 20 = 20
Task B: Reorganize Files
- Reach: 12 (times per year you search for files)
- Impact: 0.5 (low - minor convenience)
- Confidence: 100%
- Effort: 4 (hours)
- Score: (12 × 0.5 × 1.0) / 4 = 1.5
Task C: Automate Expense Reports
- Reach: 12 (monthly reports)
- Impact: 1 (medium - saves hassle)
- Confidence: 50% (unsure if possible)
- Effort: 10 (hours to build)
- Score: (12 × 1 × 0.5) / 10 = 0.6
Priority Order: A (20) > B (1.5) > C (0.6)
Benefits
- Objective: Removes bias and emotion
- Transparent: Clear why one task beats another
- Quantitative: Easy to compare disparate tasks
- Effort-aware: Accounts for time required
- Confidence factor: Acknowledges uncertainty
When to Use
- Choosing between multiple projects
- Quarterly or annual planning
- Evaluating large task backlogs
- Justifying priorities to stakeholders
- When gut feeling isn't enough
Limitations
- Requires estimation (which can be wrong)
- Time-consuming for many tasks
- May miss strategic opportunities
- Numbers can feel arbitrary
- Best for medium-term planning, not daily tasks
Tips
- Score in batches (compare similar items)
- Revisit scores as you learn more
- Use consistent scoring criteria
- Don't over-think the numbers
- Combine with other methods for daily work
