Skip to main content
Mobius
Beginner

What is poka-yoke

Also known as: mistake-proofing, error-proofing, poka yoke, poka-yoke examples

Definition

Poka-yoke (Japanese for mistake-proofing) means designing a process so an error cannot happen or is flagged at once, like a SIM card that fits only one way.

Why it matters

Telling employees to be more careful does not prevent mistakes, because people will still slip.

Common mistakes

Assuming training alone is enough to prevent errors, rather than designing the system to prevent them.

Worked exampleIllustration

Three guards on one online order form

A small print shop takes orders through a web form, one guard for each of Shingo's detection methods.

  1. Contact method, control type

    The upload field accepts only PDF files, so a file in the wrong format cannot enter the order.

  2. Fixed value method, warning type

    The form counts the pages in the file and warns the customer when the count does not match the number of pages ordered.

  3. Motion step method, control type

    The payment button appears only after the customer approves the proof, so no job reaches the press before approval.

Each guard stops a slip before it becomes a defect. The customer can still make a mistake, but a wrong file, a wrong page count or an unapproved job never gets printed.

The idea in one picture

Control: the mistake cannot happen

Control: the mistake cannot happenCorrect inputOnly correctwork passesWrong input

Warning: the mistake is flagged at once

Warning: the mistake is flagged at onceWrong inputInstant alertFixed before itmoves on
Two ways to mistake-proof a step. Control shapes the step so a wrong input cannot enter. Warning lets the slip happen but signals at once, so it is fixed before it becomes a defect.

Three guards on one order form

Online order form

  1. Your file1. Contact method, control

    Only the file type the print shop works with can enter the order.

  2. Pages ordered2. Fixed value method, warning

    The form counts the pages in the file against the pages ordered.

  3. Proof, then payment3. Motion step method, control

    The pay button appears only after the proof is approved.

The print shop from the example. The two control guards make the mistake impossible, and the warning guard flags it at once.

Definition

A poka-yoke is a device or design feature that stops a mistake from turning into a defect. Shigeo Shingo described two types: the control type, which stops the process or makes the error impossible, and the warning type, which alerts the person doing the work. He also named three ways to detect an error: the contact method, which checks shape, size or colour, the fixed value method, which checks a count of parts or moves, and the motion step method, which checks that the steps happen in the right order. The name has a story. Around 1963 at Arakawa Auto Body, a device of this kind was called baka-yoke, fool-proofing. A worker was offended by the name and did not come back the next day, so Shingo renamed it poka-yoke, protection against the inadvertent mistakes anyone can make.

Why it matters

A poka-yoke stops the slip from becoming a defect that reaches the customer. Everyday examples: a microwave that will not run until the door is closed, a SIM card that fits only one way, and a form that checks the last digit of an Israeli ID number. That last digit is a check digit, calculated from the first eight, so a form that checks it catches most single-digit typos and most swaps of two neighbouring digits. In business, this looks like software fields that refuse a wrong format before submission.

Directly related: SOP, 5S, OEE.

Improvement tips

  • Design software forms that check for correct formatting, such as email addresses, before allowing submission.
  • Use physical color-coding or shapes so that parts or files can only fit together the correct way.
  • Add checklists that must be completed before a system will allow the next process step.
  • Start with your most frequent recent mistake and ask whether it can be made impossible, or at least flagged at once.
  • Use a warning when a full block would slow everyone down, and a block when the error is costly.

Common mistakes

  • Making the mistake-proofing mechanism so restrictive that it stops employees from doing their job efficiently.
  • Blaming employees for mistakes when the process allowed the error to happen in the first place.
  • Adding a guard against a rare, cheap error, which slows everyone down every day to prevent a small cost.

Related terms

Quick check

Which description fits Poka-Yoke?

Choose an answer

Frequently asked questions

