The conversation around AI often focuses on speed, automation, and productivity. Yet one of the most important lessons emerging from modern software development is that Hero Culture Risks become more visible as technology removes traditional bottlenecks. In Building Better Developers Season 28 Episode 8, Dave Borzillo shared a perspective many experienced developers recognize immediately: being the person who always saves the day feels rewarding, but it often masks deeper organizational problems. As AI accelerates software creation, those hidden weaknesses are becoming harder to ignore.
About David Borzillo
David Borzillo is an Agile coach, author, speaker, and organizational improvement advocate with more than three decades of experience spanning software development, leadership, Agile transformation, and product delivery. Through his Better Ways of Working platform, he helps organizations improve collaboration, reduce operational friction, and create sustainable delivery systems. He is the author of Sanity at Scale and Who Killed Agile? (co-authored), and United Agility, and hosts the Better Ways of Working podcast.
Follow David: https://betterwaysofworking.com/about.html
Bonus: Free Kindle Promotion
📚 David Borzillo’s new book: Sanity at Scale
Amazon Link:
https://www.amazon.com/dp/B0H41M87KJ
Free Kindle Weekend
June 26–28
- Download the Kindle edition free during the promotion period.
- If you’re a Kindle Unlimited subscriber, the book is available at no additional cost anytime.
If you download the book, David would appreciate an honest review on Amazon after reading it.
The Hidden Cost of Hero Culture Risks
Most organizations celebrate heroes.
- The developer who answers the 4 a.m. call.
- The engineer who fixes production.
- The architect who understands the entire system.
Dave described being that person earlier in his career. Solving critical problems created a sense of accomplishment, but every rescue also prevented the organization from building repeatable systems and shared knowledge.
- The problem isn’t expertise.
- The problem is dependency.
When success depends on a specific individual, the organization becomes fragile. A hero solves today’s problem. A system prevents tomorrow’s problem.
How AI Makes Hero Culture Risks More Obvious
For years, organizations could hide inefficiencies behind effort:
- If a deployment took three days, everyone accepted it.
- If requirements were unclear, teams worked harder.
- If documentation was weak, experienced developers filled the gaps.
AI changes that equation. As Dave explained, software creation is becoming increasingly automated, much like deployment automation transformed delivery years ago. The result? The bottleneck shifts away from coding.
Organizations are discovering that their real constraints often exist in:
- Requirements gathering
- Stakeholder communication
- Product prioritization
- Team alignment
- Knowledge sharing
AI can generate code quickly. It cannot automatically create organizational clarity.
Hero Culture Risks Often Start with Poor Value Definition
One of the strongest concepts discussed in the episode was Dave’s idea of a value litmus test. Instead of building for vague departments or anonymous stakeholders, teams should identify actual people who benefit from the work. He described moving beyond “the marketing department” to serving a specific individual and understanding the value being delivered.
This shift matters because many hero-driven organizations optimize for activity rather than outcomes.
- Developers become busy.
- Projects move forward.
- Features ship.
- But nobody clearly understands who benefits or why.
AI magnifies this issue because it dramatically increases output capacity. Without clear value definitions, teams simply generate more work faster. AI can accelerate confusion just as effectively as it accelerates productivity.
Preventing Hero Culture Risks Through Learning Systems
Dave emphasized creating learning organizations rather than collections of individual heroes.
A learning organization:
- Shares knowledge openly
- Documents decisions
- Encourages cross-functional skills
- Builds repeatable processes
- Improves continuously
This becomes especially important as organizations adopt AI tools. The companies that gain the greatest advantage won’t necessarily be those with the most advanced AI. They will be the organizations that learn the fastest. Knowledge transfer, team collaboration, and continuous improvement become strategic advantages.
Hero Culture Risks and the Future Talent Pipeline
Another important concern raised during the discussion involves junior developers. As AI increases productivity, some organizations may reduce entry-level hiring. Yet Dave warned that today’s junior developers become tomorrow’s senior leaders. This creates a long-term challenge. Organizations that stop developing talent may find themselves without experienced leaders in the future.
Sustainable systems require:
- Mentorship
- Pairing opportunities
- Cross-training
- Knowledge sharing
The strongest teams are not built around heroes. They are built around growth. Evaluate whether your team depends on experts or develops future experts.
Building Resilience Instead of Dependency
The most important takeaway from this episode is that AI is not creating new organizational problems. It is exposing existing ones.
- Teams that rely on individual heroics will feel increasing pressure as development speeds increase.
- Teams that focus on systems, learning, and value creation will be positioned to thrive.
- Technology may continue to accelerate.
Human collaboration remains the real competitive advantage.
Stay Connected: Join the Developreneur Community
👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you’re a seasoned developer or just starting, there’s always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let’s continue exploring the exciting world of software development.