Kaizen Is More Than a Problem-Solving Method
Kaizen is more than a problem-solving method. It is a continuous practice that connects standards, experimentation, learning, participation, and people development. This article explores why methods, events, metrics, and specialists can support Kaizen, but cannot replace an organization’s everyday capability to understand and improve its work.
THINKING DIFFERENTLYTPS FUNDAMENTALSPROBLEM SOLVING
Kaizen Is More Than a Problem-Solving Method
Kaizen often appears in presentations, training programs, and transformation plans as though it were a problem-solving method.
People speak of “applying Kaizen,” “doing a Kaizen,” or “using the Kaizen methodology” to correct a deviation, reduce waste, or improve a metric.
The intention may be right.
But the language reveals an important misunderstanding.
Kaizen is not a specific problem-solving method.
It is not a single sequence of steps.
It is not a form.
It is not a multi-day event.
Nor is it a tool selected from a list whenever a difficulty appears.
Kaizen is the continuous practice of improving a condition through learning, people’s participation, and the constant review of how work is performed.
Problem-solving methods can support Kaizen.
But they are not Kaizen by themselves.
A Word That Became a Tool
In many organizations, Kaizen was introduced as part of a collection of Lean tools.
5S.
Kanban.
Poka-yoke.
Value stream mapping.
Standardized work.
Kaizen.
When it is placed in a list like this, it is easy to interpret it as just another technique.
Then come “Kaizen events,” “Kaizen weeks,” “Kaizen projects,” and forms for recording improvement ideas.
Little by little, a way of thinking and acting is reduced to a scheduled activity.
The organization stops asking how it can improve every day and begins asking when the next event will take place.
It stops observing how people learn and begins using the number of completed Kaizen improvements as the main evidence that improvement is occurring.
It stops questioning the system and focuses its attention on completing records and forms.
The term remains.
But its meaning becomes smaller.
Solving a Problem Is Not Always Kaizen
An organization can solve a problem without developing Kaizen.
It can hire an external specialist.
It can assign the problem to a technical team.
It can use statistical analysis, simulation, automation, or a major investment.
It can eliminate a failure and achieve an excellent result.
The problem was solved.
But if the solution remains completely separated from the people who perform the work, if the knowledge is concentrated among a few experts, if the organization develops no new capabilities, and if the improvement depends on an outsider returning to intervene, the result hardly strengthens a mature practice of Kaizen.
Participation does not mean that operators must solve every problem on their own.
Many conditions require technical knowledge, specialized analysis, investment, or collaboration across different functions.
What matters is that the solution remain connected to the genba, that knowledge can be shared, and that the organization increases its ability to face the next challenge.
Kaizen is not defined only by the fact that something changed.
How the change was produced also matters.
Did people learn to observe more effectively?
Did they develop a deeper understanding of their process?
Did they participate in pursuing a better condition?
Was the new knowledge incorporated into the standard?
Did the organization increase its ability to face the next problem?
A solution can improve performance.
Kaizen must also improve people’s ability to continue improving.
Kaizen Does Not Mean Just Any Change
At the other extreme, some organizations call every modification Kaizen.
Moving a table.
Changing a label.
Buying a tool.
Reorganizing a file.
Removing a step.
Installing a sign.
All of these actions could be improvements.
They could also fail to improve anything.
Moving a table without understanding the flow may create additional travel.
Changing a label does not correct a confusing system.
Buying a tool may increase inventory without addressing the original need.
Removing a step may simply transfer the work to someone else.
A modification does not automatically become an improvement simply because it is small, quick, or inexpensive.
Kaizen requires direction.
There must be a current condition that we seek to understand and a better condition toward which we are trying to move.
Without purpose, any change can look like progress.
But not every movement creates learning.
The Role of Problem-Solving Methods
Problem-solving methods are structures that help us think.
They allow us to define a gap.
Observe the current condition.
Investigate causes.
Establish a target.
Develop countermeasures.
Test ideas.
Verify results.
Adjust and standardize.
Depending on the organization and the type of problem, these structures can take different forms: PDCA, A3, the eight-step process, root cause analysis, Toyota Kata, DMAIC, and other approaches.
Each organizes reasoning in a particular way.
Each can be useful under certain conditions.
But none of them contains the entire practice of Kaizen by itself.
A team may complete an A3 correctly without developing a daily habit of improvement.
It may follow every stage of PDCA while treating the work as an isolated project.
It may execute DMAIC, achieve a significant financial benefit, and then return to a culture in which only specialists solve problems.
The method helps guide thinking.
Kaizen defines an ongoing relationship with work.
The Risk of Confusing the Map with the Journey
A method is like a map.
It helps organize the route.
It shows reference points.
It prevents us from jumping directly from a symptom to a solution.
It reminds us to observe, verify, and learn.
But having a map does not mean that the journey has been made.
An organization can teach problem-solving formats without creating the conditions for people to use them.
It can demand root cause analysis while punishing those who reveal a failure.
It can ask for experimentation while expecting every test to succeed immediately.
It can promote PDCA while imposing solutions before the current condition has been understood.
It can speak about Kaizen while preventing operators from changing anything in their own work.
In those cases, the method exists.
The practice does not.
Kaizen requires more than a sequence of steps.
It requires time to observe.
Safety to reveal problems.
Leadership that asks questions.
Standards that can be challenged.
Space to experiment.
And an organization willing to learn from results that do not confirm its expectations.
Kaizen Can Begin Before an Obvious Problem Exists
Problem solving usually begins with a gap:
Something is not working as it should.
There is a difference between the expected result and the actual result.
Kaizen can emerge from that gap, but it does not always depend on an obvious failure.
A process may be meeting its objectives and still be difficult, exhausting, unsafe, or unnecessarily complex.
An activity may produce the required quality while depending on one person’s memory.
A flow may deliver on time while maintaining excessive inventory as protection.
A team may achieve its target while people silently compensate for weaknesses in the system.
We do not always need to wait until an indicator turns red.
We can also improve because we see a possibility.
Because we want to reduce burden.
Because we find a simpler way.
Because we can make it easier for someone new to learn.
Because we want to move closer to an ideal condition.
Problem solving responds to a gap.
Kaizen can also create a gap by imagining a better condition that does not yet exist.
Continuous Improvement Does Not Mean Changing All the Time
Saying that Kaizen is continuous does not mean modifying the process without rest.
A system needs stability.
People need a known way to perform the work.
Without a defined condition, it becomes difficult to know whether a change actually produced an improvement.
That is why standardized work and Kaizen are not opposites.
The standard represents the best-known way at this moment.
Kaizen questions whether that way can be improved.
When a test produces a superior and sustainable result, the learning is incorporated into the standard.
That new standard then becomes the starting point for further learning.
The sequence is not:
Standard or improvement.
It is:
Standard → observation → experimentation → learning → new standard
The continuity of Kaizen is not found in constantly changing things.
It is found in never considering any way of working to be final.
An Event Can Support Kaizen, but It Cannot Replace It
Kaizen events can be useful.
They concentrate attention.
They bring together people from different functions.
They allow a process to be observed intensely.
They accelerate decisions.
They create protected time for experimentation.
The problem appears when the event becomes the only way improvement happens.
For one week, the team questions everything.
Then, for months, it waits for instructions.
During the event, leaders listen to operators.
When it ends, decisions are once again made far from the work.
For a few days, ideas are tested quickly.
Afterward, any modification requires multiple approvals.
The event produced changes.
But it did not necessarily create a culture of Kaizen.
An event should strengthen the daily capability to improve, not replace it.
Its success should not be measured only by the savings achieved or the number of actions implemented.
It should also ask:
What did the team learn?
What capabilities did it develop?
What problems will it now be able to solve without external help?
What routines will remain after the event?
Improvement is not sustainable when it always depends on a special occasion.
When Counting Replaces Purpose
Many organizations record the number of ideas or improvements made by their people.
Doing so is not necessarily wrong.
Counting can help reveal whether participation exists, whether improvement activity is sustained over time, which areas need more support, and how long the organization takes to respond to proposals.
It can also recognize people’s efforts and demonstrate that small improvements matter.
The problem begins when the number stops being a source of information and becomes the purpose.
When the objective is only to reach a certain number of Kaizen improvements, people may begin dividing one improvement into several, recording irrelevant modifications, or implementing ideas without verifying whether they actually made the work easier.
The metric did not create the problem.
The problem was forgetting what it was supposed to help us understand.
Counting improvements tells us that activity occurred.
By itself, it does not tell us what was learned, how much the process improved, or what capabilities people developed.
For that reason, quantity should be considered alongside other questions:
Who is participating, and who is not yet participating?
What obstacles prevent ideas from moving forward?
How many proposals receive a timely response?
What recurring problems do these improvements reveal?
What knowledge was incorporated into the standard?
Which people are now more capable of improving their own work?
An organization can record thousands of improvements and learn a great deal from them.
It can also record thousands and turn the system into a race to meet a quota.
The difference is not whether we count.
It is how we use the measurement.
In Kaizen, numbers should help us understand and strengthen the practice, not replace it.
Kaizen Develops People
In the Toyota Production System, process improvement and people development should not be separated.
When someone learns to recognize an abnormal condition, that person develops the ability to observe.
When someone investigates a cause, that person improves their reasoning.
When someone tests a countermeasure, that person learns to experiment.
When someone compares the result with what was expected, that person strengthens their ability to reflect.
When someone modifies the standard, individual learning becomes shared knowledge.
The process improves.
The person does too.
For that reason, a leader who simply provides answers may achieve a quick improvement while limiting the development of the team.
Solving a problem for someone does not always help that person solve the next one.
Kaizen does not seek to create dependence on experts.
It seeks to progressively expand the number of people capable of understanding and improving their work.
The result matters.
The capability that remains after the result matters too.
Kaizen Happens Within the Work, Not Around It
Another risk appears when improvement becomes a parallel activity.
The work happens during the shift.
Kaizen happens afterward.
The process belongs to the operators.
Improvement belongs to the Lean department.
Problems appear at the genba.
Solutions are designed in a conference room.
When they are separated in this way, working and improving appear to be different responsibilities.
But the people who perform the work are in a privileged position to observe many of its difficulties, irregularities, and opportunities.
That does not mean they must solve every problem alone.
Some conditions require technical knowledge, authority, investment, or coordination across different areas.
It means that improvement must remain connected to the reality of the process and to the people who interact with it every day.
Kaizen is not something we do to the work.
It is something we learn to do while understanding the work.
From a Tool to an Organizational Capability
When Kaizen is interpreted as a tool, the organization tries to implement it.
When it is understood as a capability, the organization tries to develop it.
The difference is profound.
A tool can be purchased, taught, and audited.
A capability is built through practice.
It requires time.
Coaching.
Repetition.
Reflection.
Trust.
And consistent leadership.
Teaching a method is not enough.
People need real opportunities to use it.
Asking for ideas is not enough.
The organization must respond to them.
Celebrating improvements is not enough.
We must also learn from tests that did not work.
Solving problems is not enough.
We must expand the collective capability to continue solving them.
Kaizen does not appear when everyone knows the word.
It appears when improving becomes part of the everyday way of working and leading.
The Real Difference
A problem-solving method mainly responds to one question:
How can we understand and close this gap?
Kaizen asks a broader question:
How can we continuously develop better ways of working and more capable people who can create them?
The questions are related.
But they are not the same.
Problem solving is an essential part of improvement.
Kaizen is the continuous practice that connects problems, opportunities, standards, experimentation, learning, and people development.
That is why the relationship is not:
Kaizen = problem-solving method
It is closer to:
Problem-solving methods + experimentation + standards + participation + learning + people development = the practice of Kaizen
The method provides structure.
Kaizen provides continuity and purpose.
Kaizen Does Not End When the Problem Disappears
When a cause is eliminated, the problem-solving method may reach its conclusion.
The result is verified.
The standard is updated.
The follow-up is closed.
Kaizen continues.
It continues when people observe the new standard.
When they discover another difficulty.
When they imagine a better condition.
When they challenge an assumption.
When they test an idea.
When they share what they learned.
When they help someone else develop the same capability.
Kaizen is not the document filed away after a problem has been solved.
It is the collective willingness to look at the work again and recognize that there is always something more we can understand, simplify, or improve.
It is not a tool we use from time to time.
It is a way of relating to work every day.