TPS Relationships #9 — Jidoka × Psychological Safety: Making Problems Safe to See
Jidoka depends not only on detecting and stopping abnormalities, but also on creating an environment where people feel safe making them visible. This article explores how psychological safety turns Andon from a mechanism into a true system for learning.
DEVELOPING PEOPLELEADERSHIPTPS RELATIONSHIPS
TPS Relationships #9 — Jidoka × Psychological Safety: Making Problems Safe to See
Jidoka is often described as “automation with a human touch.”
That description usually brings machines to mind.
A machine detects an abnormality.
It stops.
It prevents the defect from continuing downstream.
But the human touch matters just as much when no machine can detect what is happening.
Sometimes a person notices first.
A sound is different.
A dimension does not look right.
The standard cannot be followed.
A process begins behaving unexpectedly.
Something simply feels wrong.
And then comes the moment that determines whether Jidoka actually exists:
Does that person feel safe enough to make the abnormality visible?
That is where Jidoka meets psychological safety.
The human side of Jidoka
At its core, Jidoka is not simply about stopping machines.
It is about refusing to let abnormalities continue unnoticed.
Sometimes technology does that for us.
Sometimes people have to do it.
A person may need to pull an Andon cord.
Raise a hand.
Stop a process.
Call a team leader.
Challenge an assumption.
Admit uncertainty.
Or simply say:
“Something is not right.”
Technically, that can look very simple.
Humanly, it may not be.
Because making a problem visible also makes the person who exposed it visible.
And what happens next matters.
A lot.
“Not again! What now?”
Imagine an operator pulls the Andon cord.
From several meters away comes the response:
“Not again! What now?!”
Maybe it is said only out of frustration.
Maybe the leader is under pressure.
Maybe production is already behind.
Maybe nobody intends to intimidate anyone.
But the operator still learns something.
The lesson is not:
Thank you for making the abnormality visible.
The lesson is:
Pulling the Andon creates trouble.
Nobody has to prohibit its use.
Nobody has to write a policy against stopping the line.
Nobody has to punish the operator formally.
A repeated sigh, an irritated face, an impatient tone, or a sarcastic comment may be enough.
The Andon cord can remain physically available while becoming psychologically unavailable.
And once that happens, the organization has weakened Jidoka without changing a single technical standard.
The mechanism is not enough
An organization can install Andon lights.
Create escalation procedures.
Define stop-the-line rules.
Train people to recognize abnormalities.
Tell everyone that quality comes first.
And still create an environment where people hesitate to speak.
Because people do not learn culture primarily from procedures.
They learn it from reactions.
They notice what happens when someone raises a concern.
They notice what happens when a problem threatens output.
They notice whether asking for help creates support or irritation.
They notice whether admitting uncertainty is treated as responsibility or incompetence.
The written standard may say:
Stop when you see an abnormality.
But the experienced standard may become:
Stop only if you are willing to deal with what happens afterward.
At that point, the Andon still exists.
But Jidoka has become weaker.
Jidoka is also about what happens to the person
This may be one of the most important relationships between Jidoka and psychological safety:
Jidoka is not only about what happens when an abnormality is detected. It is also about what happens to the person who detects it.
Does the leader arrive asking:
“Who did this?”
Or:
“What happened?”
Does the first reaction communicate disappointment?
Or curiosity?
Does the person who raised the signal feel that they created a problem?
Or that they helped prevent one from traveling further?
That first response teaches far more than we sometimes realize.
If the person is embarrassed, they remember.
If a concern is dismissed, they remember.
If asking for help triggers frustration, they remember.
If stopping production is treated as personal failure, they remember.
And the next time something looks wrong, those memories participate in the decision.
Speak?
Or stay quiet?
Pull the cord?
Or let it pass?
Silence can become the safest behavior
Organizations often assume that people will naturally expose problems because doing so is “the right thing.”
But people operate inside social systems.
They observe risk.
They adapt.
If making a problem visible repeatedly creates negative consequences, silence can become a rational behavior.
Not necessarily because people do not care.
Sometimes precisely because they do.
They may not want to disappoint their leader.
They may not want to slow everyone down.
They may not want to be seen as difficult.
They may not want to be the person who “always finds something.”
They may think:
Maybe I am overreacting.
Maybe someone else will notice.
Maybe we can make it through this batch.
Maybe I should not stop everyone for this.
That is how abnormalities begin to travel.
And once a problem travels, it becomes harder and more expensive to understand.
Stopping is not failure
This becomes especially difficult in environments where continuity is celebrated.
Downtime is bad.
Missed output is bad.
Delayed shipments are bad.
Interrupted meetings are bad.
Escalations are uncomfortable.
So people begin to receive two competing messages.
One says:
Do not pass defects forward.
The other says:
Do not interrupt the flow.
One says:
Ask for help early.
The other rewards the person who solves everything alone.
One says:
Make problems visible.
The other becomes uncomfortable when visibility threatens the target.
In that environment, continuing may feel safer than stopping.
But from a Jidoka perspective, a stop at the right moment is not failure.
It may be the most responsible action available.
A stop can protect the customer.
Protect the next process.
Protect the standard.
Protect the team from producing more of the same abnormality.
And create the opportunity to learn while the conditions are still visible.
Psychological safety does not mean lowering standards
There is an important distinction here.
Psychological safety does not mean that every concern is correct.
It does not mean removing accountability.
It does not mean accepting weak performance.
It does not mean that nobody should ever be challenged.
People can misunderstand situations.
Signals can be false.
Judgment can be imperfect.
But if people are afraid to raise a concern until they are absolutely certain, many abnormalities will remain hidden too long.
The system should make it safe to say:
“I may be wrong, but I think we should look at this.”
Then we investigate.
Observe.
Compare against the standard.
Learn.
Psychological safety is not protection from thinking carefully.
It is protection of the act of making uncertainty visible enough to examine it.
The leader’s reaction becomes part of the Andon system
We often treat the Andon as hardware.
A cord.
A button.
A light.
A board.
A signal.
But the leader who responds is also part of the system.
If the hardware works perfectly but the human response discourages future signals, the system is still poorly designed.
That means the response to an Andon deserves as much attention as the mechanism itself.
Maybe the first words should not be:
“Why did you stop?”
But:
“What did you see?”
That small difference matters.
One begins with justification.
The other begins with observation.
One may make the person defend the stop.
The other invites the team to understand the abnormality.
That is the human touch too.
This goes far beyond the production line
The same relationship exists outside manufacturing.
An engineer sees data that does not support a release.
Will they say so?
A salesperson realizes that a commitment may exceed current capability.
Will they challenge it?
A finance analyst notices that a KPI may be driving the wrong behavior.
Will they raise the concern?
A project member sees an assumption becoming unrealistic.
Will they interrupt the plan?
A manager realizes that the target itself may be creating instability.
Will they tell senior leadership?
There may be no physical Andon cord in any of these situations.
But the principle is identical.
Someone notices an abnormality.
Someone has to decide whether to expose it.
The organization’s response determines what they are likely to do next time.
The real test of empowerment
It is easy to say:
“People are empowered to stop.”
The real test is whether they believe it.
Would an operator pull the Andon when uncertain?
Would someone admit:
“I don’t know.”
Would a team member say:
“I cannot follow the standard under these conditions.”
Would someone question an assumption made by a senior leader?
Would a person raise a concern that eventually turns out to be nothing?
And if they did, what would happen to them?
That question may reveal more about the organization’s actual Jidoka system than the number of Andon lights installed on the floor.
Jidoka makes problems visible. Psychological safety makes visibility possible.
Jidoka asks us not to allow abnormalities to continue silently.
Psychological safety helps determine whether people will actually expose them.
One provides the mechanism.
The other helps create the human conditions in which that mechanism can work.
Machines do not worry about embarrassment.
Sensors do not fear disappointing their boss.
Automatic controls do not wonder whether raising an alarm will make them look incompetent.
People do.
That is why a system built around Jidoka has to consider not only how abnormalities are detected and stopped, but also how people are treated when they are the ones who notice them first.
A system that asks people to expose problems must also protect the act of exposing them.
Otherwise, sooner or later, people may learn that the safest response to an abnormality is silence.
And silence is the opposite of Jidoka.