My Essay in Naida Grunden’s New Book on Lean Design – Be Lean not L.A.M.E.
I'm in Las Vegas, speaking today to close the Lean Healthcare PowerDay event. There are many great speakers, including Dr. Richard Shannon, Dr. David Munch, and my good friend and fellow author, Naida Grunden. Click on their names to listen to my prior podcasts with them. I'll be doing another podcast with Naida and her co-author Charles Hagood (of Healthcare Performance Partners) about their new book Lean-Led Hospital Design: Creating the Efficient Hospital of the Future
Their book and my upcoming Healthcare Kaizen (with Joe Swartz) are both featured on the first page of the new Productivity Press healthcare catalog, as pictured at left (click for bigger view). Naida included an essay that I wrote for her in the Appendix, under a “stories from the field” section. We agreed it would be good to repost that essay here, as well.
Be Lean, not L.A.M.E.
By Mark Graban
As simple and elegant as some lean principles can be, the reality of putting these ideas into practice can be complex and challenging. While there are well-defined and generally accepted lean principles, there is no single easy roadmap that shows you exactly how to apply these concepts and methods in a way that is guaranteed to succeed.
Because there is no single path for transforming an organization, there are different methods and approaches. Some organizations start their lean journey by conducting dozens of weeklong improvement events as a way of demonstrating that change is possible. Others eschew events and start by engaging frontline staff members in small continuous improvements (what we would call “kaizen” in the lean framework.
There are different “flavors” of lean transformation and the merits of these different approaches (and how best to combine them) can be debated respectfully amongst lean professionals (and sometimes we end the discussion by agreeing to disagree). This essay is not about criticizing any of those approaches. It is, however, a cautionary essay about avoiding approaches that violate any of these generally accepted core principles of lean management.
One challenge in the broader lean community is that any leader in any organization can do anything and then label it as “lean.” Early in their lean journeys, too many organizations try to use a single lean tool or concept in the context of their existing organizational culture. As the expression says, somebody might know “just enough about lean to be dangerous.” Some of these misapplications of lean are cases where people are trying hard, but they just don't know enough about lean yet.
A few years back, I coined an admittedly awkward acronym – L.A.M.E.
The acronym has a few different variations, including:
- Lean As Mistakenly Executed
- Lean As Misguidedly Explained
The acronym was inspired by reading a steady stream of articles that described practices as “lean,” but seemed to stray far from the true north of stated lean and Toyota Production System principles. For example, if a writer described lean as being “dehumanizing” or “turning people into robots,” it was likely a case where the writer had the completely wrong idea about lean. Or, they were describing a sad scenario where, perhaps, lean tools were being used with traditional and dysfunctional command-and-control mindsets.
The two pillars of “The Toyota Way” management philosophy are:
- Continuous Improvement
- Respect for People
For practices to be truly lean, leaders must practice both of these pillars. Former Toyota leader Gary Convis made it clear when he said that an environment for continuous improvement can “only be created where there is respect for people.” Ignoring the “respect for people” principle is what usually leads to problems described as L.A.M.E.
As author and professor Bob Emiliani writes, “Real Lean” is a “non-zero-sum principle-based management system focused on creating value for end-use customers and eliminating waste, unevenness, and unreasonableness using the scientific method.” Emiliani also emphasizes that you must practice both pillars of the Toyota Way for the benefit of all stakeholders.
Hospital leaders have, sadly, relied on layoffs and old-fashioned cost cutting for a long time, yet their efforts might get described in the news as “getting lean,” having nothing to do with the adoption of Toyota management methods. Or, hospital leaders might unfortunately use productivity improvements to directly drive layoffs, a result that is clearly a zero-sum game (the organization gains in the short-term, while the employees lose).
When organizations use lean methods to drive layoffs, this would be an example of L.A.M.E., not Real Lean. Since lean is based on Toyota's practices and philosophies, we should compare practices described as lean to that dual ideal of continuous improvement AND respect for people.
Toyota, as part of their “respect for people” philosophy, values their employees and chose to not lay off any permanent employees during even the worst of the post-financial crisis recession. Instead of taking short-term cost savings from layoffs (since, after all, they didn't need people to build cars and trucks for a period of time), Toyota instead invested in their employees by paying them for training, education, and volunteer work in the community. Taking a long-term, win-win perspective, Toyota was not being charitable, they were investing in the future success of their factories and the company as a whole. After the 2011 Japan earthquake and tsunami disaster, GM laid off employees (L.A.M.E.) while Toyota invested in them (lean), even though both companies have roughly the same amount of money in the bank.
Another way so-called lean might really be L.A.M.E. is if changes are forced on people in a top-down way. A variation on this L.A.M.E.-ness can be found when the Toyota concept of “standard work” is somehow translated into an inflexible, unchangeable “standard operating practice” that's forced on people by managers or outside experts. Taiichi Ohno, one of the creators of the Toyota Production System, wrote that people should create their own standardized work. This is quite a break from the old approach of procedures being written by the boss or an expert (an idea that traces back more than 100 years to Frederick Taylor). A truly lean environment is one where every employee has a voice in defining their standardized process in a way that best meets customer (patient) needs. Additionally, a truly lean environment is one where everybody has a voice in improving the way work is done.
Look, for example, at the use of checklists to prevent surgical errors or central line infections, as demonstrated and advocated by Dr. Atul Gawande, Dr. Peter Pronovost, and the World Health Organization. Similar work was pioneered by Dr. Richard Shannon using Toyota and lean methods as the model. The effective use of checklists has been demonstrated to virtually eliminate central line infections, but this success is characterized as a combination of the tool (the checklist or standardized work) and culture (how it was created and used). Checklists, as a close parallel to standardized work, can utilized in a way that demonstrates respect for people or, unfortunately, in a way that does not.
Checklists might be “L.A.M.E” (or it's close equivalent) if they are forced on physicians by senior leaders. The lean way would be to engage physicians and other team members in the creation of their own checklists. I know one commercial airline pilot whose consulting group teaches hospitals how to guide people through the process of writing their own checklists. Not only does this demonstrate respect for people, it's more effective because people have a greater sense of ownership over something they have created. My pilot friend complains that a competing consulting firm will basically sell a hospital a pre-written checklist. It might seem like a reasonable time saver to not reinvent the wheel, but how do you think an off-the-shelf checklist that's forced on people is likely to be received? Which approach is more likely to have clinicians and caregivers fully engaged in continuous quality and patient safety improvement?
Another example of L.A.M.E. is the use of lean tools to address things that aren't the most pressing problems for patients or staff members. It has been demonstrated that a truly lean environment can improve patient outcomes and quality, while reducing length of stay and creating a calmer, more fulfilling workplace for healthcare professionals. Lean methods should be used to solve important problems, of which hospitals have many.
One news story, from a few years back, featured complaints from nurses who said they were trying to engage their leaders in improving patient safety, yet were having their nurses' station micromanaged by managers and a central lean department. The nurses were told they could only have two pens and two pencils at their desk, likely being told that anything more was “waste.” It's inexcusable to focus lean “5S” practices on something as insignificant and inexpensive as a few pens, while patients are being harmed due to preventable falls and medication errors. This example illustrates the use of a tool, done in a top-down way, that “solves” something that wasn't a big problem to begin with – a perfect illustration of L.A.M.E. not lean. Instead of thinking “what lean tools should we use?” the question should be “what problems do we need to solve?”
Another indicator of L.A.M.E. would be cases where “hands-off” senior leaders think that lean is just a method that can be delegated to a quality department or that lean methods only apply to front-line staff. Impressive and sustainable lean results come from organizations where the CEO and leaders at all levels embrace lean as a way of managing and a way of guiding daily decisions and improvement activities. Organizations like ThedaCare and Virginia Mason Medical Center have transformed their culture because lean wasn't just a set of tools, nor was it just a bunch of projects.
As lean becomes more popular in healthcare, there's a risk that the term becomes a buzzword and a marketing tool without much depth behind it. At this stage, I would bet most healthcare architects and construction companies would answer “yes” if asked by a client or owner “do you utilize lean design and construction methods?” I've heard complaints from some hospitals that their architects could throw around the buzzwords, but then utilized the same old traditional design process. At the same time, I've heard an architect rightfully complain that some hospitals want them to design a “magically lean building,” something that's not possible without the right effort from the hospital. As with checklists, lean design has to be used in the right way – keeping “respect for people” at the forefront.
After the publication of this book, we will likely have reports of “L.A.M.E. design” instead of truly “lean design.” This won't be the fault of this book's authors, as those who read this book are far more likely to understand real lean than those who just hear the phrase. Lean design has to engage front-line staff to fully understand how they work and what they need to provide the best patient care. Lean design must also include patients and families within the boundaries of “respect for people,” involving them in the design process, as well. Lean design must be an iterative process (using the lean approach of Plan-Do-Study-Adjust) and the space and workflow design must utilize lean principles, such as point-of-use inventory, minimized walking distances (for staff and patients), and having as close to “single-piece flow” as possible.
Can we absolutely determine of something is lean or L.A.M.E.? There are some clear-cut cases where the approach being described as lean violates a core principle or belief of the Toyota-based lean approach. There are times, however, when it is a judgment call based on experience and there's room for disagreement. When is something L.A.M.E.? Repurposing a quote from the late U.S. Supreme Court Justice Potter Stewart, “I know it when I see it.”
 Liker, Jeffrey K, The Toyota Way, xi.
 Emiliani, Bob, Moving Forward Faster, 5.
 Ohno, Taiichi, Toyota Production System: Beyond Large-Scale Production, 21.