Poka-Yoke / Error-Proofing
Updated 2026-09-11
INTRODUCTION
English translation pending.
CORE DEFINITION
Poka-yoke was developed by Shigeo Shingo within the Toyota production system. The method designs fixtures, forms, and interfaces so that a mistake either cannot be made or is detected at the moment it occurs, as with a connector that only fits one way. The core claim is that errors are inevitable in any human process, so reliability must be built into the design rather than demanded from attention and training. The qualification is that prevention costs design effort and can reduce flexibility, so it pays off most where an error is frequent, costly, or hard to detect later.
SCAFFOLDING EFFECT
Reduce cognitive load
- Error mapping: list the mistakes that recur at a step, ranked by frequency and cost. - Design choice: pick prevention for frequent errors and immediate detection for the rest. - Detection timing: move the check to the moment of the error rather than the end of the line.
Anchor fast decisions
Attention is a limited resource that fluctuates with fatigue and interruption, so any process relying on vigilance will fail at some rate. Physical or logical constraints remove the possibility of the error entirely, which eliminates that failure rate rather than merely reducing it. Where prevention is impossible, detecting the error at its source stops it from propagating into downstream work that would be far more expensive to redo.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Poka-yokeverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS