Poka-Yoke Design: Making Errors Impossible

Design error-proofing that stops defects at the source: three types of human error, three inspection methods, the poka-yoke hierarchy, examples.

14 min read 4 sections Guide 15 of 20, Lean Master Practitioner Updated

Poka-yokeMake the wrong way impossible, not just warned against

New to this topic?

Read these first to get the most out of this guide:

3
Error Types
3
Inspection Methods
Prevent
Best Level
$0
Cost of Prevented Defect

Three Types of Human Errors

WHY 1WHY 2WHY 3WHY 4ROOT
5 WhysAsk why until the answer is something you can fixThe 5 Whys guide
Error TypeDescriptionAerospace ExamplePoka-Yoke Response
ForgetfulnessSkipping a step or forgetting an actionOperator forgets to apply corrosion inhibitor before closing panelChecklist with physical tokens: one token per step, cannot close panel until all tokens are returned
ConfusionSelecting the wrong item or performing the wrong actionInstalling the left bracket in the right position (mirror parts)Asymmetric mounting holes: part physically cannot install in wrong orientation
Lack of skillNot knowing the correct method or standardNew operator applies sealant bead too thin because training was incompleteTemplate/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:

TARGET
Improvement stepsSmall experiments step up toward the target condition, one rung at a timeThe Improvement steps guide

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

The constraintOutput is set by the constraint; an hour lost there is lost for the systemThe constraint guide
MethodWho InspectsWhenPoka-Yoke Fit
Source InspectionThe process itselfBefore/during the operationBest: fixtures, sensors, and physical constraints prevent errors before they create defects
Self-CheckThe operator who performs the workImmediately after the operationGood: operator verifies their own work with a go/no-go gage or visual check
Successive CheckThe next operator in the processBefore starting the next operationAcceptable: catches defects at the next station rather than at final inspection

Practical Poka-Yoke Examples

S × OD
FMEARPN = severity × occurrence × detectionThe FMEA guide
ProblemError TypePoka-Yoke SolutionLevel
Wrong fastener installedConfusionKitting: pre-counted fasteners per station in labeled compartments. If any remain after install, something was missed.Control
Panel installed backwardConfusionAsymmetric locating pin pattern: panel only fits in correct orientationPrevention
Missing sealant on hidden jointForgetfulnessUV-fluorescent sealant + UV light check: missed areas glow differently under black lightControl
Torque not reached on critical fastenerLack of skillElectronic torque wrench that locks out until target is reached + logs to databaseControl
FOD left inside wing boxForgetfulnessTool 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 sizeConfusionDrill bushing plate: only correct-size drill fits through the bushing for each hole locationPrevention

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.

Frequently asked questions

What is poka-yoke?

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).

Share this guide: LinkedIn X Follow SymplProcess on LinkedIn

Take this to a room

The running order

For engineers designing error-proofing. They should leave designing at the prevention level by default and using source inspection.

7 beats · 12 min
  1. 1

    Three kinds of human error

    Naming them changes what you design against, because each has a different fix.

    • Forgetfulness: the step was known and skipped.
    • Confusion: two things looked alike, or the sequence was ambiguous.
    • Lack of skill: the person had not been properly taught.
    • Only the third is a training problem.

    Ask the room Which of the three caused our last defect?

  2. 2

    Break the chain, do not blame the link

    Poka-yoke breaks the connection between a human error and a product defect.

    • Humans will make errors. That is not a policy question.
    • The design question is whether an error becomes a defect.
    • A device that works on every shift, with every operator, is worth more than any amount of care.
  3. 3

    Three levels, always reach for the top

    Warning, control, prevention. Start at prevention and only fall back if it is physically impossible.

    • Warning: a buzzer when torque misses. The operator can ignore it.
    • Control: the machine will not cycle until the sensor confirms the part is seated. Can be overridden.
    • Prevention: the connector only fits one way. There is nothing to override.
  4. 4

    Why prevention is different in kind

    It is not just stronger. It is permanent in a way the other two are not.

    • Warnings and controls degrade as people learn to ignore or bypass them.
    • A prevention device works under every condition, forever, with no compliance required.
    • USB-C versus the old USB-A is the example everyone in the room already knows.

    Ask the room Which of our devices could a determined person work around?

  5. 5

    Three inspection methods

    Where you inspect matters as much as how.

    • Judgement inspection: at the end, sorting good from bad. Weakest.
    • Informative inspection: feedback to the previous step. Better.
    • Source inspection: check the condition before the error occurs. Best.
  6. 6

    Source inspection is the goal

    Prevent the error before it creates a defect, rather than detecting the defect afterwards.

    • Check that the fixture is right, not that the part came out right.
    • Verifying conditions beats verifying outputs.
    • The cheapest defect is the one that never happened.
  7. 7

    Connect it to the FMEA

    A concrete link that gives you a work list instead of a philosophy.

    • For every high-severity failure mode, ask: can we make this error physically impossible?
    • That is the highest-value error-proofing backlog you will ever have.
    • Prevention reduces occurrence, which beats improving detection every time.

    Ask the room What are our top three severity items, and could any become impossible?