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 postMy 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 postThe 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.