When Everyone Is Improving, Who Is Improving the System?

When Everyone Is Improving, Who Is Improving the System?

Why more Kaizen activity doesn’t necessarily mean better organizational performance.

Some years ago, I was invited to observe a Kaizen event at a manufacturing company.

We had received relatively little information beforehand. I was curious to see how they approached continuous improvement and what we might learn from their experience.

What I found was unexpected.

Practically the entire organization was participating in Kaizen events simultaneously.

Different departments. Different teams. Different problems.

There was energy everywhere.

People were discussing ideas, analyzing their work, and looking for ways to improve it.

At first glance, it was an impressive display of commitment.

But as the visit progressed, I began noticing something else.

The teams appeared to have considerable freedom to pursue their own improvements, yet the connections between those efforts were not always clear.

And I found myself wondering:

When everyone is improving something, who is making sure we’re improving the system?

The Problem With Local Success

There is nothing inherently wrong with allowing teams to identify and solve their own problems.

Quite the opposite.

One of the fundamental purposes of TPS is to develop people’s ability to recognize problems, understand their causes, and improve their work.

But autonomy and independence are not the same thing.

Every department operates within a larger system, even when its performance is measured separately.

Production may focus on productivity.

Maintenance may focus on equipment availability.

Logistics may focus on material movement.

Quality may focus on defects.

Each objective makes sense within its own context.

But an improvement that benefits one department does not automatically benefit the organization.

Increasing production output may create excess inventory.

Reducing material handling costs may increase waiting time elsewhere.

Improving departmental productivity may simply transfer work to another team.

And reducing a local expense may increase the total cost of delivering value to the customer.

None of these outcomes is inevitable.

But all are possible when we evaluate improvements only within the boundaries of the department that implements them.

Every department can hit its target while the system misses its purpose.

This is one of the most dangerous illusions in organizational management.

Not because people are doing something wrong.

But because they may be doing exactly what the system encourages them to do.

When Problems Become Requests for Solutions

During our visit, word spread that we were there.

People from other teams began approaching us, hoping we could help them with their Kaizen activities.

Their enthusiasm was understandable.

But several conversations followed a similar pattern.

Someone would describe a problem they were experiencing and ask what we thought they should do.

Often, what they described was a symptom rather than an established root cause.

And sometimes, the solution they hoped for involved automation.

I have nothing against automation.

Properly applied, it can improve safety, consistency, quality, and productivity.

But technology cannot compensate for a problem we have not understood.

If a process produces unnecessary work, automating it may simply allow us to perform that unnecessary work faster.

If a process generates defects, increasing its speed without addressing their causes may only increase the rate at which defects are produced.

And if a process is poorly connected to the rest of the operation, automating it may make those disconnections harder to correct.

Automating waste doesn’t eliminate waste. It may simply make us produce it faster.

Before asking how to automate something, we should understand why we are doing it, what value it creates, and whether the process itself needs to change.

The same principle applies to any proposed solution.

We should not confuse recognizing a symptom with understanding a problem.

Nor should we confuse finding an answer with developing the ability to solve problems.

The Expert Trap

Those conversations also reminded me of something I have encountered throughout my career.

When people know that someone has experience with TPS, they sometimes expect that person to provide the answer.

Describe the problem.

Ask the expert.

Implement the recommendation.

Move on.

It sounds efficient.

But what happens the next time a similar problem appears?

If the team has learned only what to do, it may need the expert again.

If the team has learned how to think through the problem, it has developed a capability that remains after the expert leaves.

That distinction matters.

Experience should help us ask better questions, not just find answers faster.

A good coach doesn’t need to prove that they know more than the people they are helping.

Their contribution is to help those people see what they couldn’t see before.

What is actually happening?

What should be happening?

What evidence supports our understanding?

What are we assuming?

What would we expect to observe if our explanation were correct?

These questions may not produce an immediate solution.

But they create the conditions for learning.

And learning is what allows continuous improvement to continue without depending on the same expert forever.

Who Connects the Improvements?

As I observed the different activities, my concern gradually shifted.

It was no longer primarily about how individual teams were solving their problems.

It was about how their efforts connected.

Were the teams working toward a shared understanding of the organization’s most important challenges?

Did they understand how changes in their areas could affect others?

Were they improving individual performance indicators or addressing problems that mattered to the entire value stream?

And who was helping them recognize those differences?

Our visit was limited. I cannot say what results the company eventually achieved, nor whether the coordination mechanisms we did not observe existed elsewhere.

But the experience raised questions that apply far beyond that particular organization.

Because a company is not simply a collection of departments.

It is a system of interdependent activities.

And customers do not experience departmental performance indicators.

They experience the result of the entire system.

A department may celebrate reducing its processing time while the customer still waits just as long.

Another may report lower costs while the organization spends more elsewhere.

A third may increase output without improving the flow of products to the customer.

All three improvements may be real within their own boundaries.

But their contribution to the whole remains uncertain.

The sum of local improvements is not necessarily an improvement of the whole.

Alignment Is Not Centralization

This does not mean that every Kaizen must be selected, approved, and directed by senior management.

That would create another problem.

If people need permission to think, experiment, and improve their own work, we have replaced autonomy with dependence.

But if every team chooses its direction without understanding the larger system, we risk replacing alignment with fragmentation.

The challenge is to develop both.

People should have the capability and authority to improve their work.

And they should understand how their work contributes to a shared purpose.

That requires leadership to do more than encourage Kaizen.

Leadership must help make the direction visible.

Which problems matter most?

Where is the system struggling to deliver value?

What trade-offs are we willing to make?

How do we recognize when a local improvement creates a problem elsewhere?

And how will we learn whether our changes actually improved the whole?

These are not questions that can be delegated entirely to individual Kaizen teams.

They are part of the responsibility of managing the system.

Leadership does not need to own every solution.

But it cannot abdicate responsibility for the direction in which those solutions take the organization.

When Activity Looks Like Progress

One reason this problem can be difficult to recognize is that Kaizen activity is highly visible.

We can count events.

We can count suggestions.

We can count completed actions.

We can display before-and-after photographs.

We can celebrate improvements and turn performance indicators green.

And none of those things is necessarily wrong.

The danger appears when those measures become substitutes for understanding whether the system is actually getting better.

A growing number of Kaizen events may indicate increasing engagement.

Or it may simply indicate increasing activity.

More completed actions may reflect meaningful progress.

Or they may reflect our ability to close action items.

Green departmental indicators may represent genuine improvement.

Or they may conceal problems that remain between departments.

The numbers cannot tell us which interpretation is correct without understanding the reality behind them.

Measurement should help us see.

Not tell us what to chase.

The same applies to Kaizen.

Its purpose is not to produce more Kaizen.

Its purpose is to improve the work, develop people, and strengthen the system’s ability to deliver value.

Improving Together

I still remember the enthusiasm I saw during that visit.

And I don’t want to diminish it.

People willing to question their work and invest effort in improving it are an important part of any successful transformation.

But enthusiasm alone cannot provide direction.

Neither can the number of improvement projects.

And neither can the individual success of every department.

Continuous improvement needs people who can think independently while understanding that their work is interdependent.

It needs leaders who establish direction without prescribing every answer.

It needs measurements that reveal the condition of the system rather than merely rewarding local performance.

And it needs the humility to recognize that an improvement may look successful from one perspective while creating difficulties from another.

Perhaps the most important question is not how many people are participating in Kaizen.

Nor how many improvements have been completed.

It is whether those improvements are helping the organization become more capable of delivering value, solving problems, and learning together.

The goal is not to have everyone improving something.

The goal is to have everyone contributing to improving the whole.