Key takeaways
Poka-yoke is a Japanese term, coined by Toyota engineer Shigeo Shingo, for any device, fixture, or procedure that either makes a process error impossible or makes it instantly obvious. It eliminates defects at the source rather than catching them in downstream inspection, and is a core tool of the Toyota Production System.
Poka-yoke (pronounced PO-ka yo-KAY) translates roughly as avoid (yokeru) inadvertent errors (poka) .
The American Society for Quality defines it as "the use of any automatic device or method that either makes it impossible for an error to occur or makes the error immediately obvious once it has occurred." Shigeo Shingo formalized the technique inside Toyota in the 1960s, after redesigning an assembly step where workers kept forgetting to insert a small spring.
His fix was to stage springs in a placeholder before assembly, so a leftover spring proved a step had been skipped.
Shingo was careful to separate two ideas. An error is a human or process slip, things like a missed step, a wrong part, or a misorientation. A defect is what reaches the customer when an error escapes detection. Poka-yoke is the discipline of catching the error before it becomes a defect, ideally by designing the process so the error cannot happen at all.
Because most defects are not random. They cluster around a small number of error-prone operations: a part that fits in two orientations but only works in one, a torque spec that is right next to a similar one, a step that gets skipped under time pressure.
Inspection alone catches some of these, but inspection is itself error-prone and adds cost. Poka-yoke shifts the work upstream into the design of the fixture, jig, sensor, or instruction.
The financial case is straightforward. Research summarized by the Institute of Industrial and Systems Engineers puts the cost of poor quality in manufacturing at 5 to 35 percent of sales, averaging roughly 15 percent. Anything that prevents a unit from being scrapped or reworked goes straight to margin, and to the Quality factor of OEE.
Shingo classified mistake-proofing devices into three detection methods. Each can be deployed in a control form (which physically stops the process when something is wrong) or a warning form (which signals the operator and depends on their response).
| Type | What it detects | Typical mechanism | Shop-floor example |
|---|---|---|---|
| Contact method | Physical properties: shape, size, color, position | Limit switches, asymmetric fixtures, keyed connectors, vision check on color or fiducial | A locating pin that only lets a bracket sit in the correct orientation |
| Fixed-value (constant-number) method | Whether a required number of actions was performed | Parts counters, kitted trays, torque-count nutrunners, weight check | A bolt tray with exactly six recesses, empty when the operation is done |
| Motion-step (sequence) method | Whether the prescribed steps were done in the prescribed order | Sequence-locked PLC logic, light-curtain pick-to-light, software work instructions | A digital work order that will not unlock step four until step three is confirmed |
The classic example is the SIM card. It physically cannot go into the phone the wrong way, because one corner is chamfered. On the line, the contact method shows up as locating pins, asymmetric fixtures, tooling that will not close on an out-of-spec part, and increasingly as machine-vision checks that flag a missing component or wrong color before the next station accepts the unit.
Use this when an operation must happen n times. Kitted trays, parts counters, and torque counters all enforce the count. A simple instance: a packaging cell that will not advance until six labels have been peeled from the dispenser. A more advanced instance: a nutrunner that requires four good torque events on a flange and locks the cycle if it only gets three.
Sequence errors are common when a procedure has many small steps that look similar. Pick-to-light systems and sequence-locked digital work instructions are the modern motion-step poka-yoke. They are particularly powerful for changeovers, lockout/tagout, and complex assembly, where the order matters and a skipped step may not be visible until much later.
This is the most important design choice and the one engineers most often get wrong. The answer is almost always: prefer control over warning whenever the cost of the defect justifies it.
| Control poka-yoke | Warning poka-yoke | |
|---|---|---|
| What it does | Physically prevents the process from continuing until the error is corrected | Alerts the operator via light, buzzer, or message; the operator decides what to do |
| Best for | Safety-critical, high-cost defects, defects invisible to later inspection | Low-cost errors, ergonomic prompts, situations where stopping the line is worse than the defect |
| Risk | Nuisance stops if the sensor is unreliable | Alarm fatigue: operators ignore signals under pressure |
| Example | Press will not cycle unless both palm buttons are held | Andon light when a torque reading drifts toward the spec limit |
ASQ's framing is the simplest: control devices are for when an operator cannot be allowed to keep going; warning devices are for when they need to know but can still judge the situation.
Poka-yoke is usually discussed under quality, but its effects spread across the whole OEE calculation. Defects pull the Quality factor down directly. The rework and scrap they create also eat into Performance, because cells run extra cycles that produce no good units. And the line stops triggered by errors, missed parts, mispicks, jam-ups, register in the six big losses framework as defects and reduced speed.
A well-designed poka-yoke also reduces unplanned downtime, because many micro-stops are really tiny error-recovery events: a part jams because it was loaded the wrong way, an operator reverses a step, a sensor faults because a kit is short. Mistake-proof the load, and the micro-stop disappears.
Poka-yoke is not a standalone program. It is the countermeasure layer that other improvement tools call into:
Use this short checklist when you find a recurring defect.
Mechanical poka-yoke is still the gold standard at the workstation. But two things have changed.
First, machine vision is now cheap enough to be a poka-yoke in itself. A camera and a small model can verify that a label is present, a component is the right color, a connector is fully seated, or a weld bead is continuous, faster than any human inspection.
Second, the work order and the operator's instructions are software. That means sequence-locked checklists, contextual photos, and immediate feedback are now possible at any station with a phone or tablet, not just the ones with custom electronics. This is exactly where modern CMMS and smart factory platforms meet the poka-yoke principle.
Fabrico is a unified OEE plus CMMS system that connects directly to machine PLCs and uses computer vision to capture the true cause of downtime, including the micro-stops operators rarely log. That matters for poka-yoke for three reasons.
Want to see how the QR-enforced checklist and vision-attributed downtime look on a real line? Book a Fabrico demo and walk through your own defect data with our team.
Poka-yoke was developed by Shigeo Shingo, a Japanese industrial engineer and a pioneer of the Toyota Production System, in the 1960s. Shingo introduced the term as a more positive replacement for his earlier phrase baka-yoke ("fool-proofing"), reframing the technique as protection against inadvertent errors rather than operator stupidity.
Shigeo Shingo defined three detection methods: the contact method (which detects physical properties such as shape, size, or color), the fixed-value or constant-number method (which alerts the operator when a required number of actions has not been completed), and the motion-step or sequence method (which verifies that prescribed steps were performed in the prescribed order). Each can be implemented as a control device or a warning device.
A control poka-yoke physically prevents the process from proceeding when an error is detected, for example a press that will not cycle without both palm buttons. A warning poka-yoke signals the operator with a light, buzzer, or message but does not stop the process. Control is preferred for safety-critical or high-cost defects; warning is appropriate when stopping the line is more disruptive than the defect itself.
Poka-yoke directly lifts the Quality factor of OEE by preventing scrap and rework, and indirectly improves Performance by eliminating the micro-stops and re-runs that follow errors. Because the cost of poor quality in manufacturing averages around 15 percent of sales, even a small defect-rate improvement from poka-yoke flows straight to OEE and margin.
Yes. Mistake-proofing and error-proofing are the English terms for poka-yoke and are used interchangeably by ASQ and most lean practitioners. All three describe any device or method that makes an error impossible or makes it instantly obvious once it has occurred.
Yes. Software is a particularly clean implementation of the motion-step (sequence) method. Digital work instructions that unlock the next step only after the previous one is confirmed, QR-enforced checklists tied to a specific asset, and PLC interlocks that block a cycle until conditions are met are all software-level poka-yoke devices. Vision-system checks that flag missing or wrong components in real time are software-driven implementations of the contact method.
Login
Blog