Poka-Yoke Designer (Mistake-Proofing)
Design defects out at the source. Poka-Yoke, mistake-proofing, builds simple devices and checks that make errors impossible or immediately obvious, so problems are prevented or caught before they become defects rather than found later by inspection.
Design Poka-Yoke →What is Poka-Yoke?
Poka-Yoke, Japanese for mistake-proofing, is a Lean technique developed by Shigeo Shingo for preventing errors from becoming defects. Its premise is that human mistakes are inevitable, so instead of blaming people, you design the process so the mistake cannot happen, or is caught the instant it does.
There are two levels of function. A prevention (control) poka-yoke makes the error physically impossible, for example a connector that only fits one way. A detection (warning) poka-yoke allows the error but signals it immediately with an alarm, light or stop, so it is corrected before it propagates. Prevention is always preferred to detection.
The classic implementation methods are the contact method (using shape, size or physical features to block errors), the fixed-value method (ensuring a set number of actions or parts, such as a count), and the motion-step method (ensuring steps happen in the correct sequence). Effective poka-yoke devices are typically simple and inexpensive.
In plain terms: People make mistakes; good design makes those mistakes impossible or impossible to miss. A SIM tray that only fits one way, a part that won't seat if a step was skipped, a light that flags a missing bolt, these are poka-yokes. The goal is to stop relying on 'be careful' and build the care into the process.
Two Functions, Three Methods
Prevention vs Detection
Prevention makes the error impossible (preferred). Detection lets it occur but signals it immediately so it is fixed before becoming a defect.
Contact Method
Uses physical shape, size, or features to block incorrect actions, such as asymmetric connectors or fixtures that only accept a correctly oriented part.
Fixed-Value & Motion-Step
Fixed-value ensures the right number of parts or actions (counts, kits). Motion-step ensures steps occur in the correct order, blocking or flagging out-of-sequence work.
Key Formulas
Designing an Effective Poka-Yoke
Always prefer prevention over detection, and detection over relying on later inspection. A device that makes the error impossible removes the defect entirely; one that only warns still depends on someone responding to the signal.
The best poka-yokes are simple, low-cost, and act at the point where the error occurs. Complexity and expense are signs to reconsider the design; the tradition of mistake-proofing favors clever simplicity, a notch, a jig, a sensor, over elaborate systems.
Assumptions & Validation
Specific Error Identified
The design targets a specific, understood error mode.
If violated: Identify the exact error and where it occurs before designing the device.
Prevention Considered First
Prevention options are explored before settling for detection.
If violated: Re-examine whether the error can be made physically impossible.
Point-of-Occurrence Action
The device acts where and when the error happens.
If violated: Move the check upstream to the point of the mistake, not downstream.
⚠️ Check assumptions first
Mistake-proofing works on specific, well-understood error modes, not vague quality problems. Designing a poka-yoke before pinpointing the exact error and where it occurs leads to devices that miss the real failure. Prefer prevention over detection wherever possible, keep the device simple and act at the point of occurrence, and never treat a warning device as equivalent to one that makes the error impossible.
When NOT to Use Poka-Yoke Designer
Unknown Root Cause
If the error mode is not yet understood, do root-cause analysis first; you cannot proof against an undefined mistake.
Process Variation, Not Error
For statistical process variation rather than discrete mistakes, control charts and capability tools apply.
Systemic Flow Problems
For waste rooted in flow or layout, value stream mapping and flow redesign are more appropriate.
Industry Applications
Assembly Error Prevention
Design fixtures and connectors so parts can only be assembled correctly and in the right order.
Missing-Part Detection
Use counts, kitting or sensors to ensure no component is omitted before a step completes.
Service & Data Entry
Apply validation rules, required fields and format checks that prevent or flag input errors at the source.
Safety Interlocks
Design interlocks that prevent operation unless guards and conditions are correctly in place.
Frequently Asked Questions
What is the difference between prevention and detection poka-yoke?
A prevention, or control, poka-yoke makes the error physically impossible, such as a connector that only fits one way, so no defect can occur. A detection, or warning, poka-yoke allows the error to happen but signals it immediately with a light, alarm or stop, so it is corrected before propagating. Prevention is always preferred, because detection still depends on someone noticing and acting on the signal.
What are the three poka-yoke methods?
The contact method uses physical shape, size or features to block incorrect actions, such as an asymmetric part that only fits one orientation. The fixed-value method ensures a set number of parts or actions, for example verifying a count or using a kit. The motion-step method ensures steps occur in the correct sequence, blocking or flagging out-of-order work. Each targets a different way errors arise.
Why does poka-yoke assume people will make mistakes?
Poka-Yoke starts from the premise that human error is inevitable and that blaming individuals does not prevent recurrence. Instead of relying on attention and training alone, it designs the process so mistakes cannot happen or are caught instantly. This shifts responsibility from the person to the system, which is both more effective and more respectful, since it removes the conditions that allow error.
What makes a good poka-yoke device?
An effective poka-yoke is simple, inexpensive, and acts at the point where the error would occur. It prevents the error where possible, or detects it immediately where prevention is not feasible, and it does so reliably without depending on operator vigilance. Complexity and high cost are warning signs; the tradition favors clever, low-cost solutions such as jigs, notches, guides and sensors.
How is poka-yoke different from inspection?
Traditional inspection finds defects after they are made, often far downstream, which is costly and lets bad units accumulate. Poka-Yoke acts at the source, either preventing the error entirely or detecting it the instant it occurs so it is corrected immediately. This source-level action is far more effective than end-of-line inspection at achieving low defect rates.
Can poka-yoke be used outside manufacturing?
Yes. The principle applies anywhere errors occur. In software and services, required fields, format validation, confirmation prompts and defaults are poka-yokes that prevent or flag input mistakes. In healthcare, connector designs that prevent wrong connections are a well-known example. Any process with identifiable error modes can be mistake-proofed using the same prevention-first logic.
Make Errors Impossible or Obvious
Design simple mistake-proofing that stops defects at the source. Free during Beta.
Design Poka-Yoke →