The board asks you to prove engineering is productive. What do you present?
Short answer
Present a balanced scorecard: delivery speed and stability (DORA metrics), reliability (SLO attainment, incident impact), outcomes (features shipped against business goals and their impact), efficiency (cost per unit, cloud spend trend), and people health (attrition, engagement), with trends, benchmarks and the actions you are taking.
Detailed answer
One page with five sections and trend arrows:
| Area | Metric | Trend |
|---|---|---|
| Speed | Lead time 6 → 2 days; deploys per week 5 → 40 | Improving |
| Stability | Change failure rate 22% → 12% | Improving |
| Reliability | Checkout SLO 99.95% met 11 of 12 months | Stable |
| Outcomes | 8 of 10 roadmap commitments delivered; conversion +3.1% from checkout redesign | On track |
| Efficiency | Infra cost per order −18% YoY | Improving |
| People | Regretted attrition 6%; engagement 78% | Stable |
Add the top 3 risks and the investments addressing them.
What the interviewer expects
Outcome orientation, balanced metrics, avoidance of vanity metrics.
Common mistakes to avoid
Lines of code, story points or tickets closed as productivity measures.