<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=749646578535459&amp;ev=PageView&amp;noscript=1">

Are You Really Backsliding -- or Was Continuous Improvement Never Deeply Adopted?

Posted by Mark Graban

Find me on:

Mar 30, 2026 3:30:00 AM

 

One of the most common questions in the Ask Us Anything series sounds like this:

"We were doing great with Lean, and now we are backsliding. How do we sustain this?"

That same question could be asked about Six Sigma, operational excellence, or any other improvement programs or labels.

Sometimes it is framed around metrics slipping. Sometimes it is declining idea submissions. Sometimes it is a leadership transition. But underneath the question is fear: did we lose it?

When Greg and I revisited the series, something became clear. In many of those situations, the organization was not backsliding. Continuous improvement had never been deeply adopted in the first place. You cannot sustain what was never embedded. That is not criticism. It is diagnosis (an apt word since Greg is a physician).

See more in the Ask Us Anything reflections series.

Activity Is Not Adoption

Early CI efforts often generate visible energy -- Kaizen events, training sessions, idea boards filling up, metrics improving, leadership celebrating wins. From the outside, it looks like culture change.

But if improvement depends on a few passionate champions, a specific consultant, a single executive sponsor, or extra time carved out "when possible," then it has not become part of how the organization operates. It is still a layer on top of the work.

When that layer thins -- due to budget pressure, leadership change, or competing priorities -- performance appears to slide. But what is really happening is exposure. The system is reverting to its default behaviors.

The Adoption Gap

An organization can adopt tools without adopting thinking. It can adopt language without adopting behavior. It can adopt events without adopting leadership habits.

That gap is where most "backsliding" originates. If leaders stop modeling it, the organization will stop practicing it. Not immediately, but predictably. Because culture does not run on enthusiasm. It runs on reinforcement.

When leader standard work fades, when follow-up on ideas slows, when improvement conversations disappear from daily huddles -- the system recalibrates. That is not failure. That is gravity.

The Leadership Transition Test

One of the clearest indicators we discussed in the series was what happens when a key leader leaves.

If CI momentum collapses after one departure, it was personality-driven. If it holds, even imperfectly, it was system-driven. Sustainable CI survives leadership change -- not because the new leader is perfect, but because the behaviors are distributed. Daily huddles continue. Follow-up continues. Teams still expect to solve problems locally.

If everything pauses waiting for direction, adoption was not as deep as it appeared.

Slower Progress Is Not the Same as Regression

There is another pattern worth naming. Early gains are often dramatic. When waste is obvious, improvement is fast. Metrics jump. Energy builds.

But later-stage improvement is slower, harder, and more incremental. That slower pace can feel like regression. Sometimes it is actually maturation. If standards are stable, response times remain tight, and problem-solving is consistent, you are not backsliding. You are moving from visible wins to disciplined maintenance. Maintenance is less exciting, but it is more important.

The Better Question

Instead of asking "why are we backsliding," the more useful question might be: where was adoption shallow?

Was it in leadership modeling? In middle management ownership? In reinforcement systems? In performance expectations? Improvement does not fail dramatically. It erodes quietly. And that erosion usually starts where behaviors were not anchored.

Across the series, when organizations were truly sustaining CI, they had a few things in common. Leaders had defined standard work around improvement. Response time to problems was visible. Middle managers owned improvement rather than delegating it. Improvement was discussed weekly, not quarterly. Follow-up was not optional. Nothing flashy. Just consistent.

If You Are Seeing Regression, Do Not Panic

Looking back at these conversations, I am less alarmed by "backsliding" than I used to be. It is usually a signal -- that adoption was uneven, that reinforcement drifted, or that leadership modeling weakened. That is fixable.

What is harder to fix is pretending CI was deeply embedded when it was not. If you are seeing regression, diagnose before you re-launch. Ask where behaviors were not institutionalized. Sustainable continuous improvement is not about intensity. It is about depth. And depth takes longer than most organizations expect.

What has your experience been with sustaining improvement through leadership transitions or budget pressure? I would be curious to hear what held and what did not.

Topics: Leadership, Improvement Culture, Continuous Improvement

Recent Posts