In a new video released by the Lean Enterprise Institute, CEO John Shook talks about a “Lean transformation” model. He starts by explaining how “prescriptive implementation models” have been attractive to many organizations and “that can be effective in making a certain amount of improvement and learning” but there’s a better approach than “copying” Toyota’s tools and techniques.
Here is the video:
In the roof of the house is the “situational approach” – as the situations faced by different organizations will be different. I’d add the example of one hospital that is short on cash and might be going bankrupt in a few months versus a second hospital that has financial stability and is looking to go from “good to great” on patient safety and quality.
Shook says we need a “value-driven purpose” or a “true north.” The simple question that leads to that is “what problem are we trying to solve?”
The first of the two pillars he draws is “process improvement” (changes to the work). He says “Lean is sometimes mistaken as a process improvement program when it’s much more than that). The second pillar is “capability development” or “developing the people.” This reminds me of the two “equally important pillars” of the Toyota Way management system – “continuous improvement” and “respect for people.”
People are in the heart of the diagram, of course — the management system and the leadership behaviors. The foundation includes “basic thinking, mindsets, and assumptions.”
Shook says this model leads to a set of questions:
- What problem are we trying to solve? What is our true north?What value are we providing?
- How will we improve or change the value-creating work?
- How will we develop the people (at all levels of the organization?
- What leader behaviors and management systems are required to lead work in this new way we’re transforming?
- What basic thinking, mindsets, and assumptions underlie or define the transformation?
I agree with Shook that too many organizations have focused on copying tools. The right tool in the wrong culture can be useless or harmful. Putting an “andon cord” up is a waste of time if it’s on an assumably line where workers are afraid they will get yelled at for stopping the line (instead of being praised for putting quality first and receiving assistance in resolving the problem).
I had a chance to visit Livonia Public Schools last Thursday (the district I attended from first grade through high school graduation). Jeff Fuchs (also a Livonia product) has volunteered to help them and I’m impressed that they are focused on solving problems, as Shook described. I didn’t see half-hearted attempts at “5s-ing” the headquarters supply room. Instead, I saw an approach where Fuchs was teaching them to solve problems that mattered (such as improving the new student registration process) and people are being developed in the process. I’ll write more about this soon.
Shook concludes by saying an organization can then develop a management and leadership approach that meets the goals laid out by the true north and those questions. Are we going to travel, benchmark, and copy or have an approach that’s scientific in it’s nature?
I see hospitals being VERY willing to spend money to travel, see “best practices,” and attempt to bring them home (an attempt that often fails). I wish hospitals were also MORE willing to put in the work to figure things out themselves through PDSA and a model like Shook’s. It’s really interesting and fun to coach people through problem solving… more fun than just copying somebody. Do you think you learn more copying or figuring things out yourself?
I think we’ll have better and more effective Lean transformations, as a result. What do you think?
(hat tip to the LEI’s Lean Post site for sharing this)
About LeanBlog.org: Mark Graban is a consultant, author, and speaker in the “lean healthcare” methodology. Mark is author of the Shingo Award-winning books Lean Hospitals and Healthcare Kaizen, as well as the new Executive Guide to Healthcare Kaizen. Mark is also the VP of Innovation and Improvement Services for KaiNexus.