Top Technology / Architecture & core decisions
Technical debtThe concept
Every time a team says "let's do this quick now and fix it later", your company takes on debt. It shows up on no statement, yet it's paid every month.
It's the future cost of software decisions made the fast way instead of the right way. Sometimes it's sensible —beating your competition to market can be worth a little debt—. The problem isn't having it: it's having it without knowing and never paying it down.
It's like a credit card. Financing an urgent purchase can be smart. But if you only pay the minimum month after month, the interest ends up costing more than the original purchase. Software works the same way: debt that's never paid down grows on its own.
Impact on the business
Because technical debt doesn't stay in the IT department: it turns into business results you do see.
What used to take a week now takes three, because each change risks breaking something else.
And with them, customer complaints, support hours and team burnout.
Fragile systems are also insecure systems. The bill arrives all at once, at the worst moment.
No talented engineer wants to spend the day firefighting code nobody understands.
Industry reference ranges for software. Real results vary by organization.
Measurement
You don't need to read code to size up your technical debt. You need to ask —and get answers in numbers, not excuses— these questions:
Compare how long deliveries took a year ago versus today. If the team is the same or larger but ships less, that gap is the interest you pay.
What share of time goes to fixing errors instead of building? Above 30% sustained, debt already governs your operation.
How many people would have to be out for no one to be able to touch a system? If the answer is "one", you don't have software: you have a hostage.
A healthy business devotes around 15–20% of its development capacity to paying down debt continuously —refactoring, testing, documenting—. It's not an expense: it's the maintenance that avoids tomorrow's very costly rescue.
Quick diagnosis
Conclusion
Technical debt can't be wiped out overnight, and trying to pay it all at once is usually as bad a deal as ignoring it. The right answer is to make it visible, put a number on it and manage it: decide with data how much to pay down, when, and how much you can tolerate without risk. That's a business decision, not a technicality —which is why it belongs on your desk.
In a free assessment session we review your situation and tell you, in business terms, where your debt is and what I would do about it.
Book your free assessment