Here's a pattern that plays out in organizations around the world. Year one: excitement. A consulting engagement, a wave of kaizen events, visible wins. The manufacturing floor gets 5S'd. The hospital unit starts huddles. Leaders get trained. Year two and three: momentum. More events, more trained facilitators, maybe a deployment to other sites. Year four: the curve flattens. Year five: people start saying "flavor of the month" in the hallway, and nobody corrects them.

A Cardiff University study tracked exactly this trajectory. Most organizations that launch Lean see an initial improvement from the first workshop, then regress -- sometimes all the way back to the starting point. Even the better-performing organizations tend to plateau at "we can maintain standards" without ever reaching sustainable daily improvement. Only a small minority build the kind of culture where teams improve their processes continuously, on their own, without being prompted by an event or a consultant.

The question isn't why some organizations fail at Lean. The question is why organizations that have clearly invested -- years of training, dedicated facilitators, certified change agents, senior sponsorship -- still stall.

Four practitioners who've lived this problem from different angles converge on the same diagnosis: the stall isn't a methodology problem. It's a behavioral infrastructure problem. They built the tools. They missed the habits.

Nine Years of Effort, Three Gold Sites

Sandro Casagrande has spent more than 20 years building and evolving the Electrolux Manufacturing System (EMS) across 34 factories on multiple continents. In a recent KaiNexus webinar, he described a moment of reckoning that came nine years into the program.

Electrolux had done everything the playbook calls for. They trained change agents. They cascaded knowledge from external experts to internal coordinators to team leaders. They built a site certification process with levels from bronze to platinum. They ran master class events -- structured kaizen weeks focused on specific tools. They developed leader standard work templates. They deployed across every factory in the group.

After nine years of this sustained effort, only three sites had reached gold certification. One had reached platinum. The rest were stuck at lower levels despite receiving the same training, the same tools, the same support.

The conclusion Electrolux reached was blunt: they had spent nine years investing in methodology and tools while underinvesting in the thing that actually determined whether any of it would stick -- the specific behaviors of leaders when they interact with their teams. In the sites where leaders coached well, followed routines consistently, and responded to problems with curiosity rather than blame, the system progressed. In the sites where leaders went through the motions of the tools without the supporting behaviors, the certification level told the story.

This wasn't a mystery that required new theory. It was a pattern hiding in plain sight. The tools were the same everywhere. The training was the same. The variable was leadership behavior -- and they hadn't treated it as something that could be systematically designed, practiced, and reinforced.

Seventy Percent of Organizational Change Fails. The Survivors Know Why.

Lynn Kelley spent her career leading change across Textron (32 countries, businesses ranging from Bell Helicopter to Cessna Aircraft to EZGO Golf Cars), Union Pacific Railroad (42,000 employees), and a stint rolling out TQM in French and German auto plants. She's been on both sides of the failure rate.

In a KaiNexus webinar on sustaining change, she shared a stat that frames the problem: research consistently puts the failure rate of organizational change between 50% and 70%. She's quick to note the number is debated, but even the generous end -- 50% -- means half of all the training, tooling, and energy organizations pour into change initiatives produces nothing lasting.

Lynn's insight from decades of surviving in this failure zone is that the seeds of failure are detectable within the first month. Not by the end of the first year. The first month. There are enough small signals -- leadership attention drifting, follow-through breaking down, the neutral majority reading the room and deciding not to invest -- that you can predict the outcome almost immediately.

She describes the adoption dynamics using a model that anyone who's tried to lead change will recognize: in any group, roughly 20% will accept the change, 60% will be neutral, and 20% will resist. The mistake most organizations make is rolling the change out to everyone simultaneously. The 20% who resist have the loudest voices. They pull the neutral 60% toward them. By the time leadership notices, the narrative has already hardened: "this is just another flavor of the month."

Lynn's fix, refined over decades and codified in the book Change Questions (co-authored with John Shook), is structural: pilot with the willing 20% first, get the bugs out, publicize their early wins, and create what she calls "fear of missing out" in the neutral group. The neutrals start asking why the pilot group is getting extra resources and attention. Now you have momentum going in the right direction instead of fighting a narrative that's already set.

The parallel to Electrolux's experience is exact. Electrolux deployed methodology globally and evenly. Some sites thrived because they happened to have leaders whose behaviors supported the system. Other sites received the same investment and stalled, because the leaders' behaviors didn't match. Neither Lynn nor Sandro is saying the tools don't matter. They're saying the tools are table stakes. The differentiator is whether leadership behaviors are deliberately designed and sustained -- or left to chance.

The Trust Floor Nobody Measures

Colleen Soppelsa, a continuous improvement leader who has worked at Toyota, GE Aviation, and L3 Harris Technologies, pushes the diagnosis one level deeper. Before you can even talk about leadership behaviors and habit design, she argues, there's a precondition most organizations skip: trust.

During her Toyota onboarding in the early 2000s, Colleen asked a sensei why Western organizations struggle with Lean. He went to the whiteboard and wrote a Japanese character meaning cancer. His point: the internal competition within organizations -- ego, insecurity, departments optimizing against each other -- acts like cancer cells consuming healthy ones.

Over 15 years of practice since, Colleeen has developed a framework for assessing organizational trust using the Great Place to Work research model. She looks at five dimensions -- credibility, respect, fairness, camaraderie, and pride -- and maps specific failure symptoms to each. Poor strategy deployment is a respect problem (people don't understand how their work connects to the organization's direction). Chronic firefighting is a pride problem (the organization hasn't cared enough about the work to standardize it). High turnover is a fairness symptom.

Her provocation: organizations should measure these trust dimensions before launching a Lean transformation, and below a certain threshold, attempting the transformation is premature. The tools won't stick because the relational foundation isn't there. You're planting seeds in concrete.

This adds a layer to the Electrolux story. The sites that progressed to gold and platinum likely had functional trust relationships between leaders and teams. The sites that stalled despite identical training likely had trust deficits that no amount of kaizen methodology could overcome. The tool deployment was equal. The trust wasn't.

Designing Habits Instead of Running Programs

Once you accept that the stall is a behavior problem -- and that the behavior problem may sit on top of a trust problem -- the question becomes practical: how do you systematically build the leadership behaviors that make improvement sustainable?

This is where Greg Jacobson and Morgan Wright of KaiNexus land. In a three-part webinar series on habit science (see part 1)applied to continuous improvement, they make the case that about 50% of daily behavior is habitual -- performed automatically, without deliberate decision-making. The implication is direct: if you want improvement behaviors to persist, you need to make them habitual rather than relying on motivation, which fluctuates day to day.

They draw on BJ Fogg's behavior model (the intersection of motivation, ability, and a prompt), James Clear's habit loop (cue, routine, reward), and Clear's distinction between identity and goals. That last one deserves attention because it reframes a problem most CI leaders have felt but haven't named.

There's a meaningful difference between "we're trying to huddle every morning" and "we're the kind of organization that huddles." The first is a goal. Goals can be skipped when motivation is low, when the week is busy, when a leader is traveling. The second is an identity. Identities guide decisions automatically. You don't debate whether to huddle any more than you debate whether to answer the phone. It's who you are.

Applied at the organizational level: "We're trying to increase improvement participation by 20%" is a goal with an endpoint. Once you hit it (or don't), the energy dissipates. "We're the kind of organization where everyone improves their work" is an identity that persists. It shapes hundreds of micro-decisions every week -- whether a leader walks past a problem or stops, whether a manager responds to an idea with enthusiasm or indifference, whether a new hire is asked to improve their onboarding process on day one.

Electrolux arrived at the same insight independently. Casa Grande describes wanting to create "organizational habits" -- not just individual compliance with tools, but shared routines that become part of who the organization is. He found Charles Duhigg's habit loop (cue, routine, reward) and Mike Rother's Toyota Kata (a structured coaching routine designed for daily repetition), then layered in the neuroscience concept of neuroplasticity -- the brain's ability to form new pathways through deliberate, repeated practice. The message to Electrolux leaders: the reason you have to practice these routines daily, not just learn them once, is because that's literally how the brain works. Repetition builds the neural pathway. Skip the repetition and the old pathway reasserts itself.

Interlocking Loops: Why Isolated Habits Don't Scale

Greg and Morgan extend the habit model with a concept that solves a problem most CI leaders recognize instinctively but struggle to address: different roles need different habit loops, and those loops need to reinforce each other.

They describe four personas that exist in nearly every CI organization: the executive, the CI coach, the middle manager/leader, and the frontline worker. Each has a distinct cue-routine-reward loop. The executive's cue might be a scheduled 15-minute review with their CI coach; their routine is reviewing metrics and commenting on improvements; their reward is seeing the trajectory of the program. The frontline worker's cue is the daily huddle; their routine is sharing an observation or updating an improvement; their reward is recognition from their leader and visible evidence that their idea is being acted on.

The key design insight: each persona's routine becomes the cue or reward for someone else. When an executive comments on an improvement in the system, that's a reward for the frontline worker who submitted it and a cue for middle managers who see that senior leadership is paying attention. When a middle manager runs the weekly huddle, that's a cue for frontline workers to prepare updates and a demonstration of commitment that the executive's routine reinforces.

When these loops are deliberately designed and aligned, they create a self-reinforcing system. When they aren't -- when the executive skips the review, when the huddle is canceled, when nobody responds to ideas -- the loops break, and every other persona's habit weakens.

This explains a pattern that puzzles many CI leaders: why removing one leader from the system can cause a disproportionate collapse. It's not because that leader was uniquely talented. It's because their routine was the cue or reward in someone else's habit loop. Remove the routine, and the connected loops lose their trigger.

What the Fix Actually Looks Like

The organizations that break through the year-five stall share a set of practices that don't show up in most Lean deployment plans:

They measure trust before deploying tools. Not with a generic engagement survey, but with specific questions about whether people feel their input is valued, whether they understand how their work connects to the strategy, and whether they believe speaking up leads to action. If the scores are below a threshold, they work on the relational foundation before layering on methodology.

They treat leadership behaviors as standard work, not personality. Electrolux codified specific leadership processes (strategy coaching, condition coaching, rapid PDCA coaching) and specific leadership behaviors (goal alignment, process focus, questioning and challenging, support and recognition). These aren't suggestions. They're the expected routine, practiced daily, with coaching and feedback -- exactly how you'd train any other standard work.

They design habit loops intentionally rather than hoping that training creates lasting change. This means defining the cue (what triggers the behavior), making the routine easy enough to do consistently (especially at first), and building in rewards that are immediate and certain. As the Electrolux team learned from behavioral researcher Aubrey Daniels: feedback is most powerful when it's positive, immediate, and certain. Positive feedback delivered four times more often than negative gradually shifts people from compliance to ownership.

They pilot before scaling. Rather than deploying a new practice across the entire organization and hoping for the best, they start with willing adopters, prove the concept, and let success create pull. The neutral majority comes aboard when they see evidence -- not when they receive a memo.

And they build the infrastructure that makes all of this visible at scale. Physical boards and spreadsheets work for a single team. They fail structurally when you're trying to sustain improvement behaviors across dozens of sites in multiple countries. When a leader in one factory can see that a team in another factory solved the same problem they're facing, that's not just knowledge transfer -- it's reinforcement that the system works. When every idea gets a response, every improvement has a visible status, and every person can trace their contribution to measured impact, the system itself becomes a habit-sustaining mechanism. The notifications are cues. The streamlined workflows reduce friction in the routine. The visible impact and recognition are the reward.

See KaiNexus in action ->

The Real Timeline

The uncomfortable truth embedded in all four of these practitioners' experiences is that the stall at year five was predictable from year one. The signals were there. Leadership behaviors were uneven. Trust was unmeasured. Habit design was absent. Training was treated as sufficient for behavior change. These aren't failures of effort or commitment. They're failures of design.

The good news is that the fix doesn't require starting over. Electrolux didn't abandon EMS. They evolved it by adding the behavioral layer they'd been missing. Lynn didn't throw out Lean methodology. She added a structured diagnostic (the change questions) that catches design failures in the first month instead of discovering them in year five. Greg and Morgan didn't invent a new improvement methodology. They applied an existing body of science -- habit design -- to the specific challenge of making improvement behaviors stick.

The common thread: stop treating the stall as an engagement problem, a motivation problem, or a training problem. Treat it as an infrastructure problem. Build the trust foundation. Design the leadership habits. Create the interlocking loops. And give the whole system a platform that makes progress visible, because visibility is what turns isolated efforts into organizational identity.

One percent better per week doesn't feel like much. Compounded over a year, it's transformative. But only if the system is designed to sustain the one percent -- not just celebrate the first event.

Related KaiNexus webinars referenced in this post:

• Unlock the Power of Leadership: The Electrolux Manufacturing System Way with Sandro Casa Grande
• No More "Flavor of the Month" Change: How to Deliver Sustainable Improvement with Lynn Kelly
• Why Trust Is the Foundation of Continuous Improvement with Colleen Soppelsa
• How to Sustain Continuous Improvement with Habit Science (Part 3) with Greg Jacobson and Morgan Wright