
Definition
Poka-yoke is a mistake-proofing technique that designs a process or device so a human error either cannot happen or is caught immediately. The Japanese term means ‘mistake-proofing’. It was developed by Shigeo Shingo as part of the Toyota Production System.
Shingo first coined the term baka-yoke, meaning ‘fool-proofing’, then renamed it poka-yoke after a worker objected to the word fool. The principle is that errors are inevitable, so the process must be built to stop them reaching the customer.
A poka-yoke device either stops the process when something is wrong (a control type) or warns the operator (a warning type). Shingo grouped the detection methods into three approaches:
A good poka-yoke is cheap, simple, and built into the work itself, so it needs no extra attention to function.
Poka-yoke moves quality control from detection after the fact to prevention at the source. Because a defect is stopped at the step where it would occur, it never reaches the next operation or the customer, which cuts scrap, rework, and warranty cost. It also reduces reliance on operator vigilance over long, repetitive shifts.
The Lean Enterprise Institute treats poka-yoke as a core lean method for building quality into the process rather than inspecting it in afterward. Under ISO 9001:2015 clause 10.2, an error-proofing device is often the action that prevents a non-conformity from recurring, so it commonly closes out a CAPA investigation.
Both keep defects from reaching the customer, but they act at different points. Inspection checks parts after a step is complete and depends on a person noticing the fault, so it catches defects without preventing them. Poka-yoke is built into the step itself, so it removes the chance of error or flags it instantly. Shingo argued that inspection alone can never reach zero defects, because it relies on human judgement, whereas error-proofing the process can.
Checks parts after the operation and relies on a person spotting the fault. It finds defects that already exist, so a missed check lets the defect pass to the next step.
Built into the step so the error cannot happen or is caught the instant it does. It does not depend on operator attention, which is how it drives defect rates toward zero.
References