Engineering Leadership · Chapter 7 of 8
Budget, headcount and making the case
Where engineering leadership is decided, and the language most engineers never learn.
Above EM, a growing share of the job is arguing for resources with people who do not think in engineering terms. Leaders who cannot do this get smaller teams regardless of how well they deliver.
Translating engineering into the language of the decision
| What you want to say | What actually lands |
|---|---|
| We need to reduce technical debt | This is costing us N engineer-weeks a quarter, here is the measurement |
| We need more headcount | Here is the work we will not do without it, and what that costs |
| The platform team is valuable | Without it this work happens 40 times instead of once, badly |
| We need to improve reliability | Last quarter's incidents cost X in engineering time and Y in customer impact |
| This migration is important | Here is the run-rate saving and the date it starts, and the risk if we do not |
Two habits that make the case credible
- Volunteer the weakness in your own number. ‘This assumes recovered time converts to output, which it does not do one-for-one — so treat it as a range’. A finance audience trusts a caveated number far more than a clean one, because they know clean ones are constructed.
- Frame the alternative honestly. The work does not disappear if it is not funded; it gets done worse, elsewhere, and shows up as slower delivery rather than as a line item. The question is not whether to pay, but whether to pay once or many times.
Cloud and vendor cost, which is now yours
Cost and budget language appears in roughly 40% of the leadership and delivery postings behind this site. You will be expected to have a position on cloud spend per unit of business value, on build versus buy, and on which vendor relationships are strategic. Being unable to discuss the infrastructure bill is a visible gap at director level and above.