Key takeaways
Short answer: Poka-yoke and jidoka are both about catching defects at the source, but at different scopes. Poka-yoke is a concrete mechanism — a pin, a sensor, a fixture, a checklist gate — that stops one specific error from happening or makes it visible to everyone. Jidoka is the wider principle of autonomation: equipment that detects an abnormal condition and halts itself, plus the empowered operator culture around it, so a problem is never built into the next unit. Poka-yoke is often how jidoka is implemented. For the bigger picture, see OEE for manufacturing.
Poka-yoke — Japanese for mistake-proofing — is a device or design that makes a specific error impossible or instantly visible. The classic examples are physical: a part fixture that only accepts the component in the correct orientation, a connector that cannot be plugged in the wrong way, a counter that will not let the line advance until all six screws are detected. The genius of poka-yoke is its humility. It does not rely on training, attention, or willpower, all of which fail under fatigue and pressure. It engineers the mistake out, or forces it into the open the instant it happens. Each poka-yoke targets one failure mode, cheaply and reliably.
Jidoka is a higher-order principle, often translated as autonomation or automation with a human touch. Its rule: when an abnormality occurs, the machine — or the operator — stops the process immediately rather than continuing to produce. The idea dates to an automatic loom that halted itself when a thread broke, so it never wove flawed cloth. Jidoka separates human work from machine work: the equipment runs unattended until something is wrong, and only then does it demand attention. That stop is not a failure; it is the system refusing to manufacture scrap. Jidoka is therefore as much about culture and authority as about sensors.
The cleanest distinction: poka-yoke is a mechanism, jidoka is a principle. Jidoka says abnormalities must stop the line at the source; poka-yoke is frequently the concrete thing that detects the abnormality and triggers the stop. You can have a simple poka-yoke with no jidoka — a fixture that just prevents misassembly. And jidoka is realised through many poka-yoke devices plus the andon system and the authority to act. Think of jidoka as the policy and poka-yoke as one of the tools that enforces it. Confusing the two leads teams to install clever devices with no culture of stopping, or to preach stopping with no mechanisms to detect when they should.
An assembly station must install a left-hand and a right-hand bracket. Operators occasionally swap them under time pressure, and the defect is only caught at final test — after a dozen more units are built. First, add a poka-yoke: shape the two nests so each bracket physically fits only its correct position. The swap becomes impossible. Then extend it to jidoka: wire presence sensors so that if either nest is empty or wrong when the cycle starts, the station halts and lights the andon. Now the line cannot build the defect and cannot continue past a detected abnormality. One mistake, eliminated at the source by a device, governed by a stop-on-abnormality principle.
Reach for poka-yoke when you have a specific, recurring error with a clear failure mode — a part fitted backwards, a step skipped, a wrong component selected. It is the fast, cheap, targeted fix. Reach for jidoka as a design philosophy when you are building or rethinking a process and want quality enforced structurally rather than inspected in afterwards. In practice you do both: jidoka sets the expectation that the line stops on abnormality, and a growing library of poka-yoke devices makes that expectation real one failure mode at a time. The relationship is also why error-proofing pairs naturally with an andon signal.
Both ideas defend the quality factor of OEE by stopping defects at the source rather than discovering them at final inspection, where the rework has already consumed capacity. They connect directly to first pass yield: every error a poka-yoke prevents is a unit that passes clean the first time, lifting both the quality factor and rolled throughput yield. There is a short-term tension — a jidoka stop is downtime, which dents availability in the moment — but it trades a small planned stop now for a batch of scrap and rework avoided later. Net, source quality almost always wins.
Fabrico turns these stops and defects into data you can prioritise. When a jidoka stop or a caught error is logged with a reason code, Fabrico folds it into OEE and shows which failure modes recur most — so you know exactly where the next poka-yoke will pay off. It connects the quality losses on the floor to the maintenance and improvement work that removes them, closing the loop between detecting a problem and designing it out. Book a demo to see defect and downtime reasons ranked by impact.
Poka-yoke is a specific error-proofing device or design that prevents or exposes one mistake. Jidoka is the broader principle of giving machines and operators the autonomy to stop the process when an abnormality occurs. Poka-yoke is often one of the mechanisms that makes jidoka work.
Yes, in practice. Jidoka requires a way to detect abnormalities and trigger a stop, and poka-yoke devices are frequently what provide that detection. Jidoka is the policy; poka-yoke is one of the tools that enforces it.
Jidoka is often translated as autonomation, or automation with a human touch. It means equipment runs on its own but stops automatically when something is wrong, so a defect is never passed to the next step and human attention is only needed for abnormalities.
A part fixture that only accepts a component in the correct orientation, a connector that physically cannot be plugged in the wrong way, or a sensor that blocks the next step until all fasteners are detected. Each prevents one specific error.
Both protect the quality factor by stopping defects at the source, which raises first pass yield. A jidoka stop is brief downtime, but it prevents a larger batch of scrap and rework, so source quality generally improves OEE overall.
Connexion
Blog
