Advertise on podcast: Lean Blog Audio: Practical Lean Thinking, Psychological Safety, and Continuous Improvement

In this episode, I read my recent post about a visit to Toyota’s plant in Durban, South Africa, before I spoke at the KZN Lean Conference. I asked to see one thing: how the andon system works there and how it compares to other Toyota plants I’ve visited. About a year ago, the plant replaced the overhead andon cords with two buttons. Yellow calls for help. Red stops the line immediately. I share the two reasons the team gave for the change, including an ergonomics problem that most plants would never have, because most plants don’t use their andon enough. I also talk about what happened when a team member activated the andon while we were watching one station, why their leaders are wary of setting a target to reduce activations, how the plant traces downstream defects back to a station without turning it into blame, and why their suggestion box is only for improvements that are already done. Any company can buy the buttons. What makes it Toyota is everything around them, starting with who shows up in the first minute. Read the post, with photos from the plant and the safari afterward: https://www.leanblog.org/2026/09/the-toyota-andon-system-in-south-africa-two-buttons-instead-of-a-cord/

In July 2013, Volkswagen CEO Martin Winterkorn stopped a test drive to lecture his engineers about paint that was less than a millimeter too thick. A year later, he complained to Der Spiegel that his team never pushed back on him -- that they should have jumped on his desk. That same year, Bob Lutz came on my podcast and described VW as a totally autocratic system where everybody lived in fear, and also the most successful car company in the world. He wasn't wrong about the scoreboard. He was looking at a company whose defeat device software had already been running for seven years. Volkswagen's own investigation identified roughly 450 people involved in the emissions fraud. Over nine years, none of them stopped it. Not for lack of courage -- they had correctly read what happened to anyone who brought that CEO news he hadn't asked for. This episode is about what fear-based leadership actually produces, why the post-scandal CEO move is always some version of "nobody told me," and the question worth asking if you lead anything: not whether your organization has problems, but whether you would hear about them. Read the full post My next book, The Silence Tax: How Lean Leaders Drive Out Fear and Futility, is coming in early 2027.

What does it really mean when a problem “comes back” after a team thought it had been solved? In this episode, Mark Graban reads his article, “We Thought We Solved That: The Art and Judgment Calls in the PDSA Cycle.” He examines how a frustrated executive’s question—“Why did the problem come back?”—can either support learning or trigger blame, depending on how it is asked. Mark explores five possible explanations for a recurring problem: the wrong countermeasure, poor implementation, failure to sustain the change, changed conditions, or the possibility that the problem never actually went away. He also explains why Toyota’s language of “countermeasures” is more useful than declaring a problem permanently “solved,” and why process behavior charts can help distinguish real change from routine variation. The larger lesson: reaching the Study step of PDSA requires more than checking whether an action item was completed. Leaders must examine what actually happened, what the data show, and what the organization needs to adjust next. Read and share the original article at leanblog.org/audio471.

A construction worker named Sean Dow was working on the 22nd floor of Pfizer’s former Manhattan headquarters, a massive office building now being converted into residential apartments with additional floors being added. Dow noticed cracks in a concrete slab. When he investigated further, he found a structural column visibly bending. But when he raised the concern, the initial response from the general contractor was reportedly, “Don’t worry, you’ll work on the floor below.” Dow kept pushing. Workers were evacuated, and investigators later found floors sagging by as much as four inches. The story illustrates an important distinction in psychological safety. People remain silent not only because they fear punishment, but also because they believe speaking up will accomplish nothing. A genuine speak-up culture requires concerns to feel both safe to raise and worthwhile to raise. The real test is not whether leaders say they welcome concerns. It is what they do in the first minute after someone brings one forward. Do they dismiss the concern and offer reassurance without investigating? Or do they respond with curiosity and say, “Show me”? An organization that depends on unusually persistent workers to overcome a dismissive first response is not operating a strong safety culture. It is operating on luck.

A title change is not a culture change. In this episode, Mark Graban draws on his early experience at GM in the mid-1990s — where "foreman" became "team coordinator" overnight without anything else changing — to explore why renaming supervisors with Lean-sounding titles so often fails to deliver Lean results. Read the blog post The discussion centers on Ford's Process Coach role: what it's supposed to be, what it often is in practice, and why the gap between those two things is a leadership system problem, not a training problem. Mark also looks at why Toyota's Group Leader model works where Ford's equivalent often doesn't — and why a senior UAW worker has rational, concrete reasons to turn down a promotion to Process Coach even if they're the most qualified person on the floor. If your organization has rebranded its supervisors without redesigning the conditions those supervisors work in, this episode is worth your time.

Blog post with links Three years ago, The Mistakes That Make Us came out. Around the same time, Elisabeth Swan published Picture Yourself a Leader. Both books' third birthdays felt like a decent reason to get together and talk. On Thursday, May 7, at 1 PM ET, Elisabeth and I are co-hosting a live event on LinkedIn called “Still Learning: Mistakes and Leadership Lessons.” We will talk about what readers have shared with us, what has held up, what we might write differently now, and the leadership questions that keep coming back. Attendees will have a chance to win books and a few other things.

Most AI tools answer your question with a 500-word essay full of numbered steps. You nod, close the tab, and carry on doing what you were already doing. The Lean Hospitals Coach is built around the opposite instinct -- asking questions before giving answers, the way good coaching actually works. Check out the blog post In this episode, Mark walks through how the tool works, why it runs on Claude instead of ChatGPT, and what makes coaching mode fundamentally different from the "here are 7 steps" approach that every other AI defaults to. He also covers the two knowledge sources (Book Search and Book Plus), the two response styles (Tell Me and Coach Me), and how the combinations create different experiences depending on what you need. Mark is opening 50 founding memberships at $49/year -- price locked for life -- and hosting a LinkedIn Live demo on Tuesday, March 10 at 11 AM ET where he'll take audience questions and run them through the coach on screen, unscripted. You can also try the full product free for 48 hours at leanhospitalsbook.com/start.

Read the blog post TL;DR: A sound check, live song requests, and a naming regret — what watching Brandi Carlile perform taught me about specific problem-solving, vulnerability, and continuous improvement. My wife and I got to see the amazing Brandi Carlile perform near Chicago on Friday night. She is a multi-Grammy award-winning singer, musician, and songwriter — though calling her a solo artist would be a mistake...

The blog post TL;DR: Deming and Toyota's Fujio Cho asked the same uncomfortable question: why do management systems destroy motivation in people who started out wanting to do good work? The answer points to practices leaders can actually change. Check part 1 of this series in episode 464,

Read the blog post TL;DR: In a 1993 speech, Toyota leader Fujio Cho said organizations can create their own Lean systems, but success depends on three principles: leaders going to the gemba, asking “why” to learn from problems, and respecting and motivating people — not copying Lean tools.

The blog post What if a book could become an interactive coach instead of a static reference? In this episode, Mark Graban shares a behind-the-scenes look at his experiment turning the award-winning book Lean Hospitals into an AI-powered chat assistant embedded directly on his website. What started as a Friday afternoon curiosity quickly evolved into a working WordPress plugin, a subscription model, and a new way to deliver improvement knowledge on demand. Mark walks through how non-developers can use AI tools to write functional software, what he learned comparing different AI coding assistants, and why the real breakthrough isn’t the technology — it’s the ability to access proven Lean thinking at the moment of need. He also explores the broader implications for leaders and organizations: Could AI assistants trained on your own standards and practices reinforce daily management, support problem solving at the gemba, and scale coaching without more training sessions? This episode is both a practical case study in rapid experimentation and a thoughtful discussion about the future of learning, leadership, and continuous improvement in the age of AI. Key themes include: Turning expertise into on-demand guidance Using AI to prototype software without coding experience Subscription models for knowledge delivery Point-of-use support for leaders and frontline teams Why technology alone won’t create a Lean culture — but can reinforce the right behaviors If you care about scaling improvement capability, preserving organizational knowledge, or simply experimenting with new ways to learn, this episode offers a candid look at what works, what broke, and what might come next.

The blog post In this episode, I explore the 1987 NUMMI Management Practices Executive Summary — a confidential General Motors report that documented why the joint venture between GM and Toyota was succeeding so dramatically. What’s striking is how clearly GM’s own study team understood the real drivers of NUMMI’s performance. It wasn’t tools. It wasn’t discipline. It wasn’t copying Toyota’s production techniques. It was leadership. The report describes a management system built on mutual trust and respect, problem-solving at the source, quality built into the process, and supervisors acting as coaches rather than enforcers. Nearly 40 years ago, GM documented that NUMMI’s success came from management philosophy — not Lean tools. And yet, insight proved easier than action. In this episode, I walk through the document’s key sections, including NUMMI’s basic principles and five major management strategies, and reflect on why translating those lessons into broader cultural change proved so difficult. If you’re interested in Lean leadership, psychological safety, or the origins of what we now call continuous improvement, this historical document offers powerful — and still relevant — lessons.

The blog post In this audio version of the post, Mark Graban reflects on a rare kind of CEO message—one that treats safety not as a compliance checkbox or slogan, but as a core leadership responsibility and a living example of Respect for People. Drawing from the 2025 annual report and CEO letter from GE Aerospace and its leader Larry Culp, Mark explores what it means when safety truly comes first in SQDC—and how that ordering signals what leaders value most, especially under pressure. This episode looks at how safety is embedded into systems, structure, incentives, and daily management through GE’s FLIGHT DECK operating system, rather than being isolated in a department or reduced to culture talk. You’ll hear why safe systems surface problems, why speaking up must be protected (not just encouraged), and why safety is one of the strongest leading indicators of psychological safety and continuous improvement. For leaders working to build trust, learning, and real operational excellence, this is a practical example of what “Respect for People” looks like in action.

In this episode, Mark Graban reads and reflects on his LeanBlog.org post, “When a CEO Talks About the Work: Larry Culp, GE Aerospace, and Real Lean Leadership.” The post examines a rare example of a Fortune 50 CEO—Larry Culp of GE Aerospace—describing operational excellence not through slogans or dashboards, but through safety, trust, and small frontline improvements that compound into real results. This episode explores: What it looks like when a CEO truly understands the work Why Respect for People shows up in system design, not values statements How safety, trust, and daily improvement drive performance Why Lean leadership is about behavior, not buzzwords A practical and concrete example of Lean leadership in action—told through the words, stories, and operational details that CEOs rarely share this openly.

The blog post Many improvement efforts stall not because of poor strategy or missing Lean tools, but because people don’t feel safe speaking up. In this Lean Blog Audio episode, Mark Graban explains why psychological safety is a foundational requirement for continuous improvement. Drawing from his book The Mistakes That Make Us and decades of experience in healthcare, manufacturing, and other industries, Mark explores how fear, blame, and leader reactions silence learning — and how different leadership behaviors make improvement possible. The episode also previews themes from Mark’s upcoming workshop at Shingo Connect 2026, including what psychological safety is (and is not), how it supports accountability rather than lowering standards, and why learning from mistakes depends on creating environments where people can speak honestly without fear.