Feature Prioritization Framework (RICE)

Build a complete RICE prioritization analysis for my SaaS product backlog:

Product Name: [PRODUCT NAME]
Product Category: [B2B/B2C/B2B2C]
Total Active Users: [USER COUNT]
Current Backlog Size: [NUMBER OF FEATURES TO PRIORITIZE]
Planning Period: [QUARTER/HALF/YEAR]
Primary Business Goal: [GROWTH/RETENTION/MONETIZATION/EFFICIENCY]
Engineering Capacity: [DEVELOPER WEEKS AVAILABLE]
Features to Score: [LIST 5-10 FEATURES WITH BRIEF DESCRIPTIONS]

Develop the RICE framework across these six sections:

Section 1 - RICE Methodology Setup and Calibration:
Explain the RICE scoring framework in detail covering how Reach, Impact, Confidence, and Effort combine to produce a prioritization score. Define the specific formula where RICE Score equals Reach multiplied by Impact multiplied by Confidence divided by Effort. Establish the measurement units for each component tailored to the SaaS context. Reach should be measured as the number of users or accounts affected per quarter. Impact should use a standardized scale where 3 equals massive impact, 2 equals high, 1 equals medium, 0.5 equals low, and 0.25 equals minimal. Confidence should be expressed as a percentage where 100 percent means high confidence based on quantitative data, 80 percent means medium confidence based on qualitative signals, and 50 percent means low confidence based on intuition alone. Effort should be measured in person-weeks of engineering work. Walk through a calibration exercise using a previously shipped feature that everyone agrees was successful to anchor the scoring scales and build shared understanding across the team.

Section 2 - Reach Estimation and Data Collection:
Develop a systematic approach for estimating the reach of each proposed feature. Define reach as the number of unique users or accounts that will interact with or benefit from the feature within a defined time period. Create a data collection framework that pulls from product analytics showing current feature usage patterns, customer support tickets requesting the functionality, sales deal notes mentioning the capability gap, and survey data indicating interest levels. Establish methods for estimating reach when direct data is unavailable, including market sizing approaches, comparable feature adoption rates from past launches, and segment-based extrapolation. Address common reach estimation mistakes including confusing total addressable users with likely adopters, ignoring activation barriers, and double-counting users across overlapping features. Create a reach estimation template that documents the data sources, assumptions, and confidence level for each feature's reach score. Show how to segment reach by customer tier to weight enterprise accounts differently from self-serve accounts when appropriate.

Section 3 - Impact Assessment and Scoring:
Build a rigorous impact scoring methodology that goes beyond subjective opinion. Define impact as the expected effect on the primary business goal when a user engages with the feature. Create impact rubrics specific to each business goal type. For growth-focused goals, score based on expected conversion rate improvement, viral coefficient contribution, or market expansion potential. For retention goals, score based on expected reduction in churn rate, increase in product stickiness, or improvement in NPS scores. For monetization goals, score based on expected increase in average revenue per account, upgrade conversion, or expansion revenue. For efficiency goals, score based on expected reduction in support tickets, manual work, or operational cost. Provide worked examples showing how to assign impact scores of 3, 2, 1, 0.5, and 0.25 with concrete before-and-after scenarios for each level. Address the challenge of comparing impact across fundamentally different feature types such as new capabilities versus performance improvements versus UX refinements.

Section 4 - Confidence Assessment and Evidence Levels:
Create a structured approach for assessing confidence that reduces bias and rewards evidence-based decision making. Define three confidence tiers with clear criteria. High confidence at 100 percent requires quantitative evidence such as A/B test results, usage data from related features, or direct customer commitment backed by contracts. Medium confidence at 80 percent requires qualitative evidence such as customer interview insights, competitive analysis, sales team feedback, or beta program results. Low confidence at 50 percent applies when the score relies primarily on team intuition, market assumptions, or analogy to unrelated products. Create a confidence evidence checklist for each feature that documents what data supports the reach estimate, what data supports the impact estimate, and where the biggest uncertainty lies. Develop strategies for increasing confidence before committing to development, including rapid prototyping, painted door tests, customer co-design sessions, and concierge MVP approaches. Establish a policy for how confidence affects the roadmap, such as requiring higher confidence for larger effort features and tolerating lower confidence for small experimental bets.

Section 5 - Effort Estimation and Calibration:
Build an effort estimation process that produces consistent and reasonably accurate person-week estimates. Define effort as the total work required across all disciplines including product design, engineering, quality assurance, and documentation. Create estimation guidelines that account for complexity factors including new technology adoption, third-party integration dependencies, data migration requirements, backward compatibility constraints, and security review needs. Establish estimation methods appropriate for different levels of feature definition, from rough order of magnitude for concept-stage ideas to detailed story-point-based estimates for well-scoped features. Address common estimation biases including anchoring to initial guesses, planning fallacy optimism, and failure to account for cross-team coordination overhead. Create a historical effort accuracy tracker that compares estimated versus actual effort for past features to calibrate future estimates. Develop guidelines for when to break large features into smaller independently scorable increments versus scoring them as a single unit.

Section 6 - Score Calculation, Ranking, and Decision Making:
Calculate the final RICE scores for each feature and create a ranked prioritization list. Build a presentation-ready scorecard showing each feature with its individual component scores and final RICE score in descending order. Analyze the results looking for patterns such as high-reach low-effort quick wins, high-impact features blocked by low confidence, and expensive features whose scores do not justify the investment. Create a decision framework for how to use RICE scores alongside other factors including strategic alignment, technical dependencies, team morale, and contractual obligations. Address common objections to the scoring results including executive pet projects that score poorly, customer escalations that demand immediate attention regardless of score, and infrastructure work that scores low but enables future features. Establish a cadence for re-scoring features as new data emerges, confidence levels change, or business goals shift. Build a post-launch measurement plan that compares predicted reach and impact against actual results to continuously improve scoring accuracy.