Menu
Jidoka vs Poka-Yoke: Stopping for Defects vs Preventing Them

Jidoka vs Poka-Yoke: Stopping for Defects vs Preventing Them

Poka-yoke prevents an error from happening. Jidoka stops the process the moment a defect occurs. Together they keep bad parts from ever moving downstream.
Jidoka vs Poka-Yoke: Stopping for Defects vs Preventing Them
Jidoka vs Poka-Yoke: Stopping for Defects vs Preventing Them

Key takeaways

  • Poka-yoke (mistake-proofing) prevents an error from being made in the first place.
  • Jidoka (autonomation) stops the process automatically the instant a defect is detected.
  • Poka-yoke is prevention; jidoka is detection plus an automatic stop.
  • Used together they stop defects at the source and keep bad parts from flowing on.

Short answer: Poka-yoke prevents the mistake — a fixture that only fits the right way, a sensor that blocks a missing step. Jidoka detects a defect or abnormality and stops the machine automatically so the problem is fixed before more bad parts are made. Poka-yoke stops the error; jidoka stops the line. Together they build quality at the source. See also oee for manufacturing.

What poka-yoke does

Poka-yoke (mistake-proofing) makes the wrong action impossible or instantly obvious. A part that physically only seats one way, an interlock that will not let the cycle start with a tool missing, a light that flags a skipped step — all prevent the defect before it can be made.

  • Makes the wrong action impossible or obvious.
  • Fixtures, sensors, interlocks, checklists.
  • Prevention, before the defect exists.

What jidoka does

Jidoka (autonomation) gives the machine the judgement to detect an abnormality and stop itself, signalling for help rather than producing scrap. It is the safety net for everything poka-yoke could not prevent — one bad part instead of a thousand.

  • Detects an abnormality automatically.
  • Stops the process and signals (andon).
  • Prevents mass-producing the defect.

A worked example

An assembly station has a poka-yoke fixture so a bracket cannot be fitted backwards — that failure mode is now impossible. But a supplier sends a batch of brackets a millimetre out of tolerance, which the fixture cannot catch. Jidoka does: a downstream gauge detects the out-of-spec dimension on the first unit and halts the line, so one part is flagged instead of a full shift of bad assemblies shipping. Poka-yoke handled the foreseeable error; jidoka caught the one that slipped through.

Why both matter

Poka-yoke cannot anticipate every failure mode; jidoka backs it up by stopping the moment something unforeseen slips through. Prevention plus an automatic stop means one defect, not a batch — which is why mature lines invest in both rather than choosing.

Building them in

Design poka-yoke at each workstation to make known errors impossible, and wire jidoka so the machine halts and calls for help on any out-of-spec signal. Both are quality-by-design, built into the process, not inspection bolted on after the fact.

Common mistakes

1. Relying on inspection instead. Catching defects later is slower and more expensive than preventing or stopping them.

2. Poka-yoke only. No safety net for the failure modes you did not foresee.

3. Jidoka stops nobody answers. An automatic stop only helps if the response is fast.

4. Treating a small jidoka stop as bad for OEE. It trades a tiny Availability hit for a huge Quality gain.

How it shows up in OEE

Jidoka trades a small Availability stop for a large Quality gain — far cheaper than scrapping a batch — which is why OEE Quality on jidoka lines stays high. Poka-yoke keeps the defect from ever entering the Quality calculation.

How Fabrico fits

Fabrico captures the stops and quality events these mechanisms generate, so you can see jidoka working and target where poka-yoke is still needed. Book a demo to see quality-at-source in your OEE.

Related reading

Frequently asked questions

Are poka-yoke and jidoka the same?

No — poka-yoke prevents the error; jidoka detects a defect and stops the line.

Does jidoka hurt OEE?

It costs small Availability stops but saves large Quality losses — net positive.

Is poka-yoke just sensors?

Any mistake-proofing counts — fixtures, shapes, interlocks and checklists included.

Which comes first?

Poka-yoke to prevent foreseeable errors; jidoka to catch whatever slips through.

Why not just inspect at the end?

End inspection is slower, more expensive, and lets defects accumulate before they are caught.

Latest from our blog

Încă te întrebi?
Verificați singuri!
Încă te întrebi?

Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!

By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy și Cookies Declaration