Poka-Yoke

Also called Mistake-Proofing, Error-Proofing, Baka-Yoke

Quick answer

Poka-yoke is a Japanese term for mistake-proofing: a mechanism built into a process that prevents a human error, or makes it visible at once, before it becomes a defect. Shigeo Shingo formalized it as part of the Toyota Production System in the 1960s. A common example is a car that will not start until the clutch pedal is pressed.

~20 sec read

011 min

Poka-Yoke at a glance

  • What it is: a device or step that stops a mistake, or flags it immediately, where the mistake happens.
  • Origin: Shigeo Shingo, who applied the term in the 1960s while working on Toyota's production system.
  • Two kinds: control devices make the mistake impossible; warning devices alert the person.
  • What it costs: a lockout that blocks legitimate work gets removed. Drivers rejected GPS lockouts and the feature was largely abandoned.
  • Where it stops: it fits mistakes that follow a known pattern, not judgment calls.

021 min

The problem Poka-Yoke responds to

A defect is a product or result that does not meet its specification. For decades, factories dealt with defects by inspecting work after it was done. Shigeo Shingo, an industrial engineer, concluded that this approach could never reach zero defects.

Kumar and Watt, in a teaching paper from the University of North Texas, report that Shingo was a leading proponent of statistical process control in the 1950s. Statistical process control checks a sample of the output and uses the result to judge the whole process. The paper says Shingo became frustrated with the statistical approach because he realized it would never reduce product defects to zero. The reason is simple. A sample leaves some products untested, so some defects always reach the customer.

The Lean Enterprise Institute (LEI), which publishes guides to lean manufacturing, makes the same point. It says that sampling inspection guarantees defects, because samples of parts or products will not always contain the defects that exist in total production.

Checking every unit does not solve the whole problem either. The check happens after the work, so the defect already exists, and the person who made it has often moved on to the next task.

Poka-yoke addresses that weakness by acting when the mistake happens.

033 min

How Poka-Yoke actually works

Poka-yoke starts from a distinction. A mistake is a human slip, such as forgetting a part. A defect is a mistake that reaches the customer. Shingo distinguished between inevitable human mistakes and defects in production. He did not try to stop people from slipping. He designed the process so that a slip is noticed and corrected immediately, before it can turn into a defect.

Wikipedia's entry on the term defines a poka-yoke as any mechanism in a process that helps an equipment operator avoid mistakes and defects by preventing, correcting, or drawing attention to human errors as they occur. The word "mechanism" is broad on purpose. It can be a metal fixture, a sensor, a software check, or a change in the order of work steps.

Control and warning devices

Every poka-yoke does one of two jobs.

TypeWhat it doesExample
Control (also called shutdown)Makes the mistake impossible, or stops the processA machine will not start if a work piece is set incorrectly
WarningAlerts the person with a light, buzzer or message, and leaves the decision to themA buzzer sounds when a part is missing

LEI says shutdown devices are the most powerful kind, and that a warning alerts people to something abnormal by a buzzer or light. Wikipedia describes the same split in Shingo's terms: either the operator is alerted when a mistake is about to be made, or the poka-yoke device actually prevents the mistake from being made.

Three ways to detect the mistake

Shingo recognized three methods for detecting and preventing errors in mass production.

  • Contact method: tests the product's shape, size, color, or another physical attribute. A fixture that only holds a piece in the correct orientation is an example.
  • Fixed-value method: alerts the operator if a set number of movements has not been made. A digital counter that tracks the number of spot welds on each piece is an example.
  • Motion-step method: checks whether the prescribed steps of the process were followed in order.

Why the check happens at the step

Shingo's term for this placement is source inspection. Kumar and Watt describe it as a check that detects an error before it becomes a defect. The alternative, judgment inspection, happens at the end of the process. There, a person or machine compares the product with a standard and rejects what does not conform, but it cannot prevent the defect from occurring.

Kumar and Watt list four elements of Shingo's Zero Quality Control system: source inspection, 100 percent inspection, immediate feedback, and poka-yoke devices. The devices are what make the other three affordable. A device checks every unit at every step, and it does so without a person's attention.

041 min

Where the term Poka-Yoke comes from

Wikipedia records that the term poka-yoke was applied by Shigeo Shingo in the 1960s to industrial processes designed to prevent human errors. Shingo was an industrial engineer who worked on the Toyota Production System, the production method Toyota built around eliminating waste and stopping to fix problems.

The name has its own history. The term was first baka-yoke, which means fool-proofing, and the name was changed to the milder poka-yoke. The new word comes from a phrase in shogi, the Japanese board game similar to chess. It describes a term in shogi that means avoiding an unthinkably bad move. The change in wording matters. It places the cause of the error in the process, not in the intelligence of the person doing the work.

Shingo wrote the method up in a book, Zero Quality Control: Source Inspection and the Poka-Yoke System, whose English edition is dated 1986 by its publisher, Routledge. The publisher says Shingo provides 112 specific examples of poka-yoke development devices on the shop floor, most of them costing less than $100 to implement. That detail explains why the method spread. It rewards small, cheap changes made by the people who do the work.

052 min

Example: the missing spring in a small switch

The best-known example comes from Shingo himself. Wikipedia's account says Shingo redesigned a process in which factory workers, while assembling a small switch, would often forget to insert the required spring under one of the switch buttons.

The fix did not ask workers to pay closer attention. In the redesigned process, the worker would perform the task in two steps. First they prepared the two required springs and placed them in a placeholder. Then they inserted the springs from the placeholder into the switch. When a spring remained in the placeholder, the workers knew that they had forgotten to insert it and could correct the mistake effortlessly.

Three things make this a clean example.

  • The device is a tray. It has no electronics and no software.
  • The check is a physical fact. A spring is either in the tray or in the switch.
  • The feedback is immediate. The worker sees the leftover spring while the switch is still in their hands.

This device is a warning type, because it shows the mistake and leaves the correction to the worker. A control type for the same job could be a fixture that refuses to release the finished switch until the tray is empty.

LEI lists further common examples. Product designs have physical shapes that make it impossible to install parts in any but the correct orientation. Photocells above parts containers stop a product moving to the next stage if the operator's hands have not broken the light to obtain the necessary parts.

062 min

How Poka-Yoke shows up in product and engineering work

Poka-yoke began on factory floors, but the logic applies wherever a person repeats a step and a wrong move costs something. Wikipedia lists forcing function and behavior-shaping constraint as other names for the idea. Software teams know the same idea as a forcing function: an action that cannot continue until a condition is met.

A real software case is the Git version control tool. The Git documentation says that git push will refuse to update a branch that is not an ancestor of the commit being pushed. In plain terms, Git refuses a push that would erase commits other people already shared. A second option, --force-with-lease, allows the overwrite only if the remote branch is still in the state the user expected. The documentation explains why: blindly pushing with --force will lose another person's work. Git does not trust the user to remember. The tool checks the condition for them.

A decision for a product manager

Say a product manager reviews a form where users can delete a project. Support reports show that some users delete the wrong project. Training the users or adding a warning paragraph treats the person as the problem. The poka-yoke choice is to change the step itself. For example, the form can show how many items the project holds and require the user to type the project name before the delete button works. The decision for the manager is to accept a slower delete path in return for removing a whole class of mistakes.

A decision for an engineer

In a second case, a staff engineer reviews a deployment script that takes an environment name as free text. A typo sends a test build to production. The poka-yoke options range from weak to strong. The script can print the target and ask for confirmation, which is a warning. It can accept only names from a fixed list, which makes a typo impossible. It can refuse to run against production unless the build passed its checks, which is a control. The engineer picks the strongest option that does not block legitimate work.

071 min

What Poka-Yoke costs, even done right

Every control device removes a choice, and sometimes the removed choice was the right one. Someone has to decide in advance which cases the device blocks. That decision is made by the designer, but the cost falls on the person doing the work on the day the device is wrong.

Wikipedia's article gives a documented case. When cars first shipped with on-board GPS systems, a forcing function stopped the driver from interacting with the GPS, for example by entering a destination, while the car was in motion. The goal was to keep the driver's attention on the road. Wikipedia reports that many drivers found this feature irksome, and the forcing function has largely been abandoned.

Three further costs follow from the same logic.

  • Design effort. Someone must study how the mistake happens before choosing a device. A device aimed at the wrong step adds friction and prevents nothing.
  • Bypassing. A device that gets in the way of legitimate work invites workarounds, and a bypassed device gives less protection than having no device, because everyone believes it is still active.
  • Warning fatigue. A warning that sounds on every normal cycle is soon ignored, so a rare real mistake gets no reaction.

081 min

When Poka-Yoke is the wrong tool

Wikipedia notes that forcing functions are very effective in safety-critical situations, but can cause confusion in more complex systems that do not inform the user of the error that has been made. That is the first limit. A device that blocks an action without saying why leaves the person guessing. Every blocking device should state the reason on screen or on the part.

The second limit is the kind of error. Poka-yoke works on mistakes that follow a known pattern at a known step, such as a forgotten part, a swapped part, or a skipped step. It does not help with errors of judgment, where the person has to weigh several options and no single rule defines the right answer. A device cannot decide whether a design is good or a diagnosis is correct.

When a mistake cannot be blocked, other tools fit better. A checklist helps with steps that have a fixed order but no way to be enforced by the equipment. Error recovery, such as an undo command, helps when mistakes cannot be predicted and the damage can be reversed. Training and review help where the work is judgment.

091 min

Applying Poka-Yoke

Say a support team pastes the same account number into two systems, and about once a week a digit is dropped. The team's first instinct is a reminder to check the number. That is a request for more care, and it fails at the moment the person is tired or interrupted.

The team applies poka-yoke by finding the exact step where the digit is lost. It is the copy and paste. They add a check on the receiving system that compares the number against the account list and refuses a number that does not exist. The mistake now cannot enter the second system, and the person gets an immediate message that says which digit set did not match.

They then ask whether the check blocks any legitimate case, such as a new account that is not in the list yet. It does, so they add a clearly labelled override that needs a second person's approval. This keeps the control for the common case and gives a controlled way out for the rare one.

102 min

Poka-Yoke vs. nearby concepts

Four neighbours are often confused with poka-yoke. The deciding question is where each one acts.

ConceptWhat it acts onDeciding difference
Poka-yokeA human mistake at a process stepPrevents or flags the mistake as it happens
JidokaA machine or process abnormalityStops the line when a problem is detected
Fail-safe designA failure of the system itselfMakes the system fail into a safe state
Postel's LawIncoming data that varies from the specificationChooses to tolerate variation, the opposite stance

Toyota describes jidoka as "automation with a human touch," where a machine can detect an abnormality and stop automatically, or the operator can stop the line by pulling the stop cord. Poka-yoke is often the sensing part of that idea, because a device that detects a missing part is what triggers the stop. They differ in scope. Jidoka covers any abnormality, including a machine fault or a work delay, while poka-yoke covers the human mistake.

Postel's Law is a useful contrast for software engineers. Poka-yoke rejects bad input early and loudly. Postel's Law accepts input that varies when the meaning is still clear. Each is correct for different kinds of input: reject when a wrong value causes harm, tolerate when the sender's intent is clear and rejection only blocks work.

111 min

Where the evidence is limited

Poka-yoke has a strong practical record, but its sources are mostly teaching material, trade guides and the originator's own books. This article found no named study that measures how many defects poka-yoke devices prevent, and no named critic who argues against the method. A reader should treat the strongest claims with that in mind.

The claim with the most weight is Shingo's own: that combining source inspection with poka-yoke is the only way to reach zero defects. The publisher's description of his book repeats it. It is a statement by the method's author about a goal. It is not a measured result. A realistic reading is that poka-yoke removes one large and well-defined class of defects, those caused by human slips at known steps. Defects from bad design, bad materials or bad judgment need other controls.

The GPS lockout shows that the method can also fail by being applied without testing. The unresolved question for a practitioner is how much friction a device may add before people bypass it. No source here gives a number, so the only reliable method is to watch the device in use and see whether people work around it.

121 min

How Poka-Yoke changed since

The idea moved out of manufacturing. Wikipedia notes that the term can now refer to any behavior-shaping constraint designed into a process to prevent incorrect operation by the user. This is a wider meaning than Shingo's original one, which concerned operators on a production line.

One documented move is into health care. John Grout, a professor who runs a mistake-proofing research site, wrote a 2007 report for the US Agency for Healthcare Research and Quality, titled Mistake-Proofing the Design of Health Care Processes. The Patient Safety Network summary says the author draws from multidisciplinary sources to share examples of practical process and design changes that can mitigate human error in health care.

Two things changed from the original. First, the target moved from workers who assemble parts to anyone who follows a process, such as nurses, drivers and software users. Second, the wording moved from fool-proofing toward a design view, in which the process, and not the person, is what is corrected. Current practice does not always match Shingo's original method, because many modern devices block an action without the immediate, specific feedback that his source inspection required.

132 min

Frequently asked questions about Poka-Yoke

What is poka-yoke?

Poka-yoke is a Japanese term for mistake-proofing. It is any mechanism in a process that prevents a human error, corrects it, or draws attention to it as it happens. Shigeo Shingo applied the term to factory processes in the 1960s.

Who invented poka-yoke?

Shigeo Shingo, an industrial engineer on the Toyota Production System, applied the term in the 1960s and formalized the method. The name was first baka-yoke, which means fool-proofing, and was changed to the milder poka-yoke.

What are the two types of poka-yoke?

The two types are control and warning devices. A control device, also called a shutdown device, stops the process or makes the mistake impossible. A warning device alerts the person with a light, buzzer or message and leaves the decision to them.

What is a simple example of poka-yoke?

A car with a manual gearbox that will not start until the driver presses the clutch pedal is a simple example. A microwave oven that cannot start while its door is open is another. Both make the unsafe action impossible.

What is the difference between poka-yoke and jidoka?

Poka-yoke acts on a human mistake at a process step. Jidoka, one of the two pillars of the Toyota Production System, stops production when a machine or process abnormality is detected. Poka-yoke often supplies the detection that triggers the stop.

Can poka-yoke be used in software?

Yes. Software teams use it in checks that refuse an unsafe action, such as Git refusing a push that would overwrite shared commits. Typed confirmation for deletions and fixed lists for environment names follow the same idea.

When should you not use poka-yoke?

Do not use it for errors of judgment, where no single rule defines the right answer, or when a block would stop legitimate work. For those cases, use a checklist, an undo command, training or review instead.

Does poka-yoke guarantee zero defects?

No. Shingo argued that source inspection combined with poka-yoke is the way to reach zero defects, but that is the method author's claim, not a measured result. Poka-yoke addresses human slips at known steps, and other defects need other controls.

?8 questions

Questions people ask

What is poka-yoke?

Poka-yoke is a Japanese term for mistake-proofing. It is any mechanism in a process that prevents a human error, corrects it, or draws attention to it as it happens. Shigeo Shingo applied the term to factory processes in the 1960s.

Who invented poka-yoke?

Shigeo Shingo, an industrial engineer on the Toyota Production System, applied the term in the 1960s and formalized the method. The name was first baka-yoke, which means fool-proofing, and was changed to the milder poka-yoke.

What are the two types of poka-yoke?

The two types are control and warning devices. A control device, also called a shutdown device, stops the process or makes the mistake impossible. A warning device alerts the person with a light, buzzer or message and leaves the decision to them.

What is a simple example of poka-yoke?

A car with a manual gearbox that will not start until the driver presses the clutch pedal is a simple example. A microwave oven that cannot start while its door is open is another. Both make the unsafe action impossible.

What is the difference between poka-yoke and jidoka?

Poka-yoke acts on a human mistake at a process step. Jidoka, one of the two pillars of the Toyota Production System, stops production when a machine or process abnormality is detected. Poka-yoke often supplies the detection that triggers the stop.

Can poka-yoke be used in software?

Yes. Software teams use it in checks that refuse an unsafe action, such as Git refusing a push that would overwrite shared commits. Typed confirmation for deletions and fixed lists for environment names follow the same idea.

When should you not use poka-yoke?

Do not use it for errors of judgment, where no single rule defines the right answer, or when a block would stop legitimate work. For those cases, use a checklist, an undo command, training or review instead.

Does poka-yoke guarantee zero defects?

No. Shingo argued that source inspection combined with poka-yoke is the way to reach zero defects, but that is the method author's claim, not a measured result. Poka-yoke addresses human slips at known steps, and other defects need other controls.

§7 sources

Sources

Show all 7 sources
  1. Lean Enterprise Institute. Poka Yoke - A Resource Guide.

  2. Shingo, S. Zero Quality Control: Source Inspection and the Poka-Yoke System. Routledge, English edition 1986.

  3. Kumar, R. and Watt, B. Teaching Zero Quality Control Concepts in Mechanical Engineering Technology. University of North Texas, ASEE paper 7460.

  4. Toyota Motor Corporation. Toyota Production System: Jidoka.

  5. Git project. git-push documentation.

  6. Grout, J. R. Mistake-Proofing the Design of Health Care Processes. AHRQ Publication No. 07-0020, 2007.

Keep reading

More from Business

All of Business
All of Business

Missing a concept?

Tell us what to write next. We’ll email you when it’s live.

Several? Separate them with commas.

Only to tell you when it’s live.

How we use your email: privacy.