Me, Myself & IT Leadership · 7. Sept. 2026 · 18:51
In der Podli-App hören 🎧
Folge deinen Lieblingspodcasts, höre offline und im Auto mit CarPlay und Android Auto und mach immer dort weiter, wo du warst. Kostenlos ausprobieren.
This episode looks at technical debt not as a coding problem but as a leadership problem. Daniel and Nova work through why companies manage financial debt with precision, interest rates, owners, and repayment terms, while technical debt usually just gets pushed into the backlog. They cover what technical debt actually includes beyond old code, why taking it on can be the right business call under time pressure, and why the real failure happens later, once nobody remembers what was borrowed or why. The core of the conversation is Daniel's five-step "debt ladder," running from deliberate debt to hostage debt, plus a concrete mechanism for putting technical debt on the books the way depreciation works in finance.
Key topics:
- Why taking on technical debt can be the right business decision, and why the failure is not tracking it afterward
- The real costs of unmanaged technical debt: slower changes, more incidents, vendor lock-in, security exposure, frustrated developers
- The incentive mismatch where the business unit that benefits from a shortcut is never the one who pays for it later
- Daniel's five-level debt ladder: deliberate, orphaned, forgotten, structural, and hostage debt
- Why a debt register needs four fixed fields per entry: a price, an owner, a repayment budget, and a term
- Answering a CFO's objection that a dedicated repayment budget just becomes a blank check for IT
- Anchoring debt repayment in a formal controlling process, similar to depreciation, so it survives beyond one budget cycle
- Where AI can already help today: scanning codebases and processes to surface forgotten and structural debt faster than manual audits
Key takeaway: Technical debt itself is not the problem, since taking it on deliberately can be the right call under pressure. The failure is losing track of it, with no price tag, no owner, no budget, and no repayment date. Daniel argues the fix is structural, not moral: put repayment on whoever took out the loan, register every debt with a price and an owner, and anchor repayment in the same kind of formal process companies already use for depreciation.
Folgen: Me, Myself & IT Leadership