Skip to content
Let ideas be heard and improvements last.
Gemy

Poka-Yoke examples: how to design mistake-proofing in production

In brief

Poka-Yoke lets a device catch the mistake instead of a person. The difference between a mistake and a defect, six design questions, fictional examples from the floor and how to prove that a Poka-Yoke works.

6 November 2026 · 5 min read

Sample company · demo dataRoll-out suggestions: target unit, similarity reason and status
Roll-out suggestions

The Lean Enterprise Institute lexicon defines Poka-Yoke as low-cost devices that prevent an operator from making a mistake or make a mistake visible at once; its error-proofing entry describes how such devices are built into a process. The jidoka principle in Toyota's account of its production system comes from the same root: when an abnormality occurs, the machine or the person stops and the mistake does not pass to the next station. The silent assumption of Poka-Yoke is this: people make mistakes, so the process must not depend on people not making them.

A mistake is not a defect

A mistake is an act: picking the wrong part, skipping a screw, entering a wrong value. A defect is the trace that mistake leaves on the product. Not every mistake becomes a defect, and that is exactly where Poka-Yoke starts. If the mistake is made impossible (prevention), the defect never occurs; if the mistake is caught at once (detection), the defect does not move to the next step. A defect caught at final inspection is no longer Poka-Yoke but inspection, and the most expensive option.

Six design questions

  • Which mistake? One mistake is chosen: wrong orientation, missing part, skipped step, wrong setting, mixed material, wrong dimension.
  • Where is the mistake born? The place where the mistake is made and the place where the defect is seen usually differ; the device is built at the first.
  • Prevention or detection? Prevention is always preferred; if impossible, detection with an immediate warning.
  • What does the device rely on? Shape and contact (the part fits only the right way), fixed count (the next step does not open until six screws are done), motion sequence (steps lock in order).
  • Can the device be bypassed? A Poka-Yoke the operator can skip gets skipped on a busy day; it must be impossible to bypass, or the bypass must be visible.
  • How will it be verified? After the device is installed, the recurrence of the same mistake is counted; an uncounted Poka-Yoke is a belief.

Fictional examples from the floor

  • Wrong orientation: on an assembly where a connector could be fitted either way, a small pin added to the housing lets it seat only the right way. The mistake cannot be made.
  • Missing part: the operator used to count eight screws. The screws were laid in an eight-pocket tray; with an empty pocket left, the product cannot go into the box. The mistake is visible.
  • Skipped step: the second check cannot start until the label is printed; the printer signal locks the next step. The sequence is enforced.
  • Mixed material: two similar raw materials were put in containers of different colours with differently shaped lids; the wrong container does not fit the wrong feed opening.
  • Wrong dimension: a fixed gauge instead of an adjustable stop; a dimension can only drift if the gauge itself changes.

The operator's idea

The best Poka-Yoke are not engineering projects but devices an operator builds during a lunch break, because the person who knows the mistake best is the one who makes it and struggles every day not to. That is why Poka-Yoke is one of the most productive record types in a suggestion system: the idea is small, the cost is low, the gain is measurable. The manager's job is not to say “something this simple?” but to count together how many mistakes the device prevented.

Proving that it works

A Poka-Yoke is accepted not on the day it is installed but at the end of a monitoring period. First the current frequency of the mistake is counted; the device is installed; within the set period the same mistake is counted again. If the count has not dropped to zero, the device is being bypassed or the mistake is born elsewhere. When the monitoring period ends, a second check follows: is the device still in place, is it still working? The same device is sent to areas with similar lines as a roll-out suggestion; each area applies, adapts or declines with a reason according to its own conditions.

Which mistake to start with

A device is not built for every mistake; an order is needed. The first candidate is the mistake that recurs most often and whose defect is noticed latest: a missing part that reaches the customer, a wrong orientation that cannot be seen after assembly. The second candidate is the mistake that touches safety; even if rare, it moves to the front. Quality records, customer complaints and the operator's sentence “we always pick this one wrong” provide the list ready-made. Keeping the list short matters: a team that builds and verifies one device a month is further ahead than a team that plans ten devices a month.

Sample company · demo dataNew Kaizen form: problem, work done and gain steps
New Kaizen form

How it is done in Gemy

  • Poka-Yoke is a record type: which mistake it prevents, its type, before and after photos; it is kept with a monitoring period and a follow-up check. The form belongs to the company, which adds and removes fields.
  • The record enters the approval flow the company has set up; the decision and reason at every step stay in the record's history.
  • If the company switches on roll-out, a successful Poka-Yoke can be sent to similar areas as a suggestion; each area applies, adapts or declines with a reason.
  • If the work instructions module is on, a step can carry a measurement limit; an out-of-limit value warns, and an action or tag can be opened from the failed run.

The product does not connect to machines and does not replace the physical device; it records the device, its evidence and its roll-out.

In short

Poka-Yoke lets a device catch the mistake instead of a person. A mistake is an act and a defect its result; the device is built where the mistake is born and, where possible, makes it impossible. Six questions guide the design: which mistake, where, prevention or detection, what it relies on, whether it can be bypassed and how it will be verified. The best devices are the operator's idea and are accepted with numbers at the end of a monitoring period.

Sources

You may copy and share this article with attribution (Gemy, https://www.gemydigital.com/en/blog/poka-yoke-ornekleri-uretimde-hata-onleme-nasil-tasarlanir).

Related posts

Cookies

Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.

Cookie policyPrivacy notice