The ticket is filed. "Refactor auth service." It sits in the backlog. It is prioritized behind three features with revenue attached.
It never gets scheduled. There is always a feature with more revenue attached. The tech debt ticket ages. It grows. It is joined by others. The backlog accumulates a sediment layer of intent that nobody acts on.
This is not a prioritization failure. It is a structural inevitability.
⸻
The Invisible Cost
Technical debt has no customer. No executive is asking for it. No sales team is blocked on it. It produces no measurable revenue when resolved and no immediate failure when ignored.
The cost of tech debt is degradation rate. Deployments take longer. Features cost more. New engineers ramp slower. But these costs are distributed across every project, making them invisible in any single budget line.
The organization sees features as investments with returns. It sees tech debt remediation as cost without return. This framing is wrong, but it is the framing the budgeting system uses.
⸻
The Translation Failure
Engineers describe tech debt in engineering terms. "The service layer violates single responsibility." "The data model has accumulated schema drift." "The test suite has a 40-minute runtime."
Leadership hears: the engineers want to rewrite working code for aesthetic reasons.
The engineer failed to translate. The correct framing is not "The test suite is slow." It is "The test suite adds two hours per developer per day to the feedback loop, which means a team of eight is losing 80 hours per week of productivity. At our engineering cost rate, that is $160,000 per month."
Tech debt enters the conversation when it is denominated in the currency the budget process understands.
⸻
The Interest Payment
Ignoring tech debt does not make it free. It makes it compound.
The workaround introduced in March becomes a pattern by June. Three new features are built on top of a foundation that was supposed to be temporary. By December, fixing the original debt also requires refactoring the three features that depend on it.
The cost of remediation has tripled. The window during which the fix was cheap has closed. The organization now has a choice between an expensive remediation or permanent degradation.
⸻
The Quarterly Allocation
Tech debt will never win a prioritization battle against a revenue-attached feature. Stop fighting that battle.
Negotiate a standing allocation. Twenty percent of every sprint dedicated to debt remediation, non-negotiable, not subject to the prioritization process. This is not a luxury. It is maintenance. Buildings have maintenance budgets. Software must too.
If leadership will not approve a standing allocation, name the specific failure that underfunded maintenance will produce in the next twelve months. Make the risk concrete. Make it personal. Abstractions do not get funded. Predicted outages do.
End.