A cord pulled is a clock started. The response time is the whole game.
Andon response is the part of the andon system that almost every shop gets wrong. The hardware is easy: install lights, run cords, color-code the board. The response is the hard part, because it requires defined escalation, defined authority, defined response times, and the cultural rule that signals get treated as useful information rather than disruption. A shop with andon hardware and no response builds a shop full of signals nobody trusts. A shop with a real response system builds a shop where problems surface in seconds and get fixed in minutes.
"An andon cord pulled into silence is a cord pulled for the last time."
A working andon response system has four pieces.
The first is the escalation tree. A published, visible map of who responds at each tier and how fast. The standard small-shop pattern: tier one is the lean team leader, responding within 60 to 90 seconds. Tier two is the shift supervisor or group leader, within five minutes. Tier three is the plant manager or owner, within 15 to 30 minutes when warranted. Each tier has defined authority: what decisions they can make, what they have to escalate. The tree is posted at every workstation in the simplest possible form.
The second is authority at each tier. Tier one needs the authority to make common decisions on the spot: hold the affected parts, swap a worn fixture, call maintenance, restart the line if the fix is in place. Without authority at the lower tiers, every issue climbs and the higher tiers bottleneck. With authority, most issues close at tier one within a few minutes. The shop trusts that a tier-one responder will not be second-guessed for a reasonable call.
The third is measured response time. The system measures and posts response time at each tier, daily. The metric is not punitive; it is diagnostic. When response times drift up, the team examines why: too many concurrent signals, a missing tier-one responder, a procedural change that slowed the path. What does not get measured drifts upward.
The fourth is a no-blame discipline. The shop treats every signal as useful information and the worker who pulled it as someone who helped. Even a small sigh from a supervisor reading "another signal" trains the worker not to pull the cord next time. Lean shops with effective andon response usually drill this discipline explicitly during new-leader onboarding.
Together these four produce a system where a problem detected at a station becomes a fix in progress within minutes, and the data trail makes the root cause visible for follow-up.
Imagine a 25-person fabrication shop that installed andon lights at every station six months ago but has been disappointed in the results. Workers occasionally pull a signal but most issues still surface late, when defects reach inspection. The hardware works. The response does not.
The owner builds a real response system. He publishes an escalation tree: tier one is the team leader, target 90 seconds. Tier two is him, target 10 minutes. He gives the team leaders explicit authority to hold parts, swap fixtures, and call maintenance without his approval. He commits to never sighing or complaining about a signal, even when busy. He measures and posts daily response time on the production control board.
The first month is uneven. Workers test the system by pulling cords for small issues. The owner thanks them every time. By month two, signal volume has tripled, response time at tier one averages 75 seconds, and the team is solving 80 percent of issues at the station within five minutes. By month three, defects at inspection are down by half because they are being caught at the source. The hardware did not change. The response system did.
Andon response is the procedural counterpart to the andon signaling system and the physical andon cord that triggers it. It is operationalized through line stop authority, the rule that any worker can halt the work to flag a problem. Issues that exceed a tier's authority climb the tiered meetings cascade the same morning, so a problem detected at 9:32 can land in front of the right decision-maker before lunch.
The questions we hear most about this term.
Long-form guides that pick up where this definition leaves off, written for manufacturers running Arda today.
Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.