Engineering Leadership: The Roadmap You Get Back

The reclaimed engineering capacity is real. The question is what the team spends it on.

The engineering economics of externalizing calculator math produce a specific outcome: engineer-quarters that used to go into calculator maintenance become available for other work. The Two-Month Build That Became an Afternoon (/writing/two-month-build-afternoon) makes the case for the reclamation; this piece is for VPs of engineering deciding what to do with the reclaimed capacity. The question is not whether the reclamation happens; it does. The question is whether the team captures the value the reclamation offers, and if so, how.

The three ways teams spend reclaimed capacity

The first way is on features that were on the roadmap and kept slipping. Every product roadmap has features the team wanted to ship and did not because the calculator maintenance quarters kept absorbing capacity that would have gone to them. Reclaimed capacity restored to those features produces the specific ships the team was originally planning. This is the least visible use of reclaimed capacity and often the most valuable, because the team is closing a specific gap rather than starting new work.

The second way is on features that were not on the roadmap because the team did not think it had capacity for them. Reclaimed capacity that opens up a new roadmap slot produces work that would not have existed otherwise. This is the most visible use of reclaimed capacity and the one that leadership tends to celebrate, because the capacity produces new product surface the firm did not have before.

The third way is on the baseline of team velocity. Reclaimed capacity that gets absorbed into general velocity produces a team that ships everything a little faster, without any single feature carrying the label of the reclamation. This is the least attributable use of reclaimed capacity and often the healthiest, because it corresponds to a team whose engineering hours match the ambition of the roadmap, which is the state most engineering leaders are trying to reach.

The mistake most teams make with reclaimed capacity

The specific mistake is treating reclaimed capacity as a windfall to load new commitments onto rather than as a decompression from a previously overloaded state. A team whose calculator work was quietly consuming a quarter per engineer per year is a team that has been running above its capacity for years; the reclamation is what returns the team to sustainable pace, not what creates additional pace. VPs of engineering who treat the reclamation as new capacity and load new commitments to fill it produce teams that are again running at above-sustainable pace, this time with the additional commitments visible on the roadmap. The team is worse off than before the externalization, because the burden is now explicit rather than hidden.

The remedy is a deliberate posture at the start of the reclamation. Name the reclaimed capacity; do not immediately assign it. Let the team absorb the capacity into velocity for at least a quarter. Observe whether the team’s throughput on the existing roadmap improves. If it does, some of the reclaimed capacity was closing an overload; the improvement is the specific value the reclamation produced, and the remainder can be assigned to new commitments. If it does not, the team was not actually overloaded from calculator work, and the reclaimed capacity is genuinely available for new commitments.

What VPs of engineering typically discover

The likely discovery, for an engineering organization that runs this exercise honestly, is that a portion of the reclaimed capacity is overload relief and a portion is genuinely new. The ratio varies by firm; the general shape is that calculator maintenance was more expensive in hidden ways than the ledger showed. Correctness-incident triage, edge-case rediscovery, engineer-onboarding to legacy calculator code, compliance-review coordination, and the annual tax-year rollover cycle each contributed hours that were not billed to calculator maintenance in the firm’s time-tracking but were, in aggregate, calculator maintenance.

The discovery has a management implication: the ledger the finance function saw before the externalization was undercounting. This is not a criticism of the finance function; the hours in question were legitimately hard to attribute. It is a specific caution for VPs of engineering presenting the externalization case to leadership: the pre-externalization ledger looks smaller than the actual cost, and the post-externalization ledger looks smaller by more than the pre-externalization ledger predicted. The gap between the two is the hidden cost the externalization surfaces.

The opportunity-cost calculation, properly framed

The framing that works in an engineering-leadership meeting is not ‘we save X engineer-hours per year.’ It is ‘we redirect X engineer-hours per year to the specific work only this team can do.’ The framing shifts attention from cost reduction to strategic reallocation, which is the correct frame for an engineering-capacity decision.

The strategic reallocation frame invites a specific question: what work can only this team do? For most firms, the answer is the work that differentiates the firm from its competitors. The calculator maintenance was work any competent engineering team could do; the differentiating work is what the team was hired for and what the firm competes on. VPs of engineering who cannot answer the question of what work only their team can do have a specific gap the reclamation might expose. The gap is not the reclamation’s fault; the reclamation surfaces the gap by making the alternative use of engineering capacity a visible question rather than a hypothetical one.

The retention effect

A specific side effect of the reclamation that VPs of engineering underweight is the retention effect on senior engineers. Senior engineers who spent quarters on calculator maintenance were spending them on work that was not the reason they joined the firm. The specific work — reading revenue procedures, updating constants, debugging edge cases in code they inherited — is work senior engineers have generally done many times and are unenthusiastic about repeating.

Reclaimed capacity that goes to differentiating work is capacity these engineers experience as work worth doing. The retention effect is not usually measurable in any single quarter; it shows up in the willingness of senior engineers to stay through the medium term, and in the ability of the firm to attract senior engineers who ask, during interviews, what the team is actually working on. A firm whose answer to that question involves the calculator maintenance calendar is at a disadvantage against a firm whose answer involves the differentiating work.

How to present the case to leadership

The presentation to executive leadership is short. First, name the specific engineer-quarters currently going to calculator maintenance, including the hidden hours the finance ledger has been under-attributing. Second, name the specific differentiating work those quarters would be spent on if freed. Third, name the specific vendor evaluation the engineering team has completed or plans to complete. Fourth, name the specific expected outcome of the reclamation in the first fiscal year: which features close their slipping gaps, which new features become possible, what the baseline velocity looks like.

The presentation is not a request for permission to externalize; it is a proposal to reallocate engineering capacity toward strategic work. Framed that way, the presentation is a specific strategic conversation rather than a cost-management conversation. Cost-management conversations produce cost-management decisions; strategic conversations produce strategic decisions. The reclamation is genuinely a strategic decision; framing it as such is what makes the decision defensible over time.

“The reclaimed quarters are not a saving. They are a redirection. What the team redirects toward is the strategic question the reclamation forces.”

The engineering-culture change

Firms that externalize calculator math over a fiscal year should expect a culture change in the engineering organization: engineering conversations shift from ‘how do we keep this working’ to ‘what should we build next.’ The shift is a symptom of the reclamation; when maintenance is not consuming the team’s cognitive load, the team’s cognitive load is available for construction. VPs of engineering who lead teams through this shift experience a specific improvement in team energy that predates any specific new feature shipping. The shift itself is the outcome; the features that follow are what the shift enables.

This is the specific reason the engineering-leadership case for externalization is not only about hours. Hours are what the ledger captures. What the ledger does not capture is the cognitive-load reduction and the strategic reorientation the reclamation produces. Both are real, both matter more than the hours themselves, and both are what the roadmap-you-get-back framing is pointing at. The roadmap is the visible artifact; the invisible artifact is a team whose energy matches its ambition.