Poka-Yoke: A Practical How-To Guide to Mistake-Proofing Your Process
Poka-yoke is a Japanese term meaning 'mistake-proofing.' It refers to any mechanism in a process or product that prevents an error from being made, or that makes an error immediately obvious so it can be corrected before it becomes a defect. Poka-yoke was developed and popularised by Shigeo Shingo as part of the Toyota Production System, and it is now applied in manufacturing, service delivery, healthcare, software development, and public administration.
The key insight of poka-yoke is that humans make errors predictably -- not because they are careless or incompetent, but because human attention is limited and errors occur when processes rely on human attention to prevent them. Poka-yoke designs the process so that attention is not required to prevent the error -- the error is simply not possible, or is immediately flagged if it is made.
The Three Types of Poka-Yoke
Prevention poka-yoke. Prevents the error from occurring at all. A SIM card that can only be inserted in one orientation is a prevention poka-yoke -- incorrect insertion is physically impossible. A web form field that only accepts numeric input for a phone number field is a software prevention poka-yoke.
Detection poka-yoke. Detects the error at the point where it occurs and alerts the operator before the work moves on. A machine that stops automatically when a part is incorrectly positioned is a detection poka-yoke. An email system that asks 'Are you sure you want to send this email with no recipients?' is a detection poka-yoke.
Correction poka-yoke. Automatically corrects the error when it occurs. Spellcheck that automatically corrects common typos is a correction poka-yoke. A system that automatically formats a phone number into a standard format when a user enters it in any format is a correction poka-yoke.
How to Apply Poka-Yoke: A Practical Process
Identify the error. Start with a specific, recurring error -- not a category of errors. 'Processing fee payments to the wrong vendor account' is specific. 'Payment errors' is not. The more specific the error definition, the more targeted and effective the poka-yoke can be.
Identify when and why the error occurs. Map the process step where the error occurs. What is happening at that step? What information or action is required? Where does the human attention failure occur? The most common causes of errors are: incorrect information (doing the wrong thing because of bad data), correct information not accessed (the right information existed but was not checked), and process skipped (a required step was missed).
Design the mechanism. Design a mechanism that prevents, detects, or corrects the error. Preference order: prevention first, then detection, then correction. A mechanism that prevents the error entirely is more valuable than one that catches it after the fact.
Test the mechanism. Before implementing, test the poka-yoke with the people who will use it. Does it prevent the error without creating new errors or unacceptable process friction? A poka-yoke that slows the process to the point where operators work around it has not improved the process.
XNM applies Lean tools including poka-yoke to process improvement in public-sector and capital-project environments. Reach out to XNM's strategic advisory team to discuss error prevention and process quality for your organisation.