01 · Purpose and boundaries
Purpose and boundaries
Poka yoke means mistake proofing. It changes the process so a foreseeable error cannot occur, or so the error is detected immediately and contained before it produces an escaped defect. Prevention and detection are distinct. A keyed connector prevents the wrong orientation; a sensor that stops a process after an incorrect placement detects and contains it.
Begin with a specific error mechanism and its consequence. “People are careless” is not a design input. “Two similar cartons can receive the same carrier label when labels are printed in a batch” identifies a mechanism. Understand the sequence, normal variation, and exceptional work. Mistake proofing supports people and process reliability; it does not replace guarding, equipment safety systems, or necessary quality controls.
02 · How the method works
How the method works
Describe the error opportunity at the point of creation, not only the place it is discovered. Ask whether the step can be eliminated, whether physical or information constraints can prevent the wrong action, and whether an immediate check can detect the error. Prefer prevention when feasible without creating another hazard.
Choose an operating principle. A contact or identity check verifies an attribute; a count check confirms a required quantity; a sequence check ensures steps occur in order. Determine the response: warning, blocked release, or controlled stop. A warning that can be ignored under pressure provides weaker containment than an enforced release condition.
Test the device deliberately using representative wrong inputs, correct inputs, missing inputs, damaged labels, and loss of power or connection. Define false acceptance and false rejection separately. Establish a safe, authorized exception path with traceability; unrestricted bypass defeats the control. Assign responsibility for verification, maintenance, changes, and restoration following a fault.
03 · Worked logistics example
Worked logistics example
Fictional NorthQuay dispatches 800 parcels daily. Over ten days it records 24 wrong carrier labels among 8,000 parcels, a 0.3% escape rate. Investigation finds batch-printed labels are applied to visually similar cartons. The team changes to one parcel at a time and requires scanning both the order identifier and applied label before loading release.
The system compares order, parcel, and carrier service. A mismatch blocks release and gives a clear instruction to remove the incorrect label and reprint the approved one. It prevents downstream escape through detection at application; it does not make selecting the wrong loose label physically impossible.
Before launch, the team tests 40 mismatched combinations, 20 missing scans, and 100 valid combinations. All mismatches and missing scans are blocked; three valid combinations initially fail because damaged print quality prevents reading. Printer maintenance reduces these nuisance failures. During a five-day pilot, four attempted mismatches are contained and zero wrong labels are found among 4,000 dispatched parcels.
04 · Interpretation and decisions
Interpretation and decisions
Zero observed escapes in 4,000 parcels is encouraging, not proof of zero future risk. Monitor both contained attempts and escaped errors. Contained mismatches show the safeguard is being used and that the upstream error opportunity persists. They may justify eliminating batch printing entirely.
False rejections matter because repeated nuisance stops encourage workarounds. Improve print quality and scanner ergonomics while preserving the comparison rule. An emergency override should require authorization, a reason, and an independent check appropriate to the risk. Keep a record of overrides and verify that the control is restored. A scanner beep alone is not evidence that the identifiers were successfully compared.
05 · Common misapplications
Common misapplications
Adding another inspection far downstream is often called mistake proofing even when it only catches a sample. A sticker reminding people to be careful is an instruction, not an enforced constraint. Color can support recognition but is weak as the sole control where lighting, color vision, or similar packaging can interfere.
Do not bypass safety interlocks to make a quality interlock easier to install. Avoid controls that fail silently after a software update or sensor fault. Maintain safeguards with defined checks; a device installed once can drift, become damaged, or be defeated. Never count the device as effective merely because it has not alarmed: verify that a known wrong condition still produces the intended safe response.
06 · Advanced adaptation
Advanced adaptation
For information workflows, use controlled state transitions and unique identities. Idempotent transactions can prevent duplicate release when messages are retried. Design failure behavior deliberately: loss of connectivity may require a contained hold rather than assuming that an absent rejection means approval.
Layer prevention and detection where consequences justify it, but examine common-cause failures. Two checks reading the same incorrect master data do not provide independent protection. Include change control for item data, label formats, scanner firmware, and exception permissions. Periodically challenge the safeguard with approved test conditions and review whether the underlying error can now be removed through a simpler process design.
07 · Implementing and sustaining the change
Implementing and sustaining the change
Introduce poka yoke within a clearly named operating boundary. Identify the product family, shift, equipment, and handoffs affected; record what happens immediately before and after that boundary. A change that improves one task while exporting its delay to another department has not established an improvement. Agree who can stop the trial, who handles exceptions, and which customer commitment takes priority when the normal rule cannot be followed.
Establish a baseline from actual work rather than a single demonstration. Include normal variation in order mix, replenishment timing, staffing, and workload. Keep the denominator visible: minutes per order, defects per shipment, or completed lines per available hour answer different questions. Record the workload and conditions alongside each observation so that a quiet trial period cannot masquerade as better performance. Observe the process with the people who do it; their explanation of interruptions often changes the proposed design.
Start with a reversible pilot large enough to expose handoff problems. Explain the expected mechanism before launch: which action changes, which delay or failure it removes, and which result should respond. Train all affected shifts and support roles using the same operating definition. During the pilot, capture exceptions as information about the design. Do not conceal them through unofficial stock, unrecorded overtime, or a specialist who quietly repairs every failure.
Review customer service, safety, quality, work content, and inventory together. A faster average with more severe late orders may be unacceptable; a lower inventory level with repeated emergency deliveries may have displaced the cost. Investigate variation before declaring success. If the expected mechanism does not appear, revise the design or return to the baseline rather than defending the idea. A promising observation is a reason to test more conditions, not proof that every operating context will behave identically.
After a successful trial, make the new rule part of daily work. Give an accountable owner responsibility for the operating standard, change control, training, and periodic review. Specify the abnormal condition that requires escalation and the person who responds. Check whether the improvement remains effective when a trained colleague is absent or demand changes. Sustain the mechanism through routine management and learning; documentation is useful only when it describes the process people actually follow.
Connections
Related methods and phase use
Placed under Improve because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.