GA 651 | The Soup Stage of Transformation with Ben Morley
Gemba Academy Podcast: Lean Six Sigma | Toyota Kata | Productivity | LeadershipShow Notes
Most resistance to lean is blamed on the wrong thing. Ben Morley, an Air Force pilot turned Lean Six Sigma consultant, argues the tools are never really the problem. The breakdown almost always lives somewhere between leadership buy-in and an assumption nobody thought to question. His conversation with Ron Pereira covers cockpit emergencies, a $5 million backlog that dissolved from a single customer phone call, and what a caterpillar turning to soup has to do with organizational transformation.
In this episode you’ll learn:
How a single quote reframes what transformation actually looks like (1:59)
What flying C-17s across seven continents taught Ben about process discipline (3:26)
How DMAIC and pilot training turn out to be the same methodology (7:44)
Why skipping rigor in the define phase creates variation in the cockpit and the conference room (9:41)
How preparation before an in-flight emergency keeps your hands moving while your mind stays clear (15:39)
What to do when crossed arms and skepticism greet you on day one (20:41)
Why values on the website and culture on the floor are two different things (22:34)
When loyalty to a system that keeps you stuck is the real thing to diagnose (25:38)
“Values are your belief. Culture is your behavior. Those are two different things.” – Ben Morley
Keep Learning
If the gap between what your organization says it believes and how people actually behave on the floor resonated with you, the School of Leadership addresses exactly that kind of culture-and-conduct disconnect.
Learn More About School of Leadership at gembaacademy.com/leadership
Podcast Resources
Ben on LinkedIn
Ben’s Website
Caterpillar Soup at 30,000 Feet
Get All the Latest News from Gemba Academy
Stay current on new courses, podcast episodes, and continuous improvement resources. Sign up for the Gemba Academy newsletter at gembaacademy.com/news
What Do You Think?
Where in your own organization is dormancy being mistaken for absence of progress?
More from Gemba Academy Podcast: Lean Six Sigma | Toyota Kata | Productivity | Leadership
Most kaizen practitioners know the moment when a skeptic turns. It can take a day, a week, or nine months, but something clicks and the person who crossed their arms at the start is now telling the VP what their line accomplished. Adam Lawrence has spent decades collecting those moments, and he has built a framework around making them more likely to happen. That framework just got a significant overhaul.
Most people who feel overwhelmed blame their schedule. Peggy Sullivan argues the diagnosis itself is wrong. Time poverty has nothing to do with time management and everything to do with capacity, and until you start subtracting, no amount of better planning will get you out from under it.
Value stream mapping is one of the most familiar tools in lean practice. Christian Wolcott has spent 25 years using it with clients from Toyota suppliers to NASA, and he arrived at a question that most practitioners never think to ask: what if you mapped your own life the same way? The seed came not from a client engagement or a sensei, but from his daughter, who sketched a rough timeline on a note card after joining him on a Japan study tour. That sketch became a book, and the book became a method.
Most lean practitioners know the theory of constraints. Fewer apply it before they start fixing things. Hessam Vali, a manufacturing consultant and MES software founder based in Wichita, argues that most improvement efforts fail because they target the wrong kinks in the hose. His framework is deceptively simple: if the deepest constraint is still in place, no one will ever see your work.
Most continuous improvement practitioners are using AI the same way they use Google, and getting roughly the same quality of results. David Osagie-Igiehon has taken a different approach. He builds custom agents trained on lean principles, CI methodology, and the specific knowledge domains his work demands, and the gap in output quality is significant. What he describes is less about automation and more about compressing the time it takes to do rigorous work.