Poka-yoke (Japanese for 'mistake-proofing') is the design of devices or methods that make it physically impossible to perform an operation incorrectly, or that detect an error the instant it occurs before a defect is created. Poka-yoke targets the error (the human mistake), not the defect (the resulting bad part). Prevent the error and the defect never exists.

What is the difference between an error and a defect?

An error is a human mistake — selecting the wrong part, forgetting a step, misreading a dimension. A defect is the result of an error that was not caught — an out-of-spec part, a missing fastener, an incorrect assembly. Poka-yoke breaks the chain between error and defect: either prevent the error entirely (prevention) or detect it instantly before a defect is produced (detection).

Does poka-yoke replace inspection?

It replaces after-the-fact inspection with at-the-source prevention. Traditional inspection finds defects after they are created — costly rework. Poka-yoke prevents defects from being created — zero cost. The ideal progression: judgment inspection (human catches defect) → informative inspection (SPC catches drift) → source inspection (poka-yoke prevents error).

Poka-Yoke Design: Making Errors Impossible

New to this topic?

We recommend reading these guides first to get the most out of this one:

FMEA for Practitioners Root Cause Analysis Toolkit

Error Types

Inspection Methods

Prevent

Best Level

Cost of Prevented Defect

Three Types of Human Errors

Error Type	Description	Aerospace Example	Poka-Yoke Response
Forgetfulness	Skipping a step or forgetting an action	Operator forgets to apply corrosion inhibitor before closing panel	Checklist with physical tokens: one token per step, cannot close panel until all tokens are returned
Confusion	Selecting the wrong item or performing the wrong action	Installing the left bracket in the right position (mirror parts)	Asymmetric mounting holes: part physically cannot install in wrong orientation
Lack of skill	Not knowing the correct method or standard	New operator applies sealant bead too thin because training was incomplete	Template/guide that controls bead width mechanically + visual go/no-go gage

The Poka-Yoke Hierarchy

Not all poka-yoke is equal. The hierarchy from weakest to strongest:

Level 1: Warning (Weakest)

A signal alerts the operator that an error has occurred, but does not prevent it. Example: a buzzer sounds if a torque wrench does not reach the target value. The operator can ignore the buzzer. Warnings rely on human compliance — they fail when people are rushed, tired, or habituated to the alarm.

Level 2: Control (Moderate)

The system detects the error and stops the process. Example: the machine will not cycle until the fixture sensor confirms the part is correctly seated. The operator cannot proceed with the error, but can potentially override or work around the control. Better than warnings but not foolproof.

Level 3: Prevention (Strongest)

The physical design makes the error impossible. Example: the connector only fits in one orientation (USB-C, unlike old USB-A). The fixture only accepts the part in the correct position. The fastener hole pattern is asymmetric so left cannot be installed right. No human decision, no override, no possibility of error.

💡 Always Aim for Prevention

When designing poka-yoke, always start at Level 3 and only fall back to Level 2 or 1 if prevention is physically impossible. A prevention poka-yoke is permanent — it works on every shift, with every operator, under every condition. Warnings and controls degrade over time as people learn to ignore or bypass them.

Three Inspection Methods

Method	Who Inspects	When	Poka-Yoke Fit
Source Inspection	The process itself	Before/during the operation	Best: fixtures, sensors, and physical constraints prevent errors before they create defects
Self-Check	The operator who performs the work	Immediately after the operation	Good: operator verifies their own work with a go/no-go gage or visual check
Successive Check	The next operator in the process	Before starting the next operation	Acceptable: catches defects at the next station rather than at final inspection

Practical Poka-Yoke Examples

Problem	Error Type	Poka-Yoke Solution	Level
Wrong fastener installed	Confusion	Kitting: pre-counted fasteners per station in labeled compartments. If any remain after install, something was missed.	Control
Panel installed backward	Confusion	Asymmetric locating pin pattern: panel only fits in correct orientation	Prevention
Missing sealant on hidden joint	Forgetfulness	UV-fluorescent sealant + UV light check: missed areas glow differently under black light	Control
Torque not reached on critical fastener	Lack of skill	Electronic torque wrench that locks out until target is reached + logs to database	Control
FOD left inside wing box	Forgetfulness	Tool shadow board at entry: all tools checked in before closeout. Cannot sign closeout card if any tool is missing from shadow board.	Control
Drilling wrong hole size	Confusion	Drill bushing plate: only correct-size drill fits through the bushing for each hole location	Prevention

🎯 The Bottom Line

Poka-yoke breaks the chain between human error and product defect. Target the three error types (forgetfulness, confusion, lack of skill) with the strongest level of proofing available (prevention > control > warning). Use source inspection whenever possible — prevent the error before it creates a defect, not after. Connect poka-yoke to your FMEA: for every high-severity failure mode, ask “Can we make this error physically impossible?” This completes Module C (Problem Solving & Quality). Next: Lean Leadership Behaviors — beginning Module D on the people side of lean that makes all the technical tools sustainable.

Keep Learning

📖

Guide

Lean Leadership Behaviors

📖

Guide

Coaching for Improvement

📖

Guide

FMEA

🏭

Free Process Modeler