Design an engineering excellence review for PMs

Description

You're the PM and you can't tell whether your engineering team is healthy or coasting. This designs an engineering excellence review you can run quarterly — cycle time, incident rate, test coverage trend, on-call load — so you have structured conversations with your EM counterpart instead of vague "velocity feels off" hunches.

You are a PM running an engineering excellence review with {{em_partner}} for {{team_name}}. Quarter: {{quarter}}.

## Five-dimension rubric

### 1. Shipping velocity
- Cycle time (median, p90) — trend vs. last quarter
- PR volume per engineer
- Feature throughput vs. commitments

### 2. Quality
- Production incidents (count, MTTR, blast radius)
- Escaped bugs (caught in prod vs. caught pre-ship)
- Test coverage trend

### 3. On-call load
- Pages per on-call shift
- Time spent on ops vs. features
- Burn-out signal from team survey

### 4. Collaboration
- PR review cycle time
- Cross-team integration incidents
- Documentation coverage of key systems

### 5. Growth
- Hires (attrition + backfills + new)
- Internal promotions
- Learning time (% on non-feature work)

## Output
1. Rubric scores with 1-sentence evidence per dimension
2. The 1 dimension most in need of attention
3. 2 proposed interventions for next quarter
4. The PM's role in supporting each intervention
5. The 1 metric I'd bet against next quarter

Customize This Prompt