Home › The Garage › Poka-yoke
Lean

Poka-yoke: error-proofing

Poka-yoke means building the process so the mistake is hard to make and impossible to pass on unnoticed. It beats “try harder” every time, because it fixes the system, not the person.

By LeanBean · Updated November 2026 · 5 min read
What's in this guide
  1. What poka-yoke is
  2. Warning vs control
  3. How to design one
  4. Where it fits in Lean
  5. Common questions
Mistake happens Warning: alert the operator Control: block it entirely May still slip through Cannot pass A control method is stronger than a warning: it removes the chance of the error entirely.
A warning tells you something is wrong; a control makes the wrong thing impossible. Prefer controls.

What poka-yoke is

Poka-yoke is a Lean technique for error-proofing (or mistake-proofing) a process: designing it so a defect either cannot be made, or cannot move downstream without being caught. The insight is that most errors are not carelessness — they are a process that quietly allows the wrong action. Rather than ask people to be more careful, you change the process so the careful outcome is the only one available.

Warning vs control

How to design one

Start where a root cause analysis or a Gemba walk has shown a recurring error. Then ask, in order: can we eliminate the step that allows the error? If not, can we replace it with something more reliable? If not, can we make the error impossible with a control? Only if none of those work do you fall back to a warning. Each level down is weaker, so you climb as high as the process allows.

Where it fits in Lean

Error-proofing is cheaper than inspection
Catching a defect at the end with inspection is waste — it adds cost and still lets some defects through. A poka-yoke moves the catch to the moment the error would occur, where it costs almost nothing and nothing escapes. That is why error-proofing sits at the heart of a flowing, low-waste process.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

The Garage — a community of practice

The Garage is where Lean, process and AI-readiness practitioners learn in the open — short lessons, real examples, and a place to compare notes. Join the community: follow along, try it on your own work, and share what you find.

Common questions

What does poka-yoke mean?

It is a Japanese term for mistake-proofing: designing a process so an error either cannot be made or cannot pass downstream unnoticed. The aim is to fix the system that allows the mistake, rather than relying on people to be more careful.

What is the difference between a warning and a control poka-yoke?

A warning alerts someone that an error has occurred (a light or beep) and depends on them acting. A control physically prevents the error or stops the process until it is fixed. Controls are stronger because they remove the possibility of the error, not just flag it.

Can you give a simple poka-yoke example?

A plug that only fits its socket one way, a form that will not submit with a required field blank, or a fixture that will not clamp a part in the wrong orientation. Each makes the wrong action impossible rather than merely discouraged.

How does poka-yoke relate to Six Sigma?

Error-proofing is often used in the Improve and Control phases of DMAIC to lock in a fix: once the root cause is known, a poka-yoke stops the defect recurring without relying on inspection or vigilance.

Related guides: Root cause analysis · The 8 wastes of Lean · Standard operating procedures