Academy→Continuous Improvement→Poka-Yoke — Error Proofing
Poka-Yoke — Error Proofing
Poka-yoke (Japanese for "mistake proofing") is a lean quality technique that designs processes and equipment so that errors are either impossible to make or are immediately detected and signalled before they cause a defect. It shifts defect prevention from human vigilance to process design.
Why companies use it
- ·Eliminates defect categories permanently, without relying on operator attention or inspection
- ·Reduces inspection costs by making the process self-detecting
- ·Required by IATF 16949 for zero-defect initiatives — OEMs increasingly demand poka-yoke evidence in PFMEA
- ·In safety-critical applications (automotive, medical, aerospace), poka-yoke is often mandated for high-severity failure modes
What hiring managers look for
- ·Poka-yoke thinking separates engineers who react to defects from those who design them out
- ·Being able to design a poka-yoke solution for a specific failure mode is a practical, demonstrable skill
- ·Understanding the hierarchy (prevention poka-yoke > detection poka-yoke > inspection) shows quality maturity
- ·Experience implementing poka-yoke at the design stage (DFM) versus retrofitting to a production process both have value
Typical interview questions
What is the difference between a prevention poka-yoke and a detection poka-yoke? Which is preferable?
Give three examples of poka-yoke from everyday products you use.
How would you design a poka-yoke for an assembly step where a connector can be plugged in upside-down?
What is the link between poka-yoke and the Detection column in a PFMEA?
Describe a poka-yoke you have designed or implemented in a production process.
Common mistakes
- ·Relying on visual inspection or operator checklists as poka-yoke — these are detection controls, not error-proofing
- ·Designing poka-yoke that slows the process significantly — the best solutions are invisible to the operator in normal operation
- ·Not validating the poka-yoke by deliberately introducing the error and confirming it is caught
- ·Implementing detection poka-yoke (alarm when error occurs) when prevention poka-yoke (make the error physically impossible) is achievable
- ·Adding poka-yoke to a process without understanding why the error occurs in the first place
Real engineering example
Related interview guides
Related topics
More in Continuous Improvement
Preparing for an interview?
Browse our role-specific interview guides written by engineers who know what hiring managers at ASML, NXP, and Philips look for.
Browse Interview Guides →