TPS Relationships #7 — Andon and Leadership: A Signal Is Only as Valuable as the Response It Receives
Andon makes problems visible, but its value depends on how leadership responds. Discover how a thoughtful response can build trust, protect the process, and turn every difficulty into an opportunity for learning.
DEVELOPING PEOPLELEADERSHIPTPS RELATIONSHIPS
TPS Relationships #7 — Andon and Leadership: A Signal Is Only as Valuable as the Response It Receives
Someone notices that something is not working as it should.
It might be a part that does not fit, incomplete information, an unsafe condition, or a difference between what was expected and what is actually happening.
That person has two options.
They can make the problem visible.
Or they can try to handle it alone, improvise a solution, and keep working.
At first glance, the difference might appear to depend on their attitude, experience, or commitment.
But often, it depends on something much simpler:
What happened the last time someone asked for help?
If the response was supportive, curious, and focused on understanding, the problem will probably become visible.
If the response was blame, pressure, or indifference, the problem will probably disappear from the conversation.
Not from the system.
From the conversation.
And that difference can determine whether an organization learns or simply continues accumulating vulnerabilities.
Andon Does Not Begin With an Alarm
When we talk about Andon, we often picture a light, a screen, an audible signal, or a mechanism that allows someone to request help when an abnormal condition appears.
These signals can be part of the system.
But Andon does not begin when a light turns on.
It begins when someone recognizes that something is not happening as it should and decides to make it visible.
That decision matters more than the device.
We can install screens, configure alerts, and document escalation procedures. But if people believe that asking for help may have negative consequences, they will find ways to avoid activating the signal.
They will work around the problem.
They will compensate for variation.
They will conceal the difficulty.
And over time, the system will appear to function better than it actually does.
Not because it has fewer problems.
Because fewer problems are visible.
A Signal Does Not Improve Anything on Its Own
Imagine a smoke detector in a house.
Its purpose is not to extinguish a fire. Its purpose is to make visible a condition that requires attention.
The value of the alarm depends on what happens next.
If the people in the house investigate the source of the smoke, understand the situation, and respond promptly, the signal serves its purpose.
But if they silence the alarm because the sound is annoying and return to whatever they were doing, the detector stops protecting them.
The detector still works.
The response does not.
The same is true of Andon.
A light may turn on. An alert may appear. Someone may raise a hand.
But if no one comes, if the response arrives too late, or if the first reaction is criticism, the signal loses its ability to protect the process.
The organization still has Andon.
What it does not have is a system that learns when Andon is activated.
Leadership Defines What the Signal Means
The same signal can mean completely different things depending on how a leader responds.
In one environment, raising a hand means:
We found a gap that we need to understand together.
In another, it means:
You interrupted the work, and now you will have to explain why.
The device may be identical. The procedure may be identical too.
What changes is the experience of the person who identified the problem.
When a leader responds by asking:
What did you do wrong?
Attention turns toward self-defense.
When the leader asks:
What is happening, and what did we expect to happen?
Attention turns toward the system.
The first question looks for someone to blame.
The second creates an opportunity to learn.
This distinction does not eliminate accountability. It places accountability where it can produce a better response: understanding the conditions that allowed the problem to emerge and helping people address them.
Showing Up Is Not the Same as Understanding
Responding to a signal does not simply mean arriving at the workstation.
Nor does it mean solving the immediate problem as quickly as possible so operations can continue.
Sometimes, of course, the situation must be stabilized. If there is an unsafe condition, a risk to the customer, or a significant interruption, the immediate response matters.
But restoring operations does not necessarily explain why the problem appeared.
A leader may arrive, adjust a part, replace a component, approve an exception, or ask someone to work faster.
The process starts moving again.
The signal turns off.
Everyone returns to work.
Yet if the conditions that produced the difficulty remain, the system has not learned.
It has only recovered its ability to continue temporarily.
A more useful response distinguishes between two questions:
What do we need to do now to protect people, the customer, and the process?
And then:
What do we need to understand to reduce the likelihood that this condition will appear again?
The first question stabilizes.
The second develops capability.
Both are necessary.
What Happens Next Teaches More Than Any Speech
Many organizations say they want people to report problems.
They put up posters. They launch campaigns. They talk about transparency, continuous improvement, and teamwork.
But people do not learn what making a problem visible truly means by reading a statement.
They learn by watching what happens when someone does it.
If a supervisor responds with frustration, the team learns that the signal is an interruption.
If someone is criticized for stopping when an abnormal condition appears, the team learns that production matters more than understanding.
If problems are reported but never followed up, the team learns that raising a hand changes nothing.
But if the leader comes, listens, observes the actual work, and helps make sense of the situation, the team learns something different:
Making a problem visible is a contribution, not a failure.
Trust is not built by asking people to trust.
It is built by responding consistently when difficulties appear.
The Response Also Reveals the Leadership System
Sometimes a leader wants to respond better but cannot.
They may be attending too many meetings. They may have several competing responsibilities. They may not understand the process well enough. They may lack support to keep operations running while they investigate.
In those situations, it would be easy to conclude that the problem is a lack of commitment.
But the systemic question applies to leadership as well:
What conditions enable a leader to respond effectively when someone asks for help?
If the system expects leaders to be available but structures their work so they can never get close to the process, asking them to try harder will not solve the problem.
Perhaps they need clearer priorities.
Perhaps they need a stronger support structure.
Perhaps they need to develop their ability to observe, ask questions, and coach.
Or perhaps the organization needs to examine how many problems it has normalized before they become impossible to address.
An Andon system does not depend only on someone raising a hand.
It also depends on whether a timely, useful response is possible.
When the Signal Disappears, the Risk May Increase
An organization may celebrate when fewer alerts are activated.
Sometimes that reduction indicates that the process has become more stable.
But it can also indicate something entirely different: people have stopped reporting what they observe.
The number of signals alone cannot explain which situation is unfolding.
To understand the difference, we need to observe the actual work.
Have difficulties truly decreased?
Or have people learned to handle them silently?
Have the conditions that created interruptions been addressed?
Or have exceptions simply become normal?
Does the team feel more confident asking for help?
Or has it concluded that asking is not worthwhile?
A quiet process is not always a stable process.
Sometimes, it is a process that has stopped speaking.
The Relationship Between Andon and Leadership
Andon makes visible the difference between what was expected and what is actually happening.
Leadership determines what happens to that difference.
It can turn the situation into a search for someone to blame.
It can reduce the signal to an interruption that must disappear.
Or it can use the moment to protect the process, support people, and better understand the system.
That is why the relationship between Andon and leadership is not simply about installing an alert mechanism and assigning someone to respond.
It is about designing an organization where making problems visible is possible, where asking for help makes sense, and where every response contributes to a deeper understanding of the work.
The signal does not create learning.
The device does not build trust.
The alert does not improve the system on its own.
What makes the difference is how we respond when someone finds the courage to say:
Something is not working as it should.
Because a signal is only as valuable as the response it receives.
Andon reveals the problem. Leadership determines whether the system learns from it.