Lean has a decades-long track record of producing real results across industries. Hospitals have used it to reduce patient harm and eliminate hours of wasted time per shift. Manufacturers have used it to cut defects, shorten lead times, and improve safety. Service organizations have used it to fix broken processes that everyone had learned to work around.

Lean has also been, unfortunately, declared a failure by a long list of organizations that tried it, gave up, and moved on to the next thing.

Both of these things are true, and they're not contradictory. Lean works. But not every organization that adopts Lean gets the results it promises. The gap between those two outcomes is almost always a leadership problem, not a methodology problem.

The Pattern

The failure pattern is remarkably consistent. I've seen it play out in hospitals, factories, and offices over more than two decades. It goes something like this:

An organization decides to "get Lean." Maybe there's a financial crisis. Maybe a new executive read a book or attended a conference. Maybe a competitor's results are making the board nervous. Whatever the trigger, the decision gets made, and the rollout begins.

Training happens. A few kaizen events get scheduled. Someone implements 5S in a department. A consultant draws a value stream map. Visual boards go up on a few walls.

And then nothing changes. Not really. Leaders still manage the same way they always have. Decisions still flow top-down. Problems still get met with blame. The people doing the work watch all of this and think:

"Here we go again."

Within a year or two, enthusiasm fades. The boards stop getting updated. The events stop getting scheduled. And someone in a leadership meeting says the words that end it:

"We tried Lean, and it didn't work here."

But what they tried wasn't Lean. Not really.

L.A.M.E.: Lean As Misguidedly Executed

I've sometimes used the term L.A.M.E. -- Lean As Misguidedly Executed -- to describe what happens when organizations adopt Lean's tools but ignore its management system and philosophy. It's a pattern with deep roots. The 1994 book "Why TQM Fails and What to Do About It" documented nearly identical failure modes in the Total Quality Management movement. Two decades later, the same mistakes keep showing up under a different label.

L.A.M.E. isn't hard to spot. Here are the telltale signs.

Failure Mode 1: Tools Without the Management System

The most common failure is treating Lean as a toolkit -- a collection of methods you can deploy selectively to fix specific problems. Run a kaizen event here, implement kanban there, do some 5 Whys when something goes wrong.

The problem isn't with any of those tools. They're all useful. The problem is that tools applied in isolation, without the management system that connects them, produce temporary results. A kaizen event generates excitement and real improvements during the event week. But without leader standard work to sustain them, without daily huddles to monitor the process, without a system for tracking follow-up actions -- the gains erode within months.

As the misperceptions table in Lean Hospitals puts it: "Lean is an integrated and holistic system. The tools are most effective when in the context of the philosophy and management practices." Gary Kaplan, MD, the CEO of Virginia Mason Medical Center, said it more bluntly:

"If your leaders think this is just another improvement method, a program or initiative, you'll never achieve the long-term success this management method offers."

Failure Mode 2: Leading with Cost-Cutting

Lean reduces costs. That's true, and it's one of the reasons executives get excited about it. But cost reduction in a Lean system is a result, not a starting point. It happens as a consequence of reducing waste, improving flow, and building quality into processes.

When leadership's primary interest in Lean is cutting costs -- and especially when Lean becomes associated with layoffs, understaffing, and doing more with less -- they've taken a wrong turn. That's not Lean. That's traditional cost management wearing a Lean label.

Lean hospitals focus on reducing waste, not cutting costs. The distinction matters. Traditional cost-cutting slashes budgets, headcount, and services -- and it creates side effects: demoralized staff, hidden problems, and processes that get worse under pressure. Waste reduction improves the process itself. People spend less time searching for supplies, waiting for information, reworking errors, and doing tasks that add no value. Costs come down because the work gets better, not because people are squeezed harder.

Nobody at Toyota teaches that Lean should be used to drive layoffs. In fact, making layoffs the consequence of improvement is one of the fastest ways to kill an improvement culture. Why would anyone surface a problem or suggest a better way of doing things if the result might be that they or their colleagues lose their jobs?

Failure Mode 3: Leaders Who Don't Change

This is the one that underpins all the others. Organizations expect frontline staff to adopt new behaviors -- surface problems, run experiments, follow standard work, participate in huddles -- while leadership continues to manage the same way they always have.

Lean requires a fundamentally different leadership posture. Instead of giving orders, leaders ask questions. Instead of managing from reports and dashboards, they go to the gemba to see the work firsthand. Instead of reacting to problems with blame, they respond with curiosity and support.

When leaders skip this shift, employees recognize it instantly. They've seen initiatives come and go before. They know the difference between genuine commitment and a flavor-of-the-month program. The typical employee reaction -- skepticism, reluctance, waiting it out -- isn't "resistance to change." It's a rational response to years of experience with leadership initiatives that didn't last.

As Dr. Deming taught, quality starts in the boardroom. If the senior leaders aren't willing to change how they lead, no amount of training, tools, or kaizen events will produce lasting results.

Failure Mode 4: Copying Without Understanding

When Western automakers first studied Toyota, they focused on the visible, easy-to-copy practices: kanban cards, andon cords, standardized work charts on the wall. They replicated what they could see. What they missed was everything that made those practices work -- the coaching routines, the problem-solving culture, the decades of accumulated learning that gave each tool its context.

This mistake repeats in every industry. A hospital visits another hospital that's having success with Lean, copies their huddle board format and daily meeting structure, and wonders why it doesn't work the same way. The answer is that the visible tools are the tip of the iceberg. What makes them effective is the management system, the leadership behaviors, and the culture underneath.

Lean requires thinking, creativity, and experimentation -- not replication. You can learn from what other organizations have done, but you have to adapt it to your own context and build the understanding from the inside out.

Failure Mode 5: Treating Lean as a Finite Project

"We're implementing Lean" implies a start date and an end date. But Lean isn't a project. It's a management system you practice and refine over years. There is no point at which you're "done."

Organizations that treat Lean as a bounded initiative -- a two-year transformation plan, a series of improvement projects, a training program with a graduation date -- tend to see results plateau or erode once the initiative officially ends. The improvement work stops because nobody designed the infrastructure to keep it going as part of how the organization operates day to day.

The organizations that get lasting results build daily management systems -- tiered huddles, gemba walks, leader standard work, systems for capturing and tracking improvements. These routines make improvement part of the operating rhythm, not something layered on top of it.

The TQM Parallel

If any of this sounds familiar, it should. The Total Quality Management movement of the late 1980s and 1990s went through the exact same cycle. Organizations adopted TQM with great enthusiasm, implemented it superficially, failed to get the expected results, and declared it a fad.

TQM wasn't a fad. Its principles were sound. But as the authors of "Why TQM Fails" wrote in 1994: employees doubted the company's commitment, training didn't start at the top, management priorities remained focused on short-term financial results, and people reasonably concluded it was just another program of the month.

Swap "TQM" for "Lean" in any of those sentences and you have a description of what's happening in organizations right now. The failure mode hasn't changed. Only the label has.

What Actually Works

If the failure pattern is consistent, so is the success pattern. Organizations that sustain Lean over years share several characteristics:

Leaders practice Lean themselves. They don't just sponsor it or fund it. They do their own improvement work, go to the gemba regularly, and share what they're learning. When executives model the behavior they're asking of others, it signals that this isn't optional and it isn't temporary.

The management system is built first. Before scaling tools and events, successful organizations build the daily management infrastructure: huddles, visual boards, escalation paths, leader standard work. This infrastructure is what sustains results between events and keeps problems from hiding until they become crises.

Respect for people is practiced, not just stated. This means engaging frontline workers in improving their own processes, responding to problems as system failures rather than individual blame, and creating the psychological safety that allows people to be honest about what isn't working. Without respect for people, continuous improvement is just management telling staff to work differently.

Improvements are tracked and made visible. Organizations that sustain Lean have a system for capturing, managing, and measuring improvements across the enterprise. This does three things: it ensures that good ideas don't disappear into a void, it gives leaders evidence of what's working, and it makes it possible to spread successful improvements to other teams and facilities instead of solving the same problems in parallel.

The focus is on waste reduction, not cost reduction. Successful Lean organizations lead with safety, quality, and flow. When processes improve -- when errors drop, wait times shrink, and people spend less time on tasks that add no value -- costs follow. Leading with cost targets produces cost-cutting. Leading with waste reduction produces better processes that happen to cost less.

It's Not Lean That Failed

When an organization says "Lean didn't work here," it's worth asking what they actually did. Did leadership change how they manage? Did they build the daily management infrastructure? Did they create the conditions for frontline workers to participate honestly and safely? Did they track and sustain their improvements?

In most cases, the answer to several of those questions is no. And that's not a Lean failure. That's leaders applying Lean's tools while keeping the old management system in place -- and getting predictably disappointing results.

Lean works. The evidence across industries and decades is clear. But it only works when leadership commits to changing themselves first, building the management system to sustain it, and treating it as how the organization operates -- not as a program with an expiration date.

See KaiNexus in action -->