Pod Insights The Agile Daily Standup - AgileDad How To Defeat The 3 Most Common Arguments Against Technical Debt About this episode How To Defeat The 3 Most Common Arguments Against Technical DebtI once worked on a project where we weren’t able to think about technical debt until five years in. Like many startups, we had to hustle to get off the ground. In those initial years, we didn’t have much time or capacity to even think about addressing the debt we accumulated. And did it ever accumulate. How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:16 Speaker 00 Let's talk about technical debt. I am referring to an article that was sent in to me, so I appreciate one of my subscribers sending this in. I once worked on a project where we weren't able to think about technical debt until five years in. Could you imagine this? Like many startups, we had to hustle to get the product off the ground. In those initial years, we didn't have much time or capacity to even think about addressing debt that we accumulated. And did it ever accumulate? Touching one class in the code created ripple effects through many others. When new people joined the team, navigating it felt like sorting through dozens of unorganized filing cabinets. We even had one engineer refactoring full time. In one year, he untitled maybe 20% of the total volume of the legacy code.
0:59 Speaker 00 At that rate, it would take another five years to do a whole system. And that's not even counting the new debt that was generated during that time. Not all examples are this extreme, but we all know technical debt is a major issue. However, many don't. They don't treat it as such. They're more than prepared to make arguments about why. So the best you can do is to prepare arguments to counter when they tell you why.
1:26 Speaker 00 So as you could probably guess, or may already know, the company's business side creates most of the resistance to addressing the technical debt. They're not doing this maliciously, though. Their job is to deliver products and features and services quickly. So if coding takes a month, sales reps will want a project finished within this timeframe. If you suggest addressing debt at the same time, it means adding an additional couple of weeks to the timeline. While the improved code is attractive to us and will eventually be attractive to the customers, they still resist. Wondering what the point is if the product's going to work on arrival without those adjustments. Your instinct will be to react impulsively, telling them how wrong they are and just how damaging this type of debt could be. But all you'll accomplish is similar reaction for them.
2:10 Speaker 00 Instead, learn what they're really saying and speak directly to that. And you don't have to spend a lot of your precious time on this task because most arguments boil down to a few common reasons that people have against addressing technical debt. Let's start at the top. Technical debt isn't our problem. Some sloppy engineers cause technical debt with bad code. Their follow-up is that since those engineers are responsible, they should take care of the problems on their own time. What people are really saying is, people say this aren't denying technical debt as a problem, but they're shifting the blame to the engineers as if it's something that they can control and snap a finger and fix. Their thinking is that if everything was done correctly to begin with, technical debt wouldn't exist.
2:54 Speaker 00 In other words, technical debt is the exception instead of the rule. And as you well know, there's nothing further from the truth. So the trick here is convincing people who make this argument that the debt is a normal part of the process and shouldn't be stigmatized. So what you could say back, imagine you're moving from one house to another one. You need to transport a couch and all you own is a Fiat 500. You can't fit the couch inside, so you strap it onto the top of the car and start driving. This looks funny, but what else are you supposed to do? You don't have the money to run a moving truck or the time, parts, and money to turn the Fiat into a minivan. In short, the answer is you have to make do with what you have and get the couch there because you promised it would be there.
3:39 Speaker 00 Blaming engineers for creating technical debt is like blaming the driver for putting the couch on their car. In a perfect world, we'd have time, capacity, and the perfect vehicle to do everything. But we don't. We constantly have to make trade-offs between perfection and speed. Explain these concepts to the other side so that they understand it too. And you can start making decisions about how to deal with the problem together. Fiat example's great. We won't meet our goals. Imagine you're talking to a project manager and asking for more engineers to be allocated for a difficult piece of technical debt. That's not possible, they reply. If we give you more engineers, we're not going to get everything done to meet our next milestone. This one's really easy to understand, but the argument is worth exploring further,
4:23 Speaker 00 because why would anyone fall victim to short-term gains over long-term ones? Because the industry supports this attitude. While you may stick with a company for many years, others won't. And that's they have a choice. Sometimes companies go about laying off workers, going out of business, merge and become redundant, and so on. That's not to mention people taking on short-term or part-time work, leaving the company for personal reasons such as moving, or wanting to try something new. Regardless, would you care what happens at work after you leave a company? No matter how passionate or dedicated you are, it's not your concern anymore. Even if you are concerned, there's really nothing you can do about it. Plus, a product manager's goals are always going to be different from your own,
5:06 Speaker 00 driven by a different perspective and pressure from their supervisors. So instead, here's what you could say back. You have to make the case that if you don't address technical debt now, the team will have even less time to make things down the road. Older systems are harder to use, maintain, and learn. So people waste even more time caring for the issues later than if they just fixed them in the first place. But this is as easy as telling a 20-year-old student they shouldn't party so hard because they'll need their body for years to come. Again, what's the short-term benefit for them by considering the longer-term ones? No matter how you phrase your response, this is a likely discussion you're going to lose. However, while you won't get as much time or as many engineers as you'd like, you can get some.
5:51 Speaker 00 Show them the value of assigning at least a few people, individual contributors, to the work for however much time they're willing to spare each month, and settle for a compromise. Then you can prove the value to them with the results the compromise created, and maybe you'll get more next time. Okay, let's think about the third one. We'll have to think about survival first. In most cases, you can advocate for addressing technical debt by appealing to your team's long-term plans. Startups are the exception to this rule. If you've never worked for one, know that they're under incredible pressure to adapt, survive, and find their market fit. What people are really saying is startups are in constant crisis mode. They don't know what shape they'll end up taking, let alone the luxury of thinking about technical debt.
6:34 Speaker 00 Tell a startup to dedicate regular time to refactoring will get you a bunch of blank stares. But that's actually okay. What you can say back? Imagine you're a digital nomad. You change where you will live every year or so. With this in mind, why would you start buying furniture before you're ready to settle down? You'll just be wasting time, money, and effort. In the same way, the first few years of a startup are deeply unpredictable. They change direction as they go along and something that seemed like working code can become technical debt after a pivot. Immediately addressing it doesn't make sense then. So the solution is not to push for refactoring as much. Instead, spend time preparing to address the issue. So when it's necessary, you're ready. Setting up good logging practices.
7:18 Speaker 00 At the very least, you've tagged and organized issues in order to tackle them later. What you do, what do you do if you can't change someone's mind? Because that happens. There's almost always more room for negotiation and compromise than might be first apparent. But there will still be times where you won't immediately change someone's mind about addressing technical debt. And this may have nothing to do with how well crafted your responses are. Sometimes people are just in a bad mood, not ready to hear another perspective, are unable to make change you're asking for, possibly due to directives from above. There are two things you can do at this point. The first is switch strategies and try to change their minds by using metrics and numbers. Data wins, right? This means learning how to measure the impact of addressing technical debt.
8:00 Speaker 00 This may be difficult at first, but you can measure most things, even if indirectly. Your main goal is having figures that show how addressing tech, technical debt saves money down the line or speeds up other goals. Again, frame what you say with problems they care about and you'll have more success. The second is acceptance. Even if you're the most well spoken convincing person of all time, you won't win every argument. Not every piece of technical debt you find worrying will, or even should be addressed.
8:34 Speaker 00 We talked earlier about compromise. Be prepared to offer this as well. When someone says they simply can't prioritize debt at the moment, ask them what you can do to help them with their priorities. This could very well speed those issues up and do the same for freeing up people to address the debt. Plus, they'll more likely listen to you in the future once they see you're willing to listen to them. Ultimately, this mindset separates you from other people and engineers on your team. You have the balance, you have to balance competing priorities and make peace with suboptimal decisions. And you must become a master of salvaging imperfect situations and solutions. As you do, you'll find yourself living those choices that are just a bit easier than before.
9:19 Speaker 00 You'll start seeing issues you thought were the most critical alongside the ones that you saw as the same. And you'll be able to work together more effectively and find solutions to all the short-term and long-term issues. You're going to get pushback when you ask for people to address technical debt, but I think you need to just realize that as long as you negotiate and form and remind your colleagues and stakeholders that it's necessary to do so, it's worth a trip, it's worth a journey, and it's worth a try because the amount of time and energy you save is going to save the company very exponentially more in the future. That's going to do it. I hope you enjoyed this episode. If you have a topic you want us to discuss, learn more at agiledebt.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends.
10:03 Speaker 00 Until next time, do take care.
Previous Agile Is Broken, So What Should Startups and Tech Companies Do Instead? Next 18 Cheat Codes to Life, to Put You 10 Years Ahead of Other People Page updated November 7, 2026 · transcript and summary are machine-generated