Rolling out mistake-proofing (poka-yoke)
A poka-yoke rollout designs simple devices and process features that make errors impossible or immediately obvious, so defects are prevented at source rather than caught by inspection. It targets the recurring human-error defects that training and vigilance alone never fully eliminate.
What it is
Poka-yoke, or mistake-proofing, is the use of physical or procedural features that either prevent an error from being made — a part that only fits one way, a fixture that rejects the wrong component — or signal it instantly if it is. A rollout makes this a standard response to recurring defects: rather than asking people to be more careful, the process is changed so the mistake cannot happen or cannot pass unnoticed.
Why it is done
Human errors are inevitable, and defects that depend on people not making them will recur no matter how much care is urged. Inspection catches some but is itself error-prone and adds cost. Mistake-proofing removes the reliance on vigilance by building the prevention into the process or equipment, which is cheaper and far more reliable than detection, and it permanently eliminates the defect rather than managing it.
How it is done
Recurring error-related defects are identified from quality and rework data, and for each the specific point and mechanism of the error are pinpointed. A simple device or feature is then designed to prevent that error or to make it immediately detectable — preferring prevention over detection, and the cheapest robust solution. The device is trialled, refined to ensure it does not slow the work or get bypassed, and then standardised and replicated to similar processes.
- Identify recurring errors
- Pinpoint the error point
- Design prevent or detect
- Trial the device
- Refine to not impede work
- Standardise and replicate
What to watch for
A device that slows operators down or is awkward will be defeated or removed, so usability is as important as the prevention. Choosing detection where prevention is feasible settles for catching defects rather than stopping them, and over-engineering simple problems wastes the effort poka-yoke is meant to save.
Related practices
Reducing changeover time with SMED
Optimising clean-in-place (CIP)
Running a process capability study
Related topics
Poka-Yoke (Mistake-Proofing) · Jidoka · Six Sigma
Common in: Food Processing · Pharmaceuticals · Dairy · Paper & Packaging · Brewing & Beverage