
GA 655 | Behavior Is the Audit with Adam Lawrence
Gemba Academy Podcast: Lean Six Sigma | Toyota Kata | Productivity | LeadershipShow Notes
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.
In this episode you’ll learn:
How the Wheel of Sustainability evolved into something more auditable (4:31)
What leadership engagement looks like the day after a kaizen (5:26)
How five observable patterns replace nine abstract elements (13:09)
What owning the change looks like on the shop floor (16:20)
How earning trust shows up in a leader’s response time (18:08)
Why growing an improvement culture starts with paying attention (20:23)
What getting behavior change right actually requires of leaders (23:03)
How to adjust your approach when the room is full of skeptics (26:48)
Why sustainability is created during every conversation, not after (29:04)
“Sustainability is created during every conversation, every interaction, and every leadership behavior.” – Adam Lawrence
Keep Learning
Adam’s five observable behaviors all trace back to whether leaders know their role and act on it consistently. The School of Leadership can help you build the daily habits that turn kaizen results into lasting culture change.
Learn More About School of Leadership at https://www.gembaacademy.com/leadership
Podcast Resources
Past GA Podcast Episodes with Adam Lawrence
Adam on LinkedIn
PI Partners on LinkedIn
PI Partners
Adam on YouTube
The Wheel of Sustainability on Amazon
Sustainability System Assessment
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?
Of Adam’s five observable behaviors, which one do you see leaders struggle with most in your organization?
More from Gemba Academy Podcast: Lean Six Sigma | Toyota Kata | Productivity | Leadership
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 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.
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.