Infrastructure Debt

Infrastructure debt is not a metaphor for untidy engineering. It is an obligation with a real price, created at a specific moment, carried by a budget that did not create it, and paid every period until the underlying condition is removed.

It matters because it inverts the usual direction of cost analysis. A persistent operating expense is normally read as a management problem in the present. Treated as infrastructure debt, the same expense becomes evidence about a decision in the past — which is the only place it can actually be resolved.

The concept is most useful where the interval between decision and consequence is long enough that the two are no longer discussed together: networks, plant, fleet, facilities, and any environment where capital and operations answer to different people.

• Operational Inheritance

  The operating condition a team is handed rather than chose — decisions made elsewhere whose consequences are absorbed here.

• The Myth of Later

  The belief that deferred work is reduced work. Deferral changes the owner, the form, and the price of an obligation — not its existence.

1. March 2025

   Introduced to describe operating costs that outlive the decisions that produced them.

2. November 2025

   Separated from technical debt. The obligation here is physical and contractual as often as it is architectural, and it is rarely held by the team that incurred it.