Not long ago, an organization told us it was dissolving its continuous improvement department. The reasoning sounded almost responsible. They had been doing continuous improvement for about two years. Everyone had been trained. People were doing the work. So the logic went: if improvement is now everyone's job, why keep a team of specialists around to do it?

Greg will admit that fifteen years ago, when he was earlier in his own journey into this work, he might have nodded along. After all, isn't the goal that everyone improves their work every day? Isn't a dedicated CI department almost an admission that improvement hasn't really taken root yet?

We understand the instinct. We just think it's wrong, and we want to explain why, because this decision gets made more often than it should, usually with the best of intentions and sometimes as a quiet way to cut costs.

The mistake hiding inside the logic

The argument for disbanding rests on a real truth: continuous improvement should be everyone's responsibility, not the property of a specialist class. We agree with that completely. An organization where improvement only happens when the CI department shows up has not built a culture. It has built a service desk.

But "everyone should improve their work" and "therefore we don't need anyone whose full-time job is improvement" do not connect the way they appear to. The conclusion smuggles in an assumption that doesn't hold: that once people are trained and active, the system runs itself.

It doesn't. No system does.

Greg spent a chunk of the last few years rethinking his own body the way you'd think about an aging machine (his own words). In his mid-forties, he ruptured an ACL playing squash, and the lesson that followed was that a body, like an organization, doesn't keep itself in shape because it was once trained well. You don't work out hard for two years and then coast for the rest of your life on the strength you built. The moment you stop adding energy, entropy takes over. A continuous improvement culture is no different. The training got people started. The training is not what keeps them going.

What we've actually seen

Here's the part that matters most, and it's the reason we feel confident saying this plainly rather than hedging.

Between the two of us, KaiNexus has worked with hundreds of organizations and spoken with many more. Across all of them, Greg cannot identify a single successful organization, the kind where ten out of ten people would look at the activity and say "yes, that's what good looks like," that operates with zero people thinking full-time about continuous improvement.

Not one.

The ratio varies. It might be one CI person per few hundred employees, or per thousand, or per two thousand. But it is never zero. The organizations that sustain improvement for years all have at least one person whose job is to keep the system healthy.

Notice what that person is not doing. They are not the one doing all the improvement. That would be the failure mode the disbanding argument is rightly reacting against. Their job is to coach, to train, to keep the standards, to make the work visible, to spread what one team learned to the teams that haven't learned it yet, and to keep adding energy to a system that will otherwise drift back toward how things used to be done.

The analogy Greg keeps coming back to is professional sports. A world-class tennis player has a coach. Often one of the best coaches available. Nobody looked at Roger Federer and concludes that because he has mastered the game, he no longer needs anyone in his corner. The coach exists precisely because mastery is not a finish line. The better you get, the more a good coach is worth.

Even Toyota keeps the experts

If the everyone-does-it-now logic held anywhere, it would hold at Toyota, the company that has been practicing this longer and more deeply than anyone. Toyota has had decades. Continuous improvement is genuinely embedded in how people there work, in a way most organizations can only aspire to.

And Toyota still maintains a central group dedicated to the Toyota Production System. They still have people whose role is total quality management. The intent of those groups is not to go do the improvement work for everyone, the frontline does that every day. The intent is to serve as master coaches, trainers, and keepers of the standard.

If the most mature improvement culture on the planet still funds the experts after seventy years, the two-year-old culture that just trained everyone is not the exception to the rule.

"This is just how we do things now"

We've heard the more sophisticated version of the disbanding argument too. It isn't always framed as cost-cutting. Sometimes it's framed as a milestone: "improvement is embedded now, it's just how we do things here."

That can be true. It's also very easy to say, and the proof is in the pudding. Mark's honest reaction when he hears it is to want to see the evidence a year later, when the numbers are in and the activity either held or quietly faded.

If a CI department is genuinely no longer needed because the work is embedded, here's the test: where did those Lean specialists go? If the organization redeployed them into leadership roles, where they can keep coaching and keep the standards alive from new positions, that's a believable story about maturity. If they were simply cut to save money, we get skeptical fast. "This is just how we do things now" and "we eliminated the people who made it how we do things" rarely turn out to be the same sentence.

The pattern this fits

This decision is one specific instance of a much broader misunderstanding, the one that treats Lean as a project with an end date rather than a long-term methodology. It's the same thinking that asks "are we done yet?" about culture change. It's the same thinking behind the organization that runs a wave of kaizen events, declares victory, and is surprised when the gains erode.

The first of Jeff Liker's fourteen Toyota Way principles is to base decisions on long-term thinking, even at the expense of short-term results. It's principle number one for a reason. Disbanding the CI team to bank a short-term cost saving is precisely the trade that principle warns against. The savings are visible this quarter. The erosion of the culture shows up slowly, over the following years, in a place no budget line tracks.

What to do instead

If you've reached the point where everyone is trained and active, congratulations, that's real progress, and it's rarer than it should be. The move at that stage is not to remove the people who got you there. It's to redefine what they do.

Shift them from doing improvement toward coaching it. Shift them from running events toward keeping standards, measuring impact, and spreading proven improvements across the organization so the same problem doesn't get re-solved in five different places. Shift them, in other words, toward exactly the work that keeps a mature culture from quietly sliding backward.

That work never finishes, because entropy never takes a year off. The day you decide you no longer need anyone tending the system is the day the system starts, slowly and invisibly, to come apart.

You wouldn't fire the coach because the team finally learned to win. Don't disband the CI team because the organization finally learned to improve.

See KaiNexus in action and see how teams keep improvement work visible, coached, and spreading across the organization, long after the training is done.