GA 652 | Culture Before Technology with Hessam Vali
Gemba Academy Podcast: Lean Six Sigma | Toyota Kata | Productivity | LeadershipShow Notes
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.
In this episode you’ll learn:
What “lean is constant ticking, not occasional kicking” actually demands (2:54)
Why fixing the wrong problems leaves customers unable to see progress (7:24)
How Rapid Plant Assessment and value stream mapping work together to find constraints (10:03)
Why backsliding happens and how to catch it before it compounds (14:52)
How checklists and behavior-level metrics detect process drift faster than control charts (18:34)
Why technology without an operating system solves nothing (22:16)
What AI should and should not be trusted to do in a lean environment (27:11)
Why transformation gets worse before it gets better (30:13)
The reason firefighting organizations cannot find time for kaizen (31:40)
“You are doing firefighting because you’re not doing kaizens, because you’re not pausing, you’re not looking at it, you’re not fixing problem from the cause, and you’re not going to be out of that circle unless you change that behavior.” – Hessam Vali
Keep Learning
If Hessam’s point about finding the vital few constraints before launching improvement work resonated, the School of Lean covers the foundational tools for mapping value streams and surfacing the kinks worth fixing.
Learn More About School of Lean at gembaacademy.com/school-of-lean
Podcast Resources
Hessam on LinkedIn
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?
When your team is deep in firefighting, what does it take to carve out the time to step back and address the constraint that is feeding all those fires?
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 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.