What Is Poka-Yoke?
Poka-yoke is a Japanese error-proofing method that designs processes so mistakes are prevented or caught immediately, before they become defects. The term means “mistake-proofing,” and it is a core technique in Lean manufacturing and Six Sigma.
Instead of relying on inspection or memory, poka-yoke builds constraints, guides, sensors, and checks into the work itself. The correct action becomes the easiest action, and the incorrect action becomes difficult or impossible.
Why Poka-Yoke Matters in Six Sigma
Six Sigma focuses on reducing variation and eliminating defects. Poka-yoke complements that work by removing the possibility of common human errors at the point where they occur. It is prevention rather than detection.
- Prevents defects at the source: Errors are stopped before they can create scrap, rework, or a customer complaint.
- Reduces dependence on inspection: Quality is built into the process instead of being checked in after the fact.
- Makes processes safer: Guards, interlocks, and forced sequences prevent dangerous actions as well as quality errors.
- Supports standard work: Clear constraints and visual cues make the correct method the default method.
- Protects customers: A defect that cannot be made cannot reach a customer.
Build Error-Proof Processes
Eastman Business Institute's Lean Six Sigma training covers poka-yoke, DMAIC, and practical error prevention for real improvement projects.
Explore Training ProgramsTypes of Poka-Yoke
Prevention vs. Detection
Prevention devices make an error impossible or extremely difficult. A fixture that only accepts the correct part is a prevention device. Detection devices allow the action but catch the error immediately, such as a sensor that stops a machine when a part is missing.
Prevention is generally stronger, but detection is useful when physical prevention is impractical. The best choice depends on the failure mode, risk, and cost.
Common Mechanisms
Poka-Yoke Mechanisms and Examples
| Mechanism | How It Works | Example |
|---|---|---|
| Guide pins and fixtures | Only the correct part or orientation fits | A connector that plugs in only one way |
| Limit switches and interlocks | Stops the process when a condition is wrong | A machine that will not start with a guard open |
| Counters | Confirms the required number of steps or parts | An assembly station that verifies all screws are installed |
| Forced sequence | Requires the correct order of operations | Software that will not submit until required fields are complete |
| Visual indicators | Makes abnormal conditions immediately obvious | Color-coded bins, status lights, or shadow boards |
Practical Poka-Yoke Examples
- Manufacturing: Fixtures with guide pins prevent parts from being loaded backward; sensors detect a missing component before the cycle starts.
- Healthcare: Color-coded medication labels, barcode scanning, and connectors that fit only the correct line reduce medication and tubing errors.
- Office and software: Required fields, input masks, confirmation dialogs, and restricted dropdown values prevent incomplete or invalid data entry.
- Everyday products: A car that will not shift out of park without the brake pressed, or a USB-C plug that works in either orientation, are familiar error-proofing designs.
Good poka-yoke is usually simple. If a device requires extra training, constant attention, or workarounds, it is probably not error-proofing yet.
How to Implement Poka-Yoke
- Map the process: Walk through the actual work, not the documented ideal, and identify where errors occur.
- Describe the failure modes: Use tools such as FMEA, 5 Whys, or a fishbone diagram to define what can go wrong and why.
- Prioritize by risk: Focus first on errors with the highest safety, quality, or cost impact.
- Design the simplest device: Prefer passive prevention over alerts, and test the design with the people who do the work.
- Pilot and measure: Run the change in a controlled area and compare defect, rework, and cycle-time data.
- Standardize and train: Update standard work, train the team, and audit the device so it does not get bypassed.
Poka-Yoke and DMAIC
Poka-yoke fits naturally into the DMAIC cycle:
- Define: Identify the defect, customer impact, and project goal.
- Measure: Quantify the current error rate and the conditions that produce it.
- Analyze: Find the root causes and the steps where errors are most likely.
- Improve: Design and pilot the poka-yoke device or process change.
- Control: Standardize the device, monitor its use, and verify that the defect does not return.
Because poka-yoke changes the process rather than asking people to try harder, it is often a strong control in the Improve and Control phases.
Frequently Asked Questions
Poka-yoke is Japanese for “mistake-proofing.” It is a Lean technique that designs a process so common errors are prevented or detected immediately, before they become defects.
They mean the same thing. Poka-yoke is the Japanese term; mistake-proofing and error-proofing are the English translations used in Lean and Six Sigma.
Examples include fixtures that only accept the correct part, sensors that detect a missing component, counters that verify all fasteners are installed, and machine guards that prevent operation when open.
Yes. Required fields, input validation, restricted dropdown values, confirmation dialogs, and automated checks are common poka-yoke devices in software and administrative work.
Poka-yoke is usually designed during the Improve phase and standardized during Control. It addresses root causes found in Analyze and helps prevent the defect from returning after the project ends.
Make Errors Impossible, Not Just Unlikely
Learn how to apply poka-yoke and Lean Six Sigma in your own processes with practical training from Eastman Business Institute.
- Error-proofing and mistake-proofing techniques
- DMAIC project application
- Root cause analysis and prevention
- Practical implementation templates