How Do I Make the Case for Fixing Tech Debt, Not Features?
You see the rot under the floor. They see the roadmap on the wall. Both of you are right, and that is exactly why you keep losing this argument — you are describing a risk, and they are managing a deadline. Risk loses to deadline every time, unless you change what you're showing them. The mistake is not your argument. It is your evidence. You bring judgment — this is bad, this will bite us. They need arithmetic — this already cost us four days, and it will cost four more on the next feature. Vague warnings get filed away. Specific costs get budgeted. You cannot control what they fund. You can control what you measure, what you ask for, and how small you make the ask. Start there.
You are not failing to persuade. You are arguing the wrong case. Stop asking for time to fix debt — show what it already costs: hours lost last sprint, bugs filed, delay added to every feature since. Attach the fix to something they already want built. Choose the smallest repair that unblocks the next release, not the worst debt in the codebase.
What changes unlock by starting
- You stop pleading and start presenting numbers they can act on.
- Your requests get approved because they are small and specific, not large and abstract.
- Leadership starts seeing debt as a cost already paid, not a future risk to debate.
- You build a habit of making invisible work visible before it becomes a crisis.