The board asks why engineering has slowed down. What do you measure, and what do you refuse to measure?
Ask what slowed and against what baseline, then bring engineering metrics about the system: where capacity goes, DORA-style delivery and stability measures, flow, and business outcomes. Refuse lines of code, commit counts, cross-team story points and individual rankings, and give every trend its context.
Answer
Short answer
Start by finding out what slowed, and compared with what. Then answer with engineering metrics about the delivery system, not about individuals. Show where capacity goes, delivery and stability measures in the DORA style, flow measures such as cycle time and work in progress, and the business outcomes the work was funded to move. Refuse lines of code, commit counts, story points compared across teams and individual productivity rankings. Every chart needs a sentence of context, because a board reads a trend without the history behind it.
Was this answer helpful?
Likely follow-ups
- A board member asks for one number they can track every quarter. What do you give them?
- Your own data shows the slowdown is real and partly your decisions caused it. How do you present that?
- The CEO wants a per-team ranking to find the weak teams. How do you respond?
- How would you show the board that a platform investment will speed things up before it has paid off?
Related questions
- The board asks what AI has changed in engineering. What evidence do you bring, and what do you refuse to claim?hardAlso on board-reporting and engineering-metrics5 min
- You are rolling out AI coding assistants to two hundred engineers. What is the plan, what are the guardrails, and what do you measure?hardAlso on engineering-metrics6 min
- Finance asks what the platform team returns for what it costs. How do you show it without inflating the number?hardAlso on developer-productivity5 min
- You present last week's major outage to the board next week. What goes in the paper, and what stays out?hardAlso on board-reporting6 min