The Cord Is Not a Confession: Making Andon Calls Routine on the Line

You see it at Station 14: a housing that will not seat clean. The operator checks it once, checks it twice, then looks down the line. The team lead is on the phone. The schedule board is full. The operator thinks, I can probably make this one work, and the part moves on. Everyone loses. The operator loses confidence, the next station loses time, and the customer may eventually lose faith.

The andon cord is supposed to prevent that moment. Too often, though, it becomes a test of nerve. Pulling it feels like admitting you cannot handle the job. Or like calling out a coworker. Or like handing your supervisor a reason to look at your numbers. None of that is what andon is for.

Why good operators freeze

Most hesitation is not laziness. It is a rational read of the room. If the last person who stopped the line got a sigh and a lecture, the next person will think twice. If calls result in a five-minute visit and no real fix, people learn that the system is theater. If supervisors only show up when something is badly wrong, every call feels like an emergency.

Operators are also trained to keep things moving. That is a good instinct. The problem is when "keep it moving" becomes "hide the problem." Andon only works when the team separates two ideas: stopping to protect quality is part of production, not the opposite of production.

Make the call boring

The goal is not more drama. The goal is a short, clear signal that brings the right help without turning the operator into a defendant. The simplest way to get there is a script that everyone practices until it sounds normal.

Operator stop-call script

1. Signal first. Pull the cord or press the button. Do not wait until you have a full explanation.
2. Give the location and the issue. Say: "Andon, Station 14, housing fit issue, holding the part."
3. State what you have done. Say: "I have the suspect part in the red bin and I am checking the next one."
4. Stay with the station until someone responds. If the line keeps moving, follow your plant's stop procedure, but do not walk away from the concern.

That is it. No long story. No apology. No guessing at root cause. The operator's job is to surface the condition, not solve the whole thing alone.

Responder script

When help arrives, the first words matter. Try: "Thanks for the call. What did you see?" Then: "What do you need from me right now?" Then: "What should we check next?"

Avoid: "Why did you stop the line?" Avoid: "Who ran that part?" Avoid: "Can it wait?" Those questions teach people to hesitate. Curiosity teaches them to call.

Response-time expectations that mean something

A blameless culture without response time is just a nice poster. Teams need a simple promise they can keep. Adjust the numbers to your plant, but write them down and post them where operators can see them.

• Acknowledgment: within 60 seconds. A light, a buzzer, or a team lead saying "on my way" is enough. Silence is what kills trust.
• Team lead arrival: within 3 minutes for a standard quality call. If the lead cannot come, they name who is coming.
• Quality or maintenance support: within 10 minutes for calls that need a specialist. If support is backed up, the lead says so and gives a new time.
• Escalation: if no one responds in the promised window, the operator or lead escalates to the next level. No call should disappear into the ceiling.

These are not punishments. They are service levels. The operator is the customer of the response system. If the system does not respond, the system is broken, not the operator.

The wall test: is your andon real?

You can learn a lot without a consultant. Walk the floor and try this test at a station that rarely calls and one that calls often.

1. Ask the operator to simulate a call. Time how long until someone acknowledges. Time how long until someone arrives. Watch whether the operator seems comfortable or nervous.
2. Ask what happened on the last three calls. If nobody remembers, the calls are not feeding improvement. If people remember and the fix stuck, the system is alive.
3. Check the response, not just the button. Is there a log, a board, or a shift note that shows calls and actions? If the only evidence is a dusty andon light, you have decoration.
4. Listen for blame language. In the next shift huddle, count how many times someone says "who" instead of "what" or "where." Language leaks culture.

If calls are rare, slow, or followed by sighs, the system is not protecting quality. It is teaching people to work around problems. That is expensive in a way the schedule board never shows.

Keep the habit small and visible

You do not need a campaign. You need repetition. At the start of shift, remind people of the call script in one sentence. Thank the first person who calls that day, even if the issue turns out to be minor. Review two andon calls in the weekly team meeting and ask what changed. Put response times on a board and update them honestly.

And when someone stops the line for a real concern, say the quiet part out loud: "That call protected the customer." Do it often enough and the cord stops feeling like a confession. It starts feeling like a tool, which is all it ever was.