Do I need to build mistake-proofing into my business before I launch?
You do not need complex mistake-proofing setups before you launch because you do not have running customer transactions yet. Focus on getting your first product ready and confirming that customers want to buy it. You can add simple guards to prevent errors once you have repeatable daily tasks.
How can a new startup design software forms to prevent customer errors?
You can use simple digital validation on your website contact and order forms, such as requiring a correctly formatted email address or phone number. This prevents clients from submitting incomplete information, which saves you from chasing down details later. It is a simple way to keep your data clean from day one.
How does mistake-proofing help me design a new service delivery workflow?
Design your service workflow by setting up step-by-step checklists that your team must complete before moving to the next stage. This ensures that essential actions, like checking a client's requirements, are not forgotten. It is a low-cost way to keep quality consistent as you start.
Do I need expensive custom software to mistake-proof my new startup?
You do not need expensive software or custom programming to prevent errors in a new business. You can use standard checkboxes, template validation, and simple physical color-coding to guide your tasks. The focus is on the design of the process, not the cost of the tools.
Why do my employees keep making the same operational mistakes despite training?
Mistakes repeat because training and telling staff to be more careful does not change the system that allowed the error. If a process allows an incorrect entry or missing file to pass through, human error will eventually happen. You must design physical or digital checks that prevent the mistake from proceeding.
How do I design a mistake-proofing mechanism for my digital invoicing process?
You can mistake-proof invoicing by using software templates that pre-fill client details and calculate tax totals automatically. Set up validation rules that require a purchase order number or manager approval before the invoice can be sent. This prevents billing errors and saves support time.
How do I avoid making my mistake-proofing steps too restrictive for my team?
Ensure your error-proofing is helpful and does not block your team from working efficiently. If a check is too slow or complex, employees will find workarounds to bypass it, which defeats the purpose. Focus on creating simple, automatic guards that guide the user rather than slowing them down.
How do I apply mistake-proofing to reduce product shipping errors?
You can reduce shipping errors by using physical safeguards like color-coded bins or barcode scanners that verify the product matches the order before packing. Creating a layout where items cannot physically fit in the wrong box is an excellent way to prevent mistakes. This keeps your shipping fast, with far fewer errors.
What does Poka-Yoke mean in simple terms?
Poka-yoke is a Japanese term for mistake-proofing: designing a process so a slip cannot happen, or is flagged at once, before it turns into a defect. An everyday example is a washing machine that will not start until the door is clicked shut. Shigeo Shingo chose the name as protection against the inadvertent mistakes anyone can make, so it is about the design, not about careless people.
Is mistake-proofing too complex or technical for a small retail shop?
It is not complex and can be applied to any small shop using simple, low-cost ideas. For example, using physical keys that only fit one lock or color-coding storage shelves are simple forms of mistake-proofing. It is about using common-sense designs to make work safer and easier.
Do I need a systems engineer to set up mistake-proofing in my company?
You do not need to hire an engineer or developer to prevent daily operational errors. You and your team can design simple checks, templates, and checklists because you know where mistakes usually happen. Start by looking at your most common recent error and brainstorming how to block it.
What is the risk of relying only on reminders and signs to prevent errors?
The risk is that reminders and signs do not stop mistakes, because humans naturally get tired, distracted, or busy during the workday. If the system allows a mistake to happen, it will eventually happen, leading to customer complaints and extra costs. Designing the process to block errors, or to flag them at once, is far more reliable.

Sources: Shigeo Shingo, Zero Quality Control: Source Inspection and the Poka-yoke System, Productivity Press, 1986, Israeli ID number check digit, Hebrew Wikipedia

Last reviewed: 2026-09-23

I have worked with

What Clients Say

From different fields, at different stages of business

Dan Manto

Eclipse Capital

Real Estate Investment and Finance, USA

Arty McLabin

GameReady

Game Development Education and Outsourcing, International

Anna, Beautician

Anna

Beautician

After I finished a cosmetology course at a leading company, I was confused. I didn't know how to open a business, what to sell from home, or how to bring in clients. Since I reached out to Mobius, everything has changed. We built an organized plan with clear steps and no unnecessary risks. Today I see results, and I'm growing and developing every month.

Mark, Massage therapist, Gan Yavne

Mark

Massage therapist, Gan Yavne

When I finished a massage course, I imagined a different world. I found out it's a hard field, and financial stability isn't easy to find. When I came to Mobius, something changed. We started an organized process and built a business plan. Without Mobius? I probably would have given up. Today I believe in myself and in my own path.

Operations slowing your business down?

Alex helps Israeli businesses fix the processes that waste time and money. The first call is free.

+972 055-248-6151. Better on WhatsApp: I am in meetings most of the day and answer as soon as I am free.