RICE Scoring with Context and Stakeholder Talking Points
Prioritize features using RICE framework with detailed logic and stakeholder communication templates.
v3
Last updated: November 6, 2025
product
Product Manager
rice
prioritization
Loading...
Prioritize features using RICE framework with detailed logic and stakeholder communication templates.
# RICE Scoring with Context and Stakeholder Talking Points Act as a Product Manager prioritizing features using RICE scoring with stakeholder communication. ## RICE Framework **RICE Score = (Reach × Impact × Confidence) / Effort** ## Context - **Current User Base**: [Size and characteristics] - **Quarter Objectives**: [2-3 main goals] - **Engineering Capacity**: [Team size, velocity] - **Market Pressures**: [Competitive threats, opportunities] ## Features to Evaluate [List 5-8 features with brief descriptions] ## For Each Feature ### [Feature Name] **1. Reach Score (1-10)** - How many users will this affect? - User impact calculation: [Current users × % affected] - **Score**: [X] - [Reasoning] **2. Impact Score (0.25-3)** - 3.0 = Massive impact (game-changing) - 2.0 = High impact (significant improvement) - 1.0 = Medium impact (meaningful) - 0.5 = Low impact (nice to have) - 0.25 = Minimal impact - **Score**: [X.X] - [Reasoning] - **Business Metrics Connection**: [How this impacts revenue/retention/growth] **3. Confidence Score (50-100%)** - **100%**: High confidence (we have data) - **80%**: Medium-high (good estimates) - **50%**: Low confidence (guesses) - **Score**: [XX%] - [Reasoning] - **Uncertainty Factors**: [What we don't know] **4. Effort Score (person-months, 1-10)** - Development: [X person-months] - Testing: [X person-months] - Design: [X person-months] - Documentation: [X person-months] - **Total**: [X person-months] - **Score**: [X] - [Complexity breakdown] **RICE Score**: [X.XX] = ([Reach] × [Impact] × [Confidence]) / [Effort] **Rank**: [X of Y] ## Stakeholder Talking Points **For [Feature Name]**: **Why This Matters**: - [Business rationale] - [User value] - [Strategic alignment] **What We're Optimizing For**: - [Primary goal] - [Secondary goal] **Trade-offs We're Making**: - [What we're choosing] - [What we're not choosing] - [Why] **Alternative Approaches Considered**: - [Option 1]: [Why not chosen] - [Option 2]: [Why not chosen] **Timeline & Dependencies**: - [Expected duration] - [Resource needs] - [Blockers] ## Quarterly Roadmap Allocation **Top Priority (Must Do)**: 1. [Feature] - RICE: [X.XX] 2. [Feature] - RICE: [X.XX] 3. [Feature] - RICE: [X.XX] **High Priority (Should Do)**: 4. [Feature] - RICE: [X.XX] 5. [Feature] - RICE: [X.XX] **If Time Permits**: 6. [Feature] - RICE: [X.XX] **Explanations**: - [Why top 3 are must-do] - [Trade-offs between top features] - [Opportunity cost considerations]
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...
Apply what you learned with these prompts and patterns
Acts as a critical Red Team consultant to pressure-test your product strategy, identify hidden assumptions, uncover potential weaknesses, and validate market fit before presenting to executives or committing resources.
Assess and prioritize technical debt in your codebase
Evaluate architecture decisions and verify your analysis for completeness