Poka-Yoke (Error Proofing)
Poka-Yoke is a design approach that makes errors impossible or immediately detectable. It builds quality into the process rather than relying on inspection after the fact.
Poka-Yoke (Japanese: 'mistake-proofing') was developed by Shigeo Shingo as a consultant, first at Yamada Electric, and later became part of the Toyota Production System. The idea is simple: Design processes, tools, and fixtures so that errors either cannot occur or are detected instantly before they become defects.
There are two types: Prevention devices make it physically impossible to do something wrong (e.g., a USB connector that only fits one way). Detection devices alert the operator immediately when an error occurs (e.g., a sensor that stops the line if a part is missing).
Poka-Yoke shifts quality control from reactive inspection to proactive prevention. Instead of checking 100% of parts at the end of the line, the process itself guarantees correctness at each step.
The best Poka-Yoke solutions are simple and inexpensive: Guide pins, color coding, checklists, asymmetric shapes, or limit switches. They cost cents but prevent defects worth thousands.
Practical Example
An assembly line for electronic controllers has a step where 4 screws must be inserted. A Poka-Yoke fixture holds exactly 4 screws per cycle. If one screw remains in the fixture after assembly, a light signals the operator immediately. Missing-screw defects drop from 2.3% to 0%.
How Lean Shift Helps
In LeanShift's Muda analysis, you mark individual process steps with the waste type “Defects” and note what happens there. The summary counts the marked steps for each waste type. This shows you at which steps defects and rework occur. From these steps you trace the cause, because a Poka-Yoke solution is applied where the defect originates.
Frequently Asked Questions
Is Poka-Yoke only for manufacturing?
No. Poka-Yoke applies everywhere: Form fields that reject invalid input, checklists before surgery, software that prevents saving without required fields. Any process that can go wrong benefits from error-proofing.
What is the difference between Poka-Yoke and quality inspection?
Inspection finds defects after they happen. Poka-Yoke prevents them from happening in the first place. Inspection adds cost; Poka-Yoke eliminates the need for it.
How do you identify where Poka-Yoke is needed?
Analyze defect data and near-misses. Any step where human error occurs repeatedly is a candidate. Start with the highest-cost or highest-frequency defects for maximum impact.