Poka-yoke: designing so the error cannot be made

In one line

Poka-yoke ("mistake-proofing") is any device or design that keeps a defect from being produced or catches it before it moves on.

What it is

Meyers and Stephens explain that, to guarantee one hundred percent quality products, defects must be prevented from occurring: poka-yoke are the innovations made to tools and equipment to install devices that prevent defects. Their examples work as a catalog of types:

Example from the book	What it does
If an operation was forgotten, the next one does not start	Prevents moving forward with a missing step
Problems from earlier operations are checked in later ones	Stops the defective product before it moves on
If there are problems with the material, the machine does not start	Avoids processing material that does not belong
Tools and fixtures that only accept the part in the correct orientation	Makes the wrong assembly impossible

The Universidad Icesi article places it within jidoka: preventing errors in the process by redesigning equipment, operations and products, avoiding human errors (poka-yoke) and process errors, with 100 percent inspection at the source.

How it is applied

1. Choose a defect that keeps repeating (Pareto helps you prioritize).
2. Find the root cause of the human or process error, with 5 Whys.
3. Choose the level of protection: prevent the error (make it impossible), detect it instantly (warning and stop) or, as a last resort, detect it at the next stage.
4. Test it with the operator at the workstation: if it can be bypassed, it will be bypassed.
5. Verify the result with data, before and after.

Real example

In the Ciudad Juárez case, the team used brainstorming and 5 Whys to arrive at three possible causes of missed deliveries and tested each one with a statistical test. One of them was the lack of poka-yokes. With poka-yokes, the average lead time went from 26.07 to 23.87 seconds, an improvement of about 2.2 seconds that turned out to be statistically significant. But rebalancing the line gave a bigger improvement (down to 20.73 seconds) and the fixtures barely moved the needle (25.64 seconds, no significant difference). The practical lesson: the poka-yoke worked, but it was not the dominant cause, and that is why the team went after the balancing first.

Another example, within a root cause analysis case, is a medical products line with poorly adhered labels: the solution was molds with the exact shape of the units placed on the conveyor, so that a misaligned unit could not move forward. It is developed in the article on root cause analysis.

Benefits

• It is one of the cheapest quality improvements: a guide, a sensor or a stop usually costs little.
• It does not depend on people's attention or memory.
• It reduces final inspection and rework.

Limitations to keep in mind

• It targets specific, repetitive errors; it does not replace the analysis of deeper causes.
• A poorly thought-out poka-yoke gets bypassed or disabled: it has to be designed together with the person who uses it.
• As the Ciudad Juárez case shows, it is worth testing its effect against other causes before investing.

In summary

Poka-yoke means designing the workstation, the part or the tool so that the error does not get through. It is one of the typical tools of the Toyota production system and of Lean.