TPS Relationships #3 - Standardized Work and Kaizen: Stability as a Foundation for Improvement
Standardized work and Kaizen are not opposing forces. One establishes a known condition for observation, comparison, and learning; the other prevents that condition from becoming permanent. This article explores how stability and improvement reinforce each other, turning every lesson into a new standard and every standard into the starting point for the next experiment.
TPS RELATIONSHIPSTPS FUNDAMENTALS
TPS Relationships #3
Standardized Work and Kaizen: Stability as a Foundation for Improvement
Standardized work and Kaizen are often presented as opposing ideas.
One seems to seek stability.
The other seems to drive change.
One defines a known way of performing the work.
The other questions whether that way can be improved.
For that reason, some people interpret standardized work as a limitation on creativity and Kaizen as a constant break from what has already been established.
But within the Toyota Production System, they do not compete.
They need each other.
Standardized work creates a reference for observing, comparing, and learning.
Kaizen prevents that reference from becoming a permanent condition.
One allows us to recognize what changed.
The other allows us to turn that change into a new way of working.
Without standardized work, Kaizen can become change without evidence.
Without Kaizen, the standard can become stability without learning.
We Cannot Improve a Condition We Do Not Know
Imagine a process performed differently by every person.
Each operator follows a different sequence.
Tools are placed in different locations.
The required time changes constantly.
Materials are used in varying quantities.
Some steps are omitted, while others are added according to experience, personal preference, or the circumstances of the moment.
Under those conditions, there may be highly skilled people and acceptable results.
But it becomes difficult to understand clearly how the process actually works.
If a defect appears, we do not know which method produced it.
If the time improves, we do not know what changed.
If one person achieves a better result, we cannot distinguish whether it came from a superior practice, greater experience, or simply a different condition.
Variation in the method hides the relationship between the way the work is performed and the result.
That is why, before improving, we need a known condition.
Standardized work does not eliminate all process variation, but it seeks to reduce unnecessary variation in the way the work is performed and establishes a common basis for observation.
Among other elements, it defines a known sequence, an expected time, and a specified amount of work in process.
That reference allows us to ask an essential question:
What happened differently from the known condition?
Without that question, learning becomes much more difficult.
The Standard Is Not a Perfect Description of the Work
A common misunderstanding is to believe that the standard represents a perfect, permanent, and unquestionable way of working.
It does not.
The standard represents the best-known way at this moment under specific conditions.
The important words are at this moment.
It is temporary knowledge.
It summarizes what the organization has learned so far about performing the work safely, with quality, efficiency, and consistency.
But it also has limitations.
It may have been designed under conditions that have already changed.
It may include unnecessary motions that no one has questioned.
It may depend on skills that are not clearly expressed.
It may work for an experienced person but be difficult for someone new to learn.
It may produce the expected result while also creating burden, frustration, or risk.
The standard does not prove that nothing remains to be improved.
It makes visible where we are starting from.
Without a Reference, Any Change Can Look Like an Improvement
Suppose someone changes the order of two steps and the process appears to move faster.
Did it really improve?
To answer, we need to compare.
What was the previous time?
Was quality maintained?
Did the burden on the person increase?
Was an activity transferred to another process?
Can the result be repeated?
Does it work for different operators?
Did it create any new risk?
Without a known previous condition, we may observe a difference, but we cannot necessarily evaluate an improvement.
Standardized work provides that reference.
It allows us to compare before and after.
It makes it possible to distinguish between a perception and a result.
It helps verify whether a new way of working is truly better or merely appears faster under a particular condition.
That is why the standard is not the enemy of experimentation.
It is what allows us to learn from it.
Kaizen Questions the Best-Known Way
If standardized work were only an instruction that had to be obeyed, it could become a form of control.
But its relationship with Kaizen changes its purpose.
The person does not simply follow the standard.
They also learn to observe it.
Where does difficulty exist?
At which step does waiting appear?
Which motion seems unnecessary?
Which part depends too heavily on memory?
What condition creates risk?
Where does work accumulate?
What happens differently from one cycle to another?
Kaizen begins when the standard stops being seen as an order and starts being seen as a hypothesis.
The organization states:
This is the best way we know for now.
It then observes reality to discover where that statement is no longer sufficient.
The standard provides a foundation.
Kaizen keeps open the possibility of surpassing it.
Following the Standard Does Not Mean Stopping Thinking
When standardized work is implemented in an authoritarian way, it can communicate a dangerous message:
“Do not think. Just follow the instructions.”
That deeply contradicts people development.
The purpose should not be to create people who mechanically execute a sequence.
It should be to create conditions in which they can recognize when the process is working as expected and when it is not.
A person who understands the standard can detect a deviation.
They can explain which condition changed.
They can identify where the work becomes difficult.
They can participate in improvement experiments.
They can distinguish between a necessary adaptation and a deviation that creates risk.
The standard does not replace judgment.
It helps develop it.
To achieve this, people need to understand not only what they must do, but also why that way was defined.
When the purpose is understood, the standard stops being a list of orders.
It becomes shared knowledge.
Kaizen Does Not Mean Changing the Standard Every Day
There is also an opposite risk.
Some organizations promote improvement in such a way that anyone changes the method whenever they find an alternative that seems better.
The intention may be positive.
But when changes are made without observation, testing, verification, and agreement, the process once again fills with variation.
Each person develops their own version.
Improvements are not shared.
Results are not compared.
New risks appear without being detected.
And the organization loses the ability to know how the work is actually being performed.
Kaizen does not mean having the freedom to change everything without discipline.
It means having the freedom to question, experiment, and learn within a process that allows results to be verified.
Not every change should immediately become the new standard. It must first be tested, verified, and agreed upon with the people involved in the process.
Improvement requires creativity.
But it also requires rigor.
From the Standard to the Experiment
The relationship between standardized work and Kaizen can be represented as a cycle:
Standard → observation → gap → experiment → learning → new standard
The standard establishes the current condition.
Observation reveals a difficulty, deviation, or opportunity.
The gap defines what we want to improve.
The experiment tests a different way.
The result produces learning.
If the new condition proves to be better and sustainable, it is incorporated into the standard.
Then the cycle begins again.
The new standard is not the conclusion of Kaizen.
It is evidence that something was learned.
At the same time, it becomes the new starting point.
When Improvement Does Not Change the Standard
Many organizations make improvements that disappear over time.
An area is reorganized.
A sequence is changed.
A visual aid is developed.
A motion is eliminated.
A quantity is modified.
For several days or weeks, the process works better.
Then people gradually return to the previous way.
This is often attributed to a lack of discipline.
In some cases, that may be true.
But it may also happen because the improvement never became shared knowledge.
The standard was not updated.
The change was not explained.
People were not trained.
No one verified that the new condition was practical for everyone.
It was not incorporated into daily management.
The improvement remained in the memory of those who participated.
When those people changed shifts, areas, or responsibilities, the learning was lost.
An improvement that does not change the standard risks remaining an isolated experience.
Updating the standard is not an administrative task performed after Kaizen.
It is how the system preserves what it has learned.
When the Standard Does Not Reflect the Real Work
The opposite also happens.
The document is updated, but the actual work continues to be performed differently.
The standard is kept in a folder, on a computer, or on a board.
People follow another method because the document is impractical, outdated, or was designed far from the genba.
In those cases, the organization may claim to have standardized work, but it only has documentation.
The standard must live in the process.
It must be observable.
It must help the person performing the work.
It must be clear enough to support learning and precise enough to distinguish a deviation.
And it must be reviewed when reality shows that it no longer represents the best-known way.
When the standard and the real work do not match, the first question should not automatically be:
“Why is the person not complying?”
We should also ask:
“Why does the standard not describe reality?”
The difference may reveal a training need.
But it may also reveal that the defined method needs to improve.
A Deviation Can Be a Problem or a Signal of Learning
Not every deviation has the same meaning.
Some deviations represent risk.
A person skips a critical check.
They use an incorrect quantity.
They perform the work out of sequence and affect quality.
In those cases, restoring the standard condition may be necessary immediately.
But other deviations may reveal that people found a different way to address a difficulty.
Perhaps they moved a tool because its original location created unnecessary travel.
Perhaps they temporarily changed a sequence because a material arrived late.
Perhaps they created an informal signal because the existing visual system was not sufficient.
That does not mean every deviation should be accepted.
It means we must learn to investigate it.
The response cannot be limited to demanding compliance.
We must understand why the actual condition moved away from the standard.
Sometimes we will discover a need for training.
At other times, we will discover a Kaizen opportunity.
The Leader Protects Stability and Allows Questioning
This relationship requires a particular kind of leadership.
The leader must protect the standard because learning is difficult without stability.
But the leader must also prevent the standard from becoming an unquestionable authority.
They should ask:
Which part of the work is difficult?
Where does the deviation appear?
What condition changed?
What have you observed?
What did you expect to happen?
What could we test?
How will we know whether it was better?
Leadership is not only about ensuring that people follow the method.
It is also about developing their ability to understand and improve it.
That requires a healthy tension.
Do not change without learning.
Do not preserve without questioning.
Do not allow every modification.
Do not prevent all experimentation.
The leader holds that tension so stability and improvement can coexist.
An Imposed Standard Limits Kaizen
When the standard is designed exclusively by specialists and handed to people for compliance, it may lose an important part of its value.
Specialists can contribute technical knowledge, safety, ergonomics, quality, and process design.
Their participation may be indispensable.
But the people who perform the work know details that are difficult to observe from outside.
They know the interruptions.
The recurring difficulties.
The uncomfortable motions.
The small decisions required to maintain flow.
The conditions that change from one cycle to another.
That is why developing and improving standards should include the people who interact directly with the process.
Participation does not mean that every individual preference must be incorporated.
It means that genba knowledge must be part of the design.
When people participate in building the standard, they understand its purpose more clearly and are better prepared to recognize improvement opportunities.
The standard stops feeling like something someone created to control their work.
It becomes something the team uses to understand it.
Creativity Needs a Foundation
It is sometimes said that standardization reduces creativity.
In reality, creativity without a known condition may generate many ideas but little accumulated learning.
Each person tries something different.
Some solutions work.
Others do not.
But when they are not compared, documented, and shared, the organization starts over again and again.
Standardized work allows creativity to produce cumulative knowledge.
One person experiments.
The team verifies.
The organization learns.
The standard changes.
The next person no longer starts from zero.
They begin from what the team previously learned.
In this way, individual creativity can become organizational capability.
Stability Also Protects People
Standardized work does not only help improve results.
It also reduces dependence on constant improvisation.
When the process has no known way of being performed, people must make basic decisions again and again.
They must remember details.
Resolve shortages.
Adapt to changing conditions.
Compensate for weaknesses in the system.
That flexibility may look like experience, but it can also become mental and physical burden.
A good standard eliminates unnecessary decisions.
It supports training.
It clarifies what is expected.
It makes difficulties visible.
It allows people’s energy to be used for observation and improvement, rather than merely keeping an unstable process running.
Stability does not eliminate participation.
It can create the space required for deeper participation.
Kaizen Prevents Stability from Becoming Complacency
Stability also carries a risk.
When a process meets its targets, the organization may conclude that it no longer requires attention.
The method works.
Quality is acceptable.
Delivery is achieved.
The indicator is green.
But a stable condition may still contain waste, burden, risk, or dependence on particular people.
Kaizen prevents us from confusing stability with perfection.
It reminds us that following the standard does not mean reaching the best possible condition.
A process can be stable and still be far from an ideal condition.
That is why, even when no obvious deviation exists, we can ask:
Can we do it with less effort?
Can we make learning easier?
Can we reduce risk?
Can we simplify the flow?
Can we move closer to customer value?
The standard stabilizes what has been learned.
Kaizen keeps curiosity alive.
The TPS Relationship
Standardized work and Kaizen perform different functions.
Standardized work establishes a known condition that allows us to observe, compare, and detect deviations.
Kaizen uses that condition as a starting point for experimentation, learning, and building a better way of working.
One preserves knowledge.
The other expands it.
One reduces unnecessary variation.
The other prevents stability from becoming immobility.
That is why the relationship is not:
Standard or improvement.
It is:
A standard so we can improve. Improvement so we can build a new standard.
Without standardized work, we cannot clearly know what changed.
Without Kaizen, the standard stops learning.
Together, they create a cycle in which stability does not stop improvement and improvement does not destroy stability.
The standard represents the best-known way today.
Kaizen keeps open the possibility of finding a better one tomorrow.