Sample frameDay 137·Leadership · Signals

Morning. Toyota gave every worker a cord that stops the line. You've given yours an open door and called it the same thing.

Leadership.

The Andon Cord

5 min read·Apply by lunch

The question

Somebody on your team sees the first sign of a real problem an hour before the work goes out to the client. Say exactly what happens next: the route they use, the person who answers it, and how long that person takes. If any of those three is a guess to you, it is a guess to them as well — and nobody stops the line on a guess. They wait to see whether it turns into something.

The idea

Taiichi Ohno spent his career inside Toyota, rising to executive vice-president, and set out the system he had built in a book published in Japan in 1978 and translated as Toyota Production System: Beyond Large-Scale Production (Productivity Press, 1988). Two pillars hold it up. Just-in-time is the famous one. The other is jidoka, usually rendered as automation with a human touch, and it descends from Sakichi Toyoda's automatic loom, which stopped itself the instant a thread broke rather than weaving hundreds of metres of flawed cloth. Ohno extended the same right to people: anyone who sees a defect can signal, and the line stops. Western managers reading this fixate on the cost of stopping. Ohno's position ran the other way — a line that never stops isn't a healthy line, it's a line where problems are being passed downstream to someone with less power to fix them. Two pieces of engineering sit underneath the principle, and both get lost in the retelling. The threshold is deliberately tiny, because a loom that waits for the cloth to be ruined has waited far too long. And the pull doesn't halt the plant; it summons a team leader inside the cycle, while the work already in front of the pull runs on for a moment. The pull is cheap because the response is fast.

The framework

01
Four lines, or it isn't a cord.
A cord is a mechanism, not a sentiment. Write down four things: what counts as grounds to stop, how a person signals it, who must respond, and what happens to the work in the meantime. Toyota's version is specific to the point of being boring — a fixed station, a lit board, a named team leader. Yours might be a channel that pages whoever is on call, or a standing right to send a deliverable back before it reaches the client. A standing invitation isn't a mechanism: it leaves the entire cost of judging whether this counts sitting on the least powerful person in the room.
02
How fast does help arrive?
Ohno's pull is cheap because help arrives inside the cycle. If your version means a raised problem sits in a channel for two days while everyone waits to see who owns it, you have installed a complaints box and called it a cord. So settle the answering first: who responds within the hour, who can authorise the work to stop, who tells the customer. Then exercise it cold, on a day when nothing is actually wrong, the way you would test an alarm. A mechanism nobody has ever used will not be reached for in the single hour it matters.
03
The threshold belongs at the first odd reading.
Jidoka's whole economy depends on stopping early. Toyoda's loom halted on one broken thread rather than on a ruined bolt of cloth, because checking at that moment costs seconds and checking two hundred metres later costs the run. Teams set the bar the other way up, at disaster — the client is about to walk, the release is about to fail — and by then stopping is expensive and the pull reads as an escalation. So write the threshold at the level of the small anomaly: the estimate that arrived with no caveat, the test that failed once and passed on a retry, the spec that changed in a meeting nobody minuted. Then say it plainly in the room. A pull over something small is not a false alarm; it is the mechanism working exactly as designed.
04
Decide now what happens to the work in flight.
What kills most cords isn't the reaction to the pull. It is that nobody knew what to do with the half-finished work while everything waited, so the person holding the cord had to make three decisions above their pay grade in order to raise their hand. Toyota answers this in the design: the line stops at a fixed point, the pieces already past it finish their cycle, and containment is somebody's named job. Write the same three answers for your version. What happens to the deliverable already with the client — recalled, flagged, or left alone? Who tells the people downstream still building on top of it? And when the clock is the casualty, does the date move or does the scope? Answer those on a calm Tuesday and the pull costs a minute.

Members only · 4 principles + template + AI mentor

364 more frameworks are waiting.

The Andon Cord is Day 1 of 365. One framework every morning for a year — across strategy, sales, negotiation, leadership, and more.

$1 /day

Billed $365/yr · cancel any time

365 frameworks

12 topics · templates · AI mentor

Reserve your place — $365/yr →

One payment a year · the whole library · no auto-renewal.

More Leadership frameworks

All 22 leadership frameworks →