Error Proofing (Poka-Yoke) is a design philosophy
aimed at preventing or detecting mistakes before they cause
defects or safety hazards—often by physically or procedurally
making errors impossible or obvious.
Some plugs only fit into the wall one way. You cannot push them in upside down even if you try. The plug is shaped so the mistake is not possible. That is the trick: instead of asking you to be careful, the thing itself is built so you cannot mess it up. Seatbelts that click only the right way work the same way.
Mistake-Proof Design
Poka-yoke is a Japanese phrase meaning "mistake-proofing." The idea is simple: instead of telling people to be more careful, change the design so the mistake is impossible or instantly obvious. A USB-C plug fits either way, so you cannot insert it wrong. A microwave will not run with the door open. A gas pump shuts off when your tank is full. The designer moves the safety job from the human's attention onto the object itself, because people will always slip but well-designed things will not let them.
Designing Out the Mistake
Poka-yoke (Japanese for "mistake-avoiding") is a quality method developed at Toyota that shifts error prevention from human vigilance to system design. The premise: people will always make mistakes, so instead of training them not to, build the system so mistakes are impossible, immediately visible, or automatically stopped. There are three flavors: prevention (a part shaped so it can only fit one way; a SIM card that only seats in one orientation), warning (an alarm beeps when something is wrong), and shutdown (the machine stops automatically if something goes wrong). Shigeo Shingo formalized it in the 1960s after noticing that catching defects through inspection is too late — the waste already happened. Cheaper to make the mistake unmakeable in the first place. The idea now shows up in healthcare (color-coded syringes), software (form validation), and consumer products everywhere.
Poka-yoke (Japanese for "mistake-avoiding" or "foolproofing") is a quality-engineering methodology, formalized by Shigeo Shingo at Toyota in the 1960s, holding that human errors in manufacturing, assembly, operation, or data entry can be prevented or detected by constraining system design so the error is either physically impossible or immediately obvious. The deeper commitment is to shift the burden of error prevention from human vigilance to system design: rather than training operators to never err (cognitively impossible at scale), engineer the artifact, process, or interface so that mistakes are blocked at the source. Three detection modes are canonical. Prevention poka-yoke makes the error physically impossible — asymmetric connectors that can only seat one way, parts shaped to fit a single orientation, interlocks. Warning poka-yoke signals an error so the operator notices and corrects — alarms, indicator lights, distinctive sounds. Shutdown poka-yoke halts the process automatically when an error is detected, preventing propagation. The mechanism works because it redistributes responsibility: instead of a single inspector tasked with catching all errors (impossible given attention limits), the system enforces correctness at the point of operation. The discipline has spread far beyond manufacturing: healthcare (medication errors prevented by color and shape coding), software UI (input validation), aviation (checklists and interlocks), and consumer products (auto-shutoff appliances, fuel-pump nozzles).
Focuses on immediate feedback or structural
constraints so that an operator or user cannot inadvertently do the
"wrong" thing, or they'll be alerted immediately.
Rather than extensive training or
complicated instructions, the system's design physically or
logically prevents key errors—bypassing the need to rely on
memory or perfect vigilance.
Reveals a design-constraint approach: if a
mistake is physically or procedurally blocked, humans or machines
naturally stay on the correct path without mental overhead.
A car that won't start unless the driver's foot is on
the brake (automatic transmission models) is an error-proofing
measure preventing unintentional movement.
Parents (2) — more general patterns this builds on
Error Proofing (Poka-Yoke)is a kind ofConstraint — Error Proofing is a kind of constraint: the system is designed so that error states are physically inadmissible or immediately detected.
Error Proofing (Poka-Yoke)is a kind ofFail-Safe — Error proofing is a specialization of fail-safe in which the safe default is achieved by making the unsafe input physically impossible or immediately obvious.
Path to root: Error Proofing (Poka-Yoke) → Constraint
Error Proofing prevents errors from occurring or catches them before impact. Validation checks whether a product meets specifications. One prevents; the other checks.
Error Proofing (Poka-Yoke) and Presentism differ in their structural focus and domain of primary application.
Error Proofing (Poka-Yoke) and Confounding differ in their structural focus and domain of primary application.