Technical Debt, The Business Choice That Changes the Game

Your competitor launches a feature. Your team says five months. And the explanation is always the same: technical debt.

You don't know if it's a serious problem or an excuse. You don't know how much it will cost to fix. You don't know if it could have been avoided. And nobody remembers who decided what, because the person who made the call often doesn't work there any more.

This book starts from a simple idea: technical debt is not a mistake to hide, nor a problem to leave to the engineers. It is a business choice. And like every choice, you can make it blindly or consciously.

You won't find code here. You'll find the language to read technical debt the way you read a loan, a budget or an investment: with a date, a cost, an owner and an instalment.

What you'll find inside:

• Why debt stays invisible to the very people who allocate resources, and how to bring it to the surface
• How to document a debt decision in a few lines, with a reason, a deadline and an owner
• A seven-field register that turns a vague complaint into a tracked decision
• The thirty-minute monthly meeting that puts debt on the business agenda
• The ritual for paying it down regularly, and how to protect it when emergencies hit
• A method for putting a number on debt: lost speed, turnover, forced maintenance
• Five signs that debt has stopped being a choice and become negligence
• A five-question checklist and three metrics to know whether it is under control
• A practical guide to getting started: from Friday before you log off to your first meeting, including what to do if your CTO says no

Inside are true stories: the team where every new hire leaves within two months, and the SaaS product that loses clients and people after the board orders "no more than 10% of the time".

Who it's for:
CEOs, founders, CFOs, CTOs, tech leads and product managers. Anyone who decides how resources are invested, at every level of the organisation. Anyone who launched an MVP with AI and is now being told it's nothing but technical debt. Anyone who has to explain to the board why it takes five months.

A short, dense essay you can read in a few hours and put to work on Monday.