Management rejected three tech debt proposals. The fourth one passed because I spoke their language.
The first proposal was two paragraphs about code quality, mentioning a module that had become hard to change safely and a request for two weeks to refactor it. It got a polite no, the kind that comes with "let's revisit next quarter" attached. The second was longer, with more technical detail about coupling and test coverage, and got the same answer. The third had a diagram. Still no. Each…
Three attempts to address tech debt were rejected, but a fourth proposal succeeded after it was rephrased. The initial proposals focused on code quality, coupling, and test coverage without considering the impact on engineering time. Management preferred concrete, comparative data over abstract technical explanations. The fourth proposal reframed the issue by highlighting specific production incidents and delivery delays caused by the module.
By presenting the costs of continued neglect in terms the decision-makers could easily understand, the argument resonated better and was approved in the same meeting.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
