TPS Relationships #5 — Jidoka and Standardized Work: You Cannot See Abnormality Until Normal Is Defined
Standardized Work defines what normal should look like. Jidoka makes deviations visible and creates the opportunity to respond. Together, they help organizations recognize abnormalities, protect quality, and learn from the conditions that prevent work from proceeding as expected.
TPS RELATIONSHIPSTPS FUNDAMENTALS
TPS Relationships #5 - Jidoka and Standardized Work: You Cannot See Abnormality Until Normal Is Defined
Without a clearly defined normal condition, abnormalities do not disappear.
They become routine.
A machine begins to require a small adjustment every few cycles. An operator develops a personal workaround to compensate for a recurring problem. Material arrives incomplete, but the team has learned how to continue anyway. The sequence changes depending on who is performing the work.
Nothing seems serious enough to stop the process.
Over time, however, what was once a deviation becomes the accepted way of working.
The problem is still there.
We have simply stopped seeing it.
This is where the relationship between Jidoka and Standardized Work becomes essential.
Jidoka helps us recognize and respond when the process departs from its expected condition.
Standardized Work defines what that expected condition is.
One makes abnormality visible.
The other provides the reference that allows us to call it abnormal.
Jidoka Requires a Reference
Jidoka is often described as the ability to stop when an abnormality occurs.
That description is correct, but incomplete.
Before a person or a machine can stop because something is abnormal, the system must first answer a more basic question:
What is normal?
If the expected sequence is unclear, how can we know that it has been interrupted?
If the expected cycle time is unknown, how can we recognize a delay?
If the expected amount of material at the workstation has not been defined, how can we identify a shortage or excess?
If the expected quality condition is open to interpretation, when should the process stop?
Jidoka does not begin with the stop.
It begins with a clear distinction between normal and abnormal conditions.
Without that distinction, the process may continue operating while defects, delays, workarounds, and instability accumulate.
Standardized Work Defines the Current Normal Condition
Standardized Work is sometimes misunderstood as an attempt to make people work mechanically.
But its purpose is not to eliminate judgment or prevent improvement.
Its purpose is to make the current best-known method visible and repeatable.
It establishes a reference for:
the sequence in which the work should be performed;
the time required to complete it;
the amount of work-in-process needed to maintain the flow;
the conditions necessary to perform the task safely and correctly.
This reference does not mean the process is perfect.
It means the organization has made an explicit decision about how the work should currently be done.
Once that condition is visible, deviations become visible as well.
A missing step is no longer a personal variation.
It is a departure from the expected sequence.
A recurring delay is no longer accepted as “something that always happens.”
It is a difference between the expected cycle and the actual one.
A workaround is no longer evidence of operator flexibility.
It is information that the standard cannot be followed under current conditions.
Standardized Work does not eliminate abnormalities.
It defines the normal condition that allows us to see them.
When Everyone Has a Different Method, Variation Hides the Problem
Imagine a process performed by five different people.
Each person completes the work in a different sequence. Each uses different movements. Each keeps a different amount of material nearby. Each has developed their own way to avoid interruptions.
The process may still produce acceptable results.
But when something goes wrong, it becomes difficult to understand why.
Was the problem caused by the design of the work?
By the sequence?
By missing material?
By a quality issue?
By an equipment condition?
Or simply by the way one person chose to perform the task?
Without a common reference, variation in the method mixes with variation in the process.
The system cannot distinguish between the two.
As a result, problems remain hidden inside individual experience.
The most experienced operators compensate for them.
New operators struggle with them.
Supervisors interpret them as performance differences.
And the process continues without learning.
Standardized Work separates the method from the individual.
It creates a shared baseline from which the organization can observe, compare, and understand.
Only then can Jidoka respond to a meaningful abnormality rather than to unexplained variation.
An Andon Signal Depends on Shared Understanding
An Andon signal is often treated as the visible symbol of Jidoka.
A light turns on.
A sound is activated.
An operator pulls a cord or presses a button.
Help is requested.
But the signal itself is not the system.
The real question is whether the people doing the work understand when the signal should be activated.
Should the operator call for help when a part does not fit correctly?
When material is missing?
When the cycle cannot be completed on time?
When the standard sequence must be changed?
When a defect is suspected but not yet confirmed?
If these conditions have not been clearly defined, the decision depends on personal judgment.
One operator may stop immediately.
Another may try to solve the problem alone.
A third may continue because similar deviations have been tolerated before.
The Andon exists, but the criteria for using it remain ambiguous.
Standardized Work provides those criteria.
It turns the call for help from a subjective decision into a response to a visible departure from the expected condition.
Jidoka then becomes more than a mechanism for stopping.
It becomes a disciplined way to prevent abnormalities from moving forward.
The Most Dangerous Abnormalities Are the Ones We Normalize
Many process failures do not begin as dramatic events.
They begin as small deviations.
A tool is placed slightly farther away.
An inspection is postponed until the end.
A machine requires a minor adjustment.
A component arrives with inconsistent dimensions.
A task regularly exceeds its expected time.
Someone discovers a workaround.
Production continues.
Because the immediate result appears acceptable, the deviation is tolerated.
Then it is repeated.
Eventually, it becomes part of the process.
This is how abnormality becomes normal.
Not because anyone formally decided to change the standard, but because the system learned to live with the deviation.
The risk is not only that performance deteriorates.
The deeper risk is that the organization loses its ability to detect deterioration.
Once a workaround becomes routine, it no longer appears on a problem-solving list.
Once waiting becomes expected, nobody asks why it occurs.
Once rework is built into the schedule, defects stop feeling abnormal.
A process can become increasingly unstable while appearing completely familiar to the people inside it.
That is why defining normal is not a bureaucratic exercise.
It is an act of protection.
Stopping Is Not the Final Objective
Jidoka is sometimes reduced to the instruction: stop the process when there is a problem.
But stopping is not the purpose.
Learning is.
A stop creates the opportunity to prevent the abnormality from advancing and to understand what caused it.
If the process stops but no one investigates, the system only loses production.
If the process stops and the response is to blame the operator, people will soon stop making problems visible.
If the process stops and the only action is to restart it as quickly as possible, the abnormality will return.
The stop has value only when it leads to understanding.
Standardized Work strengthens that learning because it allows the team to compare the actual condition with the expected one.
What step could not be completed?
At what point did the sequence change?
What condition was missing?
What caused the cycle to extend?
What forced the operator to deviate?
The standard becomes a reference for investigation.
It helps the team move from “something went wrong” to a more precise understanding of what changed.
The Standard Is Not a Weapon Against the Operator
There is a danger in defining normal too rigidly.
A standard can be used as a reference for learning.
Or it can be used as a weapon for compliance.
When a person cannot follow the standard, the first conclusion should not be that the person failed.
The first question should be:
What prevented the standard from being followed?
Perhaps the material was late.
Perhaps the equipment condition changed.
Perhaps the workload was unrealistic.
Perhaps the standard was incomplete.
Perhaps the actual work was never properly observed.
Perhaps the process has changed, but the document has not.
An abnormality is not automatically evidence of poor discipline.
It may be evidence that the system no longer supports the expected method.
This is another important connection between Jidoka and Standardized Work.
The standard helps expose the deviation.
Jidoka creates the moment in which the organization must respond.
The quality of that response determines whether people will continue making problems visible.
If the response is blame, abnormalities will be hidden.
If the response is curiosity, abnormalities will become opportunities for improvement.
Normal Is Not Permanent
Defining normal does not mean freezing the process.
The standard represents the best-known condition today.
When the team learns a safer, simpler, more reliable, or more efficient method, the standard should change.
This is why Standardized Work must remain connected to Kaizen.
A stable reference is necessary to detect abnormality.
But that reference must evolve as the system learns.
Otherwise, people may be asked to follow a condition that no longer reflects reality.
Jidoka does not protect the standard from change.
It protects the process from uncontrolled deviation.
There is an important difference.
Improvement is a deliberate change based on learning.
Abnormality is an unplanned departure that has not yet been understood.
One should update the standard.
The other should trigger investigation.
Without a defined normal condition, the organization cannot clearly distinguish between them.
Visibility Before Correction
Organizations often rush to solve problems before they have made the problems visible.
They add inspections.
They increase supervision.
They introduce new controls.
They remind people to be more careful.
But if the normal condition remains undefined, these actions produce activity without clarity.
The system still does not know what it is trying to protect.
Standardized Work creates that clarity.
Jidoka uses it to reveal the moment when reality no longer matches the expected condition.
Together, they create a simple but powerful sequence:
Define normal.
Recognize the deviation.
Stop it from advancing.
Understand what changed.
Improve the system.
Update the standard.
This is not only a quality mechanism.
It is a learning mechanism.
The Relationship
Jidoka and Standardized Work are sometimes discussed as separate elements of TPS.
One belongs to quality at the source.
The other belongs to process stability.
But they depend on each other.
Standardized Work without Jidoka may document a method while allowing deviations to continue unnoticed.
Jidoka without Standardized Work may ask people to react to abnormalities that have never been clearly defined.
One establishes the reference.
The other protects it by making deviations visible.
Together, they help the organization distinguish between three very different conditions:
The work is proceeding as expected.
The work has departed from the expected condition.
The expected condition itself needs to be improved.
That distinction is fundamental.
Because a problem cannot be solved consistently until it can be recognized consistently.
And an abnormality cannot be seen clearly until normal has been defined.