Somebody That I Used to Know
Gotye (feat. Kimbra)
“You can be addicted to a certain kind of sadness.”
The Business Angle
Organizations and individuals become attached to legacy systems, processes, and ways of working — even when they cause friction. The familiar discomfort of the old beats the uncertainty of the new. It's a strange comfort, choosing the devil you know over the one you don't.
This maps directly to status quo bias, sunk cost fallacy, and resistance to digital transformation. Teams defend aging infrastructure not because it's better, but because it's known. Processes persist not because they work, but because rebuilding them feels riskier than tolerating them.
Change management isn't just about deploying new technology — it's about breaking the emotional dependency on legacy ways of doing things. Acknowledge the grief. Name the attachment. Then move forward anyway.
7 Rings
Ariana Grande
“People who say money can’t solve their problems must not have had enough money to solve them.”
The Business Angle
Underfunded IT teams often treat tool selection, infrastructure upgrades, and talent acquisition as unsolvable problems — when the real constraint is budget. "We can't fix that" frequently translates to "we haven't allocated what it would cost to fix that." Adequate investment unlocks options that didn't exist before.
This speaks directly to IT budget advocacy and the hidden cost of technical debt. Every year an aging system isn't replaced, the organization pays in productivity loss, security exposure, and engineer burnout. The "savings" from not upgrading are often illusory — they're just future costs in disguise.
Chronically understaffed engineering organizations stay stuck in cycles of firefighting instead of building. You can't innovate when your whole team is on-call for a system that should have been retired three budget cycles ago. Sometimes the most strategic thing a technology leader can do is make the business case — clearly, loudly, and with data — for simply spending the money.