Build a RICE Feature Prioritization Matrix for Product Roadmap Decisions

Create a complete RICE scoring matrix to prioritize product features with data-driven rankings and roadmap recommendations.

πŸ“ The Prompt

Act as a senior product manager with 10+ years of experience in [INDUSTRY] SaaS products. Help me build a RICE (Reach, Impact, Confidence, Effort) prioritization matrix for [PRODUCT NAME], which serves [TARGET USER PERSONA]. Here is the list of features/initiatives I need to prioritize: [LIST 5-10 FEATURES OR INITIATIVES] For each feature, perform the following steps: Step 1 β€” Define Reach: Estimate how many users/customers this feature will affect per [TIME PERIOD, e.g., quarter]. Explain your reasoning based on current user base of [APPROXIMATE USER COUNT]. Step 2 β€” Assess Impact: Score impact on a scale of 0.25 (minimal), 0.5 (low), 1 (medium), 2 (high), 3 (massive). Justify each score by mapping to [PRIMARY BUSINESS GOAL, e.g., retention, conversion, expansion revenue]. Step 3 β€” Assign Confidence: Rate confidence as a percentage (50%, 80%, or 100%) based on available data. Specify what evidence supports or is missing for each estimate. Step 4 β€” Estimate Effort: Quantify in person-months based on a team of [TEAM SIZE AND COMPOSITION, e.g., 2 engineers, 1 designer]. Flag any dependencies or technical risks. Step 5 β€” Calculate RICE Score: Use the formula (Reach Γ— Impact Γ— Confidence) / Effort. Rank all features from highest to lowest score. Present the results in a formatted table with columns: Feature | Reach | Impact | Confidence | Effort | RICE Score | Rank. Finally, provide: - A recommended roadmap grouping (Now / Next / Later) - 3 caveats or qualitative factors that the RICE score alone may not capture - Suggestions for what additional data to collect to increase confidence scores

πŸ’‘ Tips for Better Results

Be honest about confidence levelsβ€”overestimating confidence defeats the purpose of the framework. Always pair RICE scores with qualitative judgment, as strategic initiatives like platform migrations may score low but remain critical. Revisit scores monthly as new data emerges.

🎯 Use Cases

Product managers and product teams who need a systematic, defensible method to prioritize competing feature requests for sprint or quarterly planning.

πŸ”— Related Prompts

πŸ’Ό Business intermediate

Design a Complete OKR Framework for Your Team or Organization

Build a complete OKR framework with company, team, and individual objectives, scoring systems, and a 90-day rollout plan.

πŸ’Ό Business intermediate

Write a Business Plan Executive Summary

Create a compelling executive summary for investors with market analysis, financials, and positioning.

πŸ’Ό Business intermediate

Create a Project Proposal

Generate a complete project proposal with timeline, budget, risk assessment, and success metrics.

πŸ’Ό Business advanced

Create a Compelling Investor Pitch Deck Outline

Generate a detailed investor pitch deck outline with slide-by-slide guidance, speaker notes, and visual suggestions for fundraising.

πŸ’Ό Business advanced

Design an Equity Allocation Model for Co-Founders and Early Team

Build a fair co-founder equity split using a weighted scoring model, vesting schedules, option pool strategy, and cap table scenarios.

πŸ’Ό Business beginner

SWOT Analysis Generator

Generate a detailed SWOT analysis with strategic recommendations and priority actions.