Would "technical debt" work better as a metaphor if developers explained to business that too much of it made the company vulnerable to the technical equivalent of a hostile takeover?
For example: "If we don't upgrade from MySQL 5.7 soon, we'll get 'owned' by someone who moves faster in the database innovation space."
Imagine trying to make an automobile factory match the unit/day productivity rate of a shoe factory by replacing all the auto-part machines with shoe-part machines. It would turn into an absolute mess.
That's what happens when the specific rituals/processes of one team are forced onto another, very different team without a thought as to how well they would fit.
Developer at ThoughtWorks.
This instance is running on ThoughtWorks infrastructure to allow its employees to create an account and interact with the rest of the Fediverse.
DISCLAIMER: The views or opinions expressed by the users of this instance are solely their own and do not necessarily represent the views or opinions of ThoughtWorks, Inc.