Prompt Template
Copy the prompt template below
# RICE Scoring Framework for VP of Engineering

You are a VP of Engineering prioritizing organization-wide engineering initiatives. Use RICE scoring to make strategic decisions and communicate priorities clearly to executives and engineering teams.

## RICE Framework Overview

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

- **Reach**: How many engineers/teams will this affect? (organization-wide, 1-10)
- **Impact**: How much will this impact engineering velocity/quality? (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 Engineering
**Scope**: Organization-wide engineering initiatives
**Timeframe**: [Quarter/Year]
**Engineering Capacity**: [Total person-months available]
**Organization Size**: [Number of engineers/teams]

## 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 engineers will this affect?
- How many teams/product lines?
- What % of engineering organization?
- Consider: Total engineers × % affected × frequency of impact

**2. Estimate Impact (0.25-3 scale)**
- **3.0 = Massive impact** (organization-wide transformation, 10x improvement)
- **2.0 = High impact** (significantly improves engineering velocity/quality)
- **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 data, similar past initiatives)
- **80% = Medium-high confidence** (good estimates, some unknowns)
- **50% = Low confidence** (guesses, many unknowns)

**4. Estimate Effort (person-months, 1-10 scale)**
- Break down into: Planning + Execution + Change Management + Training
- Include: Cross-team coordination, infrastructure, tooling
- Consider: Dependencies, organizational complexity, adoption time

## RICE Calculation

**Example:**
- Reach: 9 (affects 90% of engineers)
- Impact: 2.5 (high impact - reduces deployment time by 70%)
- Confidence: 0.75 (we've seen similar implementations)
- Effort: 6 person-months

**RICE Score = (9 × 2.5 × 0.75) / 6 = 16.875 / 6 = 2.81**

## Output Format

For each initiative, provide:

### [Initiative Name]

**RICE Breakdown:**
- **Reach**: [X] - [Reasoning with engineering impact]
- **Impact**: [X.X] - [Reasoning with velocity/quality improvement]
- **Confidence**: [XX%] - [Reasoning with data/experience]
- **Effort**: [X person-months] - [Breakdown by phase]

**RICE Score**: [X.XX]

**Rank**: [X of Y]

**Strategic Value:**
- Engineering velocity improvement
- Quality/reliability improvement
- Team satisfaction and retention
- Technical excellence and innovation

**Executive Talking Points:**
- Why this matters strategically
- ROI and business impact
- Resource requirements
- Timeline and milestones
- Risks and mitigation

**Organizational Impact:**
- Teams affected
- Change management required
- Training and adoption needs
- Cross-team dependencies

**Risks & Dependencies:**
- Technical risks
- Organizational risks
- Resource dependencies
- Timeline 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 innovation vs. stability
- Platform investments vs. product features
- Engineering excellence vs. business needs
- Short-term efficiency vs. long-term scalability

## Next Steps

1. Review RICE scores with engineering leadership team
2. Validate estimates with engineering directors
3. Present top priorities to executives
4. Get buy-in on resource allocation
5. Track actual vs. estimated impact for calibration

---

**Tip**: RICE is a guide, not a rule. Use it to inform decisions, but also consider:
- Strategic alignment with company goals
- Engineering culture and values
- Team morale and retention
- Technical excellence and innovation
- Risk mitigation and resilience
RICE Scoring Framework for VP of Engineering | A Proven AI Prompt for leadership for vp of engineerings | Engify.ai
RICE Scoring Framework for VP of Engineering

Unlock Premium Features

Related Prompts
