The phrase “technical debt” has such a negative connotation for something that happens in basically every organization. I mean, the word “debt” is literally in there. We typically think of technical debt as any sort of unplanned or unscheduled work that needs to be done by an engineering team that you’ve accumulated over time as a result of other actions made - whether it’s productionizing a patch (yes, we all have those “temporary” fixes) or upgrade packages within your repo, this engineering-driven work always holds a very necessary part of your overall roadmap.
Subscribe to All Access to read the rest.
Become a paying subscriber of All Access to get access to this post and other subscriber-only content.
UpgradeA subscription gets you:
- Gain access to all historical content 4+ weeks old
- Receive a monthly deep dive on a leadership topic designed to make you a stronger, more influential leader