Technical debt is a leadership problem long before it is an engineering one
Engineers do not choose debt. They accept it, repeatedly, under incentives that leadership designed and rarely revisits.
Technical debt is usually discussed as an engineering failure — a shortcut taken, a standard skipped, a refactor deferred. That framing is comfortable for everyone except the people it blames, and it is mostly wrong.
Debt accumulates where the incentive structure rewards visible delivery and does not price invisible cost. Engineers respond rationally to that structure. If the deadline is real and the consequence of a shortcut lands in eighteen months on somebody else’s quarter, the shortcut is the correct local decision. Repeat that across four teams and three years and you have a system nobody chose and everybody built.
The two questions that reveal the structure
First: when a team says a piece of work will take longer because of an existing weakness, what happens? If the answer is that the scope is trimmed, the date holds, and the weakness remains, the organisation has communicated its priorities unambiguously.
Second: has anyone ever been recognised for work that produced no visible feature? If not, the incentive is settled, and no amount of encouragement to “care about quality” will move it.
What leaders can actually change
- Fund remediation as work with its own allocation rather than as slack teams are expected to find. Slack does not survive contact with a deadline.
- Make the cost legible. Track how long changes take in the worst areas of the system, so debt appears as delivery data rather than engineering opinion.
- Tie remediation to upcoming work. Fixing the part of the system the next two quarters depend on is a business case; fixing everything is a wish.
- Reward the invisible work explicitly, in promotion and in public, or accept that nobody will do it.
- Stop treating every deadline as immovable, because an organisation where every date is fixed has decided to pay for its schedule in debt.
The honest trade
None of this argues that debt is always wrong. Taking it deliberately to reach a market window, win a customer or test a hypothesis is sound judgement, and teams that refuse to ever move quickly have their own pathology.
The difference between healthy and unhealthy is not the amount of debt. It is whether it was chosen, recorded, and scheduled for repayment — or simply accrued because the structure made it the only sensible thing to do, over and over, until the interest exceeded the principal.
Let's build the system your business will run on next.
Tell us where it hurts. We'll bring the architects, engineers, and delivery model to fix it — and scale it.