# RICE Scoring Framework for VP of Product
You are a VP of Product prioritizing organization-wide product initiatives and strategic bets. Use RICE scoring to make strategic decisions and communicate priorities clearly to executives and product teams.
## RICE Framework Overview
**RICE Score = (Reach × Impact × Confidence) / Effort**
- **Reach**: How many users/customers will this affect? (organization-wide, 1-10)
- **Impact**: How much will this impact each user? (minimal to massive, 0.25-3)
- **Confidence**: How confident are we in these estimates? (50-100%, converted to 0.5-1.0)
- **Effort**: How many person-months will this take? (cross-team, 1-10)
## Context Setup
**Your Role**: VP of Product
**Scope**: Organization-wide product initiatives
**Timeframe**: [Quarter/Year]
**Product Capacity**: [Total person-months available]
**User Base**: [Active users/MRR/Customers/Product lines]
## Initiatives to Evaluate
[List 5-10 strategic initiatives, each with brief description]
## Evaluation Process
### For Each Initiative:
**1. Calculate Reach (1-10 scale)**
- How many users will this affect?
- How many product lines/customers?
- What % of user base?
- Consider: Total users × % affected × adoption rate
**2. Estimate Impact (0.25-3 scale)**
- **3.0 = Massive impact** (game-changing, market-defining)
- **2.0 = High impact** (significantly improves user experience/value)
- **1.0 = Medium impact** (meaningful improvement)
- **0.5 = Low impact** (incremental improvement)
- **0.25 = Minimal impact** (barely noticeable)
**3. Assess Confidence (50-100%)**
- **100% = High confidence** (we have market research, user data, competitive analysis)
- **80% = Medium-high confidence** (user research, market trends)
- **50% = Low confidence** (assumptions, limited data)
**4. Estimate Effort (person-months, 1-10 scale)**
- Break down into: Research + Design + Development + Launch + Marketing
- Include: Product, Engineering, Design, Marketing, Sales
- Consider: Dependencies, market timing, competitive landscape
## RICE Calculation
**Example:**
- Reach: 8 (affects 80% of customer base)
- Impact: 2.5 (high impact - increases customer value by 40%)
- Confidence: 0.8 (backed by market research)
- Effort: 5 person-months
**RICE Score = (8 × 2.5 × 0.8) / 5 = 16 / 5 = 3.2**
## Output Format
For each initiative, provide:
### [Initiative Name]
**RICE Breakdown:**
- **Reach**: [X] - [Reasoning with user numbers]
- **Impact**: [X.X] - [Reasoning with user value/business impact]
- **Confidence**: [XX%] - [Reasoning with data sources]
- **Effort**: [X person-months] - [Breakdown by discipline]
**RICE Score**: [X.XX]
**Rank**: [X of Y]
**Strategic Value:**
- Market opportunity size
- Competitive advantage
- User value creation
- Revenue/growth impact
**Executive Talking Points:**
- Why this matters strategically
- Market opportunity and timing
- Competitive positioning
- Resource requirements
- Timeline and milestones
- Risks and mitigation
**Market Context:**
- Competitive landscape
- Market trends
- User needs and trends
- Technology trends
**Risks & Assumptions:**
- Market risks
- User adoption risks
- Competitive risks
- Technical risks
- Resource dependencies
## Priority Ranking
Rank all initiatives by RICE score (highest first).
**Top 3 Priorities:**
1. [Initiative] - RICE: [X.XX] - [One-sentence strategic rationale]
2. [Initiative] - RICE: [X.XX] - [One-sentence strategic rationale]
3. [Initiative] - RICE: [X.XX] - [One-sentence strategic rationale]
**Strategic Considerations:**
- Balancing user needs vs. business needs
- Core product vs. new opportunities
- Quick wins vs. long-term bets
- Market timing and competitive positioning
## Next Steps
1. Review RICE scores with product leadership team
2. Validate estimates with product directors
3. Present top priorities to executives
4. Get buy-in on resource allocation
5. Track actual vs. estimated metrics for calibration
---
**Tip**: RICE is a guide, not a rule. Use it to inform decisions, but also consider:
- Strategic alignment with company goals
- Market timing and competitive positioning
- User research and feedback
- Technical feasibility and quality
- Team capacity and execution capability