HS129: Achieving Operational Excellence

The Everything Feed - All Packet Pushers Pods39mApril 7, 2026

Get the full intelligence

Search transcripts, export clips, track mentions, and explore all topics from “HS129: Achieving Operational Excellence” inside PodZeus.

AI-Generated Summary

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.

Key Takeaways
1

After-action reviews must be consistent, structured, and psychologically safe to generate real improvement.

2

Apply manufacturing principles like theory of constraints and lean to software development to reduce waste and improve flow.

3

Focus on root cause analysis using the 'five whys' to avoid blaming individuals and fix systemic issues.

4

AI can accelerate knowledge creation but won't fix flawed processes—waste on top of AI is still waste.

5

Overproduction of features, even when code is cheap, increases long-term support and complexity costs.

…and 3 more takeaways available in PodZeus

Chapters
0:00
1 min

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.

0:44
1 min

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.

2:05
3 min

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.

5:00
4 min

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.

9:13
8 min

Theory of Constraints: From Manufacturing to Software

Busy is not the same as productive, and that's always important.

Highlight
High-Impact Quotes
I'm in a business of manufacturing knowledge, not which.
John Miranda32:08
Viral: 95.0
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?
John Miranda18:40
Viral: 90.0
Busy is not the same as productive, and that's always important.
John Miranda11:09
Viral: 85.0
Speakers

Hosts

John Achill JohnsonJohn Burke

Guest

John Miranda
Topics Discussed
after-action reviews95%operational excellence95%theory of constraints90%root cause analysis90%software development quality85%knowledge manufacturing85%lean management80%ai and operational efficiency75%
People & Brands

John Miranda

person

25xPositive

after-action review

other

12xPositive

software development

other

10xPositive

defects

other

8xNegative

AI

other

8xMixed

theory of constraints

other

7xPositive

five whys

other

6xPositive

Intel

organization

6xNeutral

overproduction

other

5xNegative

Meter

organization

5xPositive

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