HS129: Achieving Operational Excellence
Get the full intelligence
Search transcripts, export clips, track mentions, and explore all topics from “HS129: Achieving Operational Excellence” inside PodZeus.
In this episode of Heavy Strategy, John Miranda, a Cal Poly Business School faculty member and former Intel strategist, shares his transformative experience leading a struggling software development team responsible for high-stakes financial modeling that influenced $20 billion in investments. Facing a crisis of quality with frequent defects escaping production, Miranda led a two-day off-site workshop to reset the team’s operating model, drawing inspiration from manufacturing principles like lean management, theory of constraints, and after-action reviews (AARs). By shifting focus from blame to systemic root cause analysis—using techniques like the 'five whys'—and embedding AARs into the team’s biweekly sprint cycles, the team reduced defects by 10x over 18 months. This cultural shift not only improved product reliability but also boosted team productivity, predictability, and stakeholder confidence. Miranda emphasizes that operational excellence isn't achieved overnight but through consistent practice, psychological safety, and leadership role modeling. He also warns that AI, while powerful, can amplify waste if applied to inefficient processes and cautions against overproduction of features, even when code creation costs near zero. The episode concludes with a reflection on the durability of cultural change and the importance of nurturing continuous improvement habits. Key takeaways include: (1) Use after-action reviews not as blame sessions but as tools to generate organizational knowledge; (2) Apply manufacturing principles like theory of constraints and lean to software development to reduce waste and improve flow; (3) Prioritize consistency and psychological safety over perfection—celebrate small wins to build momentum; (4) AI should augment, not replace, disciplined processes; (5) Overproduction of features, even at near-zero cost, creates long-term technical debt and support burden; (6) Cultural change takes time—18 months in this case—but builds lasting resilience; (7) Leadership must role model vulnerability and accountability to foster trust; (8) Small, recurring inefficiencies compound into major productivity drains and should be addressed systematically.
After-action reviews must be consistent, structured, and psychologically safe to generate real improvement.
Apply manufacturing principles like theory of constraints and lean to software development to reduce waste and improve flow.
Focus on root cause analysis using the 'five whys' to avoid blaming individuals and fix systemic issues.
AI can accelerate knowledge creation but won't fix flawed processes—waste on top of AI is still waste.
Overproduction of features, even when code is cheap, increases long-term support and complexity costs.
…and 3 more takeaways available in PodZeus
Sponsor: Meter - Full-Stack Networking
Sponsorship announcement for Meter, a company offering integrated wired, wireless, and cellular networking solutions for enterprises, with a focus on performance, scalability, and single-provider simplicity.
Introduction and Guest Welcome
Hosts John Achill Johnson and John Burke introduce the episode and welcome guest John Miranda, a Cal Poly faculty member and former Intel strategist, who will discuss operational excellence through after-action reviews.
The Crisis: High-Stakes Software with Frequent Defects
Miranda describes inheriting a software team responsible for billion-dollar investment models that were plagued by recurring defects—about one in every four releases—leading to stakeholder distrust and constant firefighting.
The Reset: Two-Day Workshop on Lean and Agile Methods
The team undergoes a two-day off-site workshop to adopt lean, agile, and theory of constraints principles, with a focus on building skills in root cause analysis and after-action reviews, and committing to a new operating model.
Theory of Constraints: From Manufacturing to Software
“Busy is not the same as productive, and that's always important.”
“I'm in a business of manufacturing knowledge, not which.”
“I could have made the same mistake Mary did. So let's kind of get into, could we have done a process that could have prevented any of us from making that mistake?”
“Busy is not the same as productive, and that's always important.”
Hosts
Guest
John Miranda
person
after-action review
other
software development
other
defects
other
AI
other
theory of constraints
other
five whys
other
Intel
organization
overproduction
other
Meter
organization
PP103: FireMon Brings Clarity to Firewall Rule Chaos (Sponsored)
The Everything Feed - All Packet Pushers Pods • 56m • 3/31/2026
HW074: Build Your Own Access Point with Bradley Wegner
The Everything Feed - All Packet Pushers Pods • 26m • 3/31/2026
NAN118: The Importance of the Data Behind AI in Networks (Sponsored)
The Everything Feed - All Packet Pushers Pods • 43m • 4/1/2026
D2DO299: The State of Platform Engineering and DevEx
The Everything Feed - All Packet Pushers Pods • 43m • 4/1/2026
N4N052: Multicast Part 2
The Everything Feed - All Packet Pushers Pods • 1h 25m • 4/2/2026
Get the full intelligence
Search transcripts, export clips, track mentions, and explore all topics from “HS129: Achieving Operational Excellence” inside PodZeus.
Start discovering podcast insights today
Start with a 7-day trial and explore a growing catalog of popular podcasts. No credit card required.
No credit card required • 7-day trial • Cancel anytime
