Skip to content
Knight Capital: Technical Debt is Leadership Debt episode artwork

Apr 23, 2026 24 min

Knight Capital: Technical Debt is Leadership Debt

from Project Management is Boring

This season has explored a pattern many organizations miss: Failures rarely begin in the moment of collapse. They begin earlier. In assumptions left unverified. In controls left untested. In drift left unmanaged. In governance that looked stronger than it was. Today we’re talking about another one of those quiet beginnings: Technical debt. Usually, technical debt is discussed like an engineering inconvenience. Messy code. Old systems. Deferred cleanup. Something the technical team should “handle later.” But technical debt is rarely just technical. Because every unresolved weakness survives through organizational choice. Someone funded features instead of remediation. Someone accepted short-term speed over long-term resilience. Someone tolerated fragility because the consequences were not immediate. That means technical debt is often leadership debt. It reflects decisions about what risk is allowed to remain. And this episode is about how project management helps make that risk visible. Because leadership decides what gets fixed. And leadership also decides what risk lives.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Knight Capital: Technical Debt is Leadership Debt

0:00 24:20

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of Project Management is Boring?

This episode is 24 minutes long.

When was this Project Management is Boring episode published?

This episode was published on April 23, 2026.

Can I download this Project Management is Boring episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.