In this episode of Technical Debt: Design, Risk and Beyond, Maxim Silaev is joined by Rob Broadhead, a technology leader with more than 30 years of experience across enterprise systems, startups, and consulting.

Together, they explore how technical debt actually creeps into systems: not through bad engineering, but through reasonable decisions made under pressure. Rob shares early-career scars, leadership failures without happy endings, and hard-earned lessons about how debt becomes normalised inside teams.

A large part of the conversation focuses on modern tooling and AI. While AI promises speed, Rob explains how “vibe coding” and unreviewed AI output can quietly amplify existing problems: shifting debt from code into architecture, design, and assumptions. When teams stop asking the right questions, systems slow down, trust erodes, and recovery becomes expensive.

This episode also dives into leadership responsibility: why strong teams still fail, how lack of authority distorts decision-making, and why delaying cleanup for “one more release” almost always backfires.

If you are a CTO, architect, or technical leader navigating growth, AI adoption, or mounting complexity, this conversation will feel uncomfortably familiar.

Topics covered:

• Where technical debt is really born
• How bad patterns become “normal”
• AI as an accelerator of existing habits
• Early non-technical warning signs of dangerous debt
• Why cleanup efforts fail — and how to avoid that
• Leadership habits that prevent debt from becoming a way of life

Connect with Rob on his website.

Send us a text

Reach us @ LinkedIn:

https://www.linkedin.com/in/maxim-silaev
https://www.linkedin.com/in/dr-nikita-golovko