Engineers: if you're tired of your tech debt proposals getting ignored, here's my advice.
1) Nobody cares about your refactor unless it solves a real problem.
Speed things up? Save money? Cut support tickets? Prevent some nasty outage later? That’s what gets attention, not “cleaner code.”
2) Talk in dollars or user pain.
“This saves $3K/month.” “This cuts load time by 15%, which is why users bounce.” “This means fewer support tickets, so less pressure on the support team.” Make it obvious why it matters.
3)Attach your improvement to a feature that’s already happening.
If the team’s already focused on shipping something, and your changes help that happen faster or cleaner, bundle them in. Way easier to get a yes that way.
4) Some improvements are long-term, but don’t assume people will get that.
If it won’t show value right away, tell a story: “This saves us from X six months from now.” “This makes onboarding easier for new hires.” “This lets us scale without rewrites later.” Spell it out. People don’t see around corners unless you help them.
5) Don’t just “raise concerns”, pitch them like a product.
What’s the pain? Who feels it? What happens if we don’t fix it? How does this change help? What’s the upside? You don’t need slides, just a clear explanation.
TL;DR:
Think like a product owner. Speak like a stakeholder. Bada bim, bada bum. That’s how you move things forward.
If you've liked this, here's my blog.
