Problem Solving & Quality · Sustain

Poka-Yoke

Design a device that makes the error impossible or immediately visible — a keyed fitting, a sensor that stops the cycle, a jig that only fits one way.

Time1 h
FormatSmall group
StageSustain

Poka-Yoke: what it is and why it works

Poka-yoke, Japanese for mistake-proofing, is a device or design feature that prevents an error from happening or makes it immediately obvious so it can be corrected before it becomes a defect. There are two types. A control poka-yoke stops the process when an error is detected, so the cycle cannot continue. A warning poka-yoke signals the error with a light, sound or visual cue. There are also three detection methods: contact methods use shape or physical features such as pins, keys or guides; fixed-value methods count parts or operations; motion-step methods check that steps occur in the correct sequence.

Poka-yoke targets human slips: forgetting a step, reversing a part, picking the wrong item. Training, reminders and inspection cannot eliminate these, because they happen even to skilled, attentive people. Error-proofing turns an administrative control into an engineering one, which is why it sits high on the hierarchy of controls. Good devices are simple, cheap and robust, and designed with the operators who know how errors happen. The weak point is maintenance: a sensor that is bypassed or out of adjustment gives false confidence. That is why each device should appear in the control plan with a regular function check, and why it becomes part of standard work.

What you need

A precise description of the error and when it occurs
The verified cause showing that a human slip is involved
Operators and maintenance staff who know the task and the equipment
Basic knowledge of the part, tools and process sequence

What you get

A device or design feature that prevents or signals the error
Test evidence that the device catches the error when it is deliberately attempted
An entry in the control plan with a function check frequency
Updated work instructions and training

When to use it

When the root cause is a human slip that training alone will never remove.

How to do it, step by step

Identify the exact error: wrong part, missing step, wrong orientation, wrong setting, wrong sequence.
Choose the type: control (the process cannot continue) or warning (the error is signaled immediately).
Choose the method: contact (shape, pin, key), fixed value (count of parts or operations) or motion step (sequence check).
Build a simple, robust device, test it by deliberately trying to make the error, and involve the operators in the design.
Add the device to the control plan with a daily or per-shift function check.

Worked example: Wrong-tank chemical delivery at a water treatment plant

Illustrative scenario — figures are realistic but not from a real company.

A water treatment plant receives bulk deliveries of sodium hypochlorite and sulfuric acid by truck. Both unloading connections were identical camlock fittings on the same wall, labeled but side by side. A near miss occurred when a driver started connecting the acid hose to the hypochlorite fill line, which, if completed, could have released chlorine gas.

The error was defined: connecting a delivery hose to the wrong fill line. The team judged that labels and supervision were warning-level measures that depended on attention.
A control type was chosen: the error had to be physically impossible. Using the contact method, each chemical received a different, dedicated coupling that could not mate with the other.
Both fill connections were placed in separate lockable cabinets, color-coded and moved apart. The cabinet key was held by the plant operator, who opened only the correct cabinet after checking the delivery paperwork.
Operators and two regular drivers tried to connect the wrong hose on purpose during testing; it could not be done. The change went through the plant's management-of-change review.

Result. The unloading procedure and the control plan were updated, with a monthly inspection of couplings and cabinet locks. The chemical suppliers were informed so their trucks carried the correct dedicated couplings. There have been no wrong-connection attempts since. The team noted that a few hundred dollars of hardware replaced a risk that no amount of labeling could fully control.

Open it in the FieldKit Problem Solving app → Get the Problem Solving template pack — join the waitlist

Common pitfalls and how to avoid them

Designing a warning device where the error can still pass through unnoticed.Prefer a control device that stops the process for critical errors; use warnings only where a stop is impractical and the response is immediate.
Building a device that is complex, fragile or slows the cycle, so operators bypass it.Keep it simple and robust, and design it with the operators who will use it.
Assuming the device works forever after installation.Add a function check to the control plan, for example with a known bad part at the start of each shift.
Error-proofing the symptom rather than the actual error.Define the specific error that causes the defect, and target the point where it happens.

Frequently asked questions

What are the types of poka-yoke?

There are two types by function: control, which stops the process when an error occurs, and warning, which signals the error so it can be corrected. There are also three methods by how the error is detected: contact, based on shape or physical features; fixed-value, based on counting; and motion-step, based on the sequence of actions.

What is an example of poka-yoke?

Common examples include a fixture pin that allows a part to be loaded in only one orientation, connectors keyed so they cannot be plugged into the wrong socket, a counter that prevents a cycle from completing until all fasteners have been torqued, and a parts tray with one pocket per component so a missing part is visible. Everyday examples include fuel nozzles sized to fit only the right tank.

What is the difference between poka-yoke and inspection?

Inspection finds defects after they are produced, often by sampling, and depends on the inspector's attention. Poka-yoke acts at the source, preventing the error from happening or detecting it immediately at the point where it occurs, for every piece. Shigeo Shingo promoted poka-yoke as part of source inspection, aiming to reach zero defects by preventing errors from ever becoming defects.

Origin

Poka-yoke — Shigeo Shingo, 1960s, Toyota Production System; Zero Quality Control: Source Inspection and the Poka-yoke System, 1986.

Used in these playbooks

Customer complaint closure 4 weeks

Four weeks to answer a complaint the way customers expect: a structured 8D, a clean problem statement, causes of occurrence and escape, an error-proof fix and deployment to sister lines.

Related methods

More in “Sustain”

Verify the result, lock it into standards and spread the lesson so it never comes back.