Using Prioritization Methods (RICE, ICE, MoSCoW, I/E)

How to get there: Click Prioritize in the sidebar → Score-Based Prioritization to use RICE, ICE, MoSCoW, or I/E scoring.

Learn how to use structured prioritization frameworks in ProductLift to make data-driven decisions about which features to build next, combining quantitative scoring with strategic alignment.

What is Feature Prioritization?

Feature prioritization is the process of systematically evaluating and ranking feature requests to determine which should be built first. Rather than relying on gut feeling or whoever shouts loudest, prioritization frameworks provide objective, repeatable criteria for making product decisions.

ProductLift supports multiple industry-standard prioritization frameworks, allowing you to score features based on impact, effort, reach, and strategic fit.

Why Use Prioritization Frameworks?

Benefits of structured prioritization:

  • Objective decision-making: Reduce bias and politics in feature selection
  • Team alignment: Shared criteria everyone understands
  • Transparent communication: Explain decisions to stakeholders with data
  • Efficient resource allocation: Focus effort on highest-impact work
  • Reduced regret: Make decisions based on evidence, not hunches

When to prioritize:

  • Quarterly or annual roadmap planning
  • Sprint planning for upcoming development cycles
  • When backlog grows too large to manage
  • When stakeholders disagree on priorities
  • After collecting significant customer feedback

Accessing Prioritization Tools

Step 1: Access Prioritization

  • Navigate to your Feedback Board or Wishlist board
  • Click "Prioritization" or "Score-Based Prioritization" button
  • Prioritization interface opens

[Screenshot: Feedback board with "Prioritization" button highlighted in toolbar]

Step 2: Select Posts to Prioritize

  • By default, shows posts with wishlist/backlog statuses
  • Click "Select Statuses" to customize which posts appear
  • Choose statuses: "Under Review", "Planned", etc.
  • Posts with selected statuses load into prioritization view

[Screenshot: Status selector showing checkboxes for Under Review, Planned, Considering statuses]

Step 3: Choose Prioritization Framework

  • Framework dropdown at top
  • Select: RICE, ICE, Impact/Effort, or MoSCoW
  • Interface adapts to show relevant input fields

[Screenshot: Prioritization view with framework dropdown showing RICE, ICE, Impact/Effort, MoSCoW options]

RICE Prioritization Framework

What is RICE?

RICE stands for Reach × Impact × Confidence / Effort

Developed by Intercom, RICE helps you prioritize features by estimating their potential impact relative to the effort required.

RICE Formula:

RICE Score = (Reach × Impact × Confidence) / Effort

Higher scores = higher priority features.

RICE Scoring Criteria

Reach: How many customers will this affect?

Estimate the number of users/customers who will use this feature per quarter.

Examples:

  • All users (1000+): Score 10
  • Most users (500-1000): Score 8
  • Many users (100-500): Score 5
  • Some users (50-100): Score 3
  • Few users (<50): Score 1

Alternative: Use percentage of user base

  • 80-100%: Score 10
  • 60-80%: Score 8
  • 40-60%: Score 6
  • 20-40%: Score 4
  • <20%: Score 2

Impact: How much will this improve their experience?

Rate the impact for each user who encounters it.

Impact Scale:

  • 3 = Massive impact: Solves critical pain point, drives conversions, significant value
  • 2 = High impact: Major improvement, removes friction, valuable
  • 1 = Medium impact: Notable improvement, nice to have
  • 0.5 = Low impact: Minor improvement, small convenience
  • 0.25 = Minimal impact: Barely noticeable improvement

Examples:

  • SSO for enterprise (prevents churn): 3
  • Dark mode (improves daily experience): 2
  • Export to Excel (useful but not essential): 1
  • Custom theme colors (nice cosmetic touch): 0.5
  • Adjust button padding (barely noticeable): 0.25

Confidence: How sure are you about reach and impact?

Acknowledge uncertainty in your estimates.

Confidence Scale:

  • 100% = High confidence: Strong data, validated assumptions, clear evidence
  • 80% = Medium confidence: Some data, reasonable assumptions
  • 50% = Low confidence: Guessing, limited data, many assumptions

Examples:

  • Feature requested by 50 customers with MRR data: 100%
  • Feature mentioned in user research: 80%
  • Hypothesis based on analytics: 50%
  • Complete guess with no data: 50% (or lower)

Pro tip: If confidence is below 50%, do more research before committing to build.

Effort: How much work will this take?

Estimate in person-months (or person-weeks).

Effort Examples:

  • Simple UI change: 0.5 (2 weeks)
  • New feature with backend + frontend: 3 (3 months)
  • Complex integration: 6 (6 months)
  • Platform overhaul: 12 (1 year)

Alternative: Use t-shirt sizes then convert

  • XS: 0.5 person-months
  • S: 1 person-month
  • M: 3 person-months
  • L: 6 person-months
  • XL: 12+ person-months

RICE Scoring Example

Feature: Dark Mode

  • Reach: 80% of users = 8
  • Impact: Significant daily experience improvement = 2
  • Confidence: Requested by many, clear demand = 90% = 0.9
  • Effort: UI overhaul, CSS variables = 2 person-months

RICE Score = (8 × 2 × 0.9) / 2 = 14.4 / 2 = 7.2

Feature: Advanced Reporting

  • Reach: 20% of users (power users) = 2
  • Impact: Massive impact for those who use it = 3
  • Confidence: Requested by enterprise customers = 100% = 1.0
  • Effort: Complex backend, charts, exports = 8 person-months

RICE Score = (2 × 3 × 1.0) / 8 = 6 / 8 = 0.75

Decision: Dark Mode (7.2) scores higher than Advanced Reporting (0.75) despite lower individual impact, because it affects more users with less effort.

[Screenshot: RICE scoring interface showing Dark Mode with inputs: Reach=8, Impact=2, Confidence=0.9, Effort=2, calculated score=7.2]

When to Use RICE

Best for:

  • Large backlogs requiring quantitative comparison
  • B2C or B2B products with diverse user base
  • Teams that value data-driven decisions
  • Balancing quick wins vs. major projects

Not ideal for:

  • Very early-stage products (limited data)
  • Features that are strategic must-haves (score doesn't matter)
  • Maintenance/technical debt (hard to quantify reach/impact)

ICE Prioritization Framework

What is ICE?

ICE stands for Impact × Confidence × Ease

Simpler than RICE, ICE is faster to calculate while still providing structured scoring.

ICE Formula:

ICE Score = (Impact + Confidence + Ease) / 3

Or simply: Average of three scores.

ICE Scoring Criteria

Impact: How much will this move the needle?

Rate on 1-10 scale.

  • 10: Transformational, game-changing
  • 8: Very high impact
  • 6: Meaningful impact
  • 4: Moderate impact
  • 2: Minor impact
  • 1: Negligible impact

Confidence: How sure are you this will work?

Rate on 1-10 scale.

  • 10: Extremely confident, proven concept
  • 8: High confidence, good data
  • 6: Moderate confidence, some data
  • 4: Low confidence, mostly assumptions
  • 2: Very uncertain, pure hypothesis
  • 1: Complete guess

Ease: How easy is this to implement?

Rate on 1-10 scale.

  • 10: Trivial, hours of work
  • 8: Very easy, days of work
  • 6: Moderate, 1-2 weeks
  • 4: Challenging, 1 month
  • 2: Difficult, 2-3 months
  • 1: Extremely hard, 6+ months

Note: Ease is inverse of Effort (high ease = low effort).

ICE Scoring Example

Feature: Dark Mode

  • Impact: 8 (significant user experience improvement)
  • Confidence: 9 (highly requested, clear demand)
  • Ease: 5 (moderate effort, CSS overhaul)

ICE Score = (8 + 9 + 5) / 3 = 22 / 3 = 7.3

Feature: Slack Integration

  • Impact: 7 (useful but not transformational)
  • Confidence: 8 (requested by customers)
  • Ease: 6 (moderate, API integration)

ICE Score = (7 + 8 + 6) / 3 = 21 / 3 = 7.0

Decision: Dark Mode (7.3) slightly edges out Slack Integration (7.0).

[Screenshot: ICE scoring interface showing two features side-by-side with impact, confidence, ease sliders and calculated scores]

When to Use ICE

Best for:

  • Quick prioritization sessions
  • Startup environments (fast decisions needed)
  • Growth experiments and A/B tests
  • Marketing campaigns or tactical initiatives

Not ideal for:

  • Large enterprise decisions requiring detailed analysis
  • Long-term strategic features (need more nuance than 3 factors)

Impact/Effort Matrix

What is Impact/Effort Matrix?

Visual prioritization approach that plots features on 2D grid:

  • X-axis: Effort (Low to High)
  • Y-axis: Impact (Low to High)

Creates four quadrants that guide prioritization.

The Four Quadrants

         High Impact
            |
   Quick   |  Major
   Wins    |  Projects
-----------|----------
   Fill-   |  Money
   Ins     |  Pits
            |
         Low Impact
     Low       High
        Effort

Quadrant 1: Quick Wins (High Impact, Low Effort)

  • Priority: Build these first
  • Examples: UI improvements, small feature additions, bug fixes with big impact
  • Strategy: Ship fast, get quick value

Quadrant 2: Major Projects (High Impact, High Effort)

  • Priority: Plan carefully, schedule for roadmap
  • Examples: Platform features, integrations, architectural changes
  • Strategy: Worth the investment, but need resources and planning

Quadrant 3: Fill-Ins (Low Impact, Low Effort)

  • Priority: Build when you have spare capacity
  • Examples: Minor tweaks, polish, nice-to-haves
  • Strategy: Low risk, low reward - fit in around major work

Quadrant 4: Money Pits (Low Impact, High Effort)

  • Priority: Avoid or deprioritize
  • Examples: Over-engineered solutions, edge cases, vanity features
  • Strategy: Say no unless strategic reasons override impact/effort analysis

[Screenshot: Impact/Effort matrix visualization with features plotted as circles, color-coded by quadrant]

Using Impact/Effort Matrix in ProductLift

Create Matrix View:

  1. Navigate to Prioritization → Impact/Effort
  2. See grid with quadrants
  3. Drag posts to position on matrix
  4. Impact (Y-axis) and Effort (X-axis) automatically scored based on position

Or Use Sliders:

  1. For each post, set Impact (1-10) and Effort (1-10)
  2. ProductLift plots automatically on matrix
  3. Color-coded by quadrant

Bulk Positioning:

  • Select multiple posts
  • Drag together to quadrant
  • Quick categorization for backlog grooming

[Screenshot: Matrix interface with drag-and-drop positioning, posts clustered in Quick Wins quadrant]

When to Use Impact/Effort Matrix

Best for:

  • Visual learners and teams
  • Executive presentations (easy to understand)
  • Backlog grooming and triage
  • Identifying quick wins vs. long-term investments

Not ideal for:

  • Precise scoring (less granular than RICE/ICE)
  • Features that don't fit binary high/low classifications

MoSCoW Prioritization

What is MoSCoW?

MoSCoW is a simple categorization method:

  • Must have
  • Should have
  • Could have
  • Won't have (this time)

No scoring - just bucket features into categories.

MoSCoW Categories

Must Have:

  • Critical features required for launch or success
  • Without these, product fails or release doesn't happen
  • Non-negotiable

Examples:

  • User authentication (can't launch without it)
  • Core functionality (reason product exists)
  • Legal/compliance requirements

Should Have:

  • Important but not critical
  • Significant impact, but workarounds exist
  • High priority but can be deferred if needed

Examples:

  • Password reset flow (important, but support can manually reset)
  • Email notifications (valuable, but not blocking)
  • Search functionality (important, but can browse/filter)

Could Have:

  • Nice to have if time permits
  • Desirable but low impact if missing
  • "Cherry on top" features

Examples:

  • Dark mode
  • Custom themes
  • Advanced filters

Won't Have (This Time):

  • Out of scope for current release/quarter
  • May be reconsidered later
  • Explicitly deprioritized

Examples:

  • Features that don't align with strategy
  • Low-impact requests
  • Future-phase enhancements

[Screenshot: MoSCoW view showing four columns with posts categorized: Must Have (5), Should Have (12), Could Have (23), Won't Have (47)]

Using MoSCoW in ProductLift

Categorize Posts:

  1. Navigate to Prioritization → MoSCoW
  2. Drag posts into categories
  3. Or use dropdown to assign category
  4. Focus on "Must Have" and "Should Have" for roadmap

Timeboxing:

  • Set deadline (e.g., Q2 Launch)
  • Must Have = required by deadline
  • Should Have = nice to have by deadline
  • Could Have = if we have extra time
  • Won't Have = explicitly post-deadline

When to Use MoSCoW

Best for:

  • Release planning (what's in vs. out of scope)
  • Time-constrained projects
  • Simple triage of large backlogs
  • Teams new to prioritization (easy to understand)

Not ideal for:

  • Ranking within categories (everything is "Must Have")
  • Quantitative analysis
  • Comparing features across categories

Combining Frameworks

Multi-Framework Approach

Use different frameworks for different purposes:

Step 1: MoSCoW for Initial Triage

  • Quickly categorize 100+ posts
  • Eliminate "Won't Have" from consideration
  • Focus on Must/Should/Could

Step 2: RICE for Must Have + Should Have

  • Score remaining ~30 posts with RICE
  • Get precise ranking
  • Identify top 10 priorities

Step 3: Impact/Effort Matrix for Communication

  • Plot top 10 on matrix
  • Use for stakeholder presentation
  • Visual storytelling

Weighting with Customer Value (MRR)

Enhance RICE with Revenue Impact:

Weighted RICE = (Reach × Impact × Confidence × MRR Weight) / Effort

MRR Weight Calculation:

MRR Weight = Total Voter MRR / Average MRR per Voter

Example:

Feature A:

  • Standard RICE: 6.0
  • Voted by 10 users, $50k total MRR = $5k avg MRR
  • Company avg MRR: $1k
  • MRR Weight: $5k / $1k = 5x
  • Weighted RICE: 6.0 × 5 = 30.0

Feature B:

  • Standard RICE: 8.0
  • Voted by 50 users, $25k total MRR = $500 avg MRR
  • MRR Weight: $500 / $1k = 0.5x
  • Weighted RICE: 8.0 × 0.5 = 4.0

Decision: Feature A (30.0) prioritized over Feature B (4.0) despite lower base RICE, because high-value customers need it.

[Screenshot: Prioritization table showing Base RICE, MRR Weight, and Weighted RICE columns for comparison]

Exporting Prioritization Data

Export Scored Features

Export to Spreadsheet:

  1. After scoring posts with chosen framework
  2. Click "Export" button
  3. Choose format: CSV or Excel
  4. Download includes:
    • Post title, description, status
    • All scores (Reach, Impact, Confidence, Effort)
    • Calculated RICE/ICE score
    • Votes, comments, MRR data
    • Category, tags

[Screenshot: Export dialog showing format options and preview of exported columns]

Use Cases for Export:

  • Present to executives in familiar Excel format
  • Further analysis in BI tools
  • Archive prioritization decisions
  • Share with stakeholders without ProductLift access

Saving Prioritization Sessions

Save Current Scoring:

  • Scores saved automatically with each post
  • Return to prioritization view anytime
  • Historical scores preserved
  • Track how priorities change over time

Version History:

  • See when scores were last updated
  • Compare quarterly prioritization changes
  • Understand priority drift

Best Practices for Prioritization

Before Prioritizing

1. Define Scope:

  • What are you prioritizing for? (Q3 roadmap? This sprint? Annual plan?)
  • Timeframe matters (effort estimates change with horizon)

2. Gather Data:

  • Collect votes and feedback
  • Sync customer MRR data (Stripe integration)
  • Review analytics
  • Consult with sales, support, engineering

3. Involve Stakeholders:

  • Product, engineering, design
  • Sales, customer success
  • Leadership (for strategic input)

During Prioritization

1. Be Consistent:

  • Use same criteria for all features
  • Same person/team scores similar features
  • Define clear rubrics (what does Impact=8 mean?)

2. Calibrate Scores:

  • Score a few features together as team
  • Align on what each score means
  • Adjust outliers

3. Challenge Assumptions:

  • Question high-confidence scores (are we sure?)
  • Debate low-impact/high-effort features (do we really need this?)

After Prioritizing

1. Review Results:

  • Do top priorities make sense?
  • Any surprising results?
  • Strategic features ranked too low?

2. Apply Human Judgment:

  • Frameworks inform, don't dictate
  • Strategic must-haves may override scores
  • Technical debt may be required despite low RICE

3. Communicate Decisions:

  • Share prioritization with team
  • Explain top priorities to stakeholders
  • Update feedback posts with reasoning

4. Track Outcomes:

  • After building high-RICE features, did they have expected impact?
  • Were effort estimates accurate?
  • Improve scoring over time

Common Pitfalls and Solutions

Pitfall: Everything is "High Priority"

Solution:

  • Force ranking (only top 5 can be "Must Have")
  • Use relative comparison ("Is this more important than X?")
  • Apply strict effort/resource constraints

Pitfall: Ignoring Effort

Solution:

  • Always balance impact with effort
  • Quick wins are real wins
  • Long-term projects need strong justification

Pitfall: Gaming the System

Solution:

  • Collaborative scoring (not one person)
  • Challenge inflated scores
  • Use data to validate assumptions (votes, MRR, research)

Pitfall: Analysis Paralysis

Solution:

  • Set time limit for prioritization session
  • "Done is better than perfect" - approximate scores are fine
  • Prioritize the prioritization (don't score 500 posts with RICE)

Pitfall: Deprioritizing Technical Debt

Solution:

  • Include tech debt in prioritization
  • Estimate "impact" as prevention of future problems
  • Reserve capacity for unglamorous but necessary work

Use Case Workflows:

Prioritization Tools:

Roadmap Management: