Poka-Yoke
A mistake-proofing mechanism built into a process or design that prevents errors from occurring or makes them immediately obvious.
Also known as: Mistake-Proofing, Error-Proofing, Fool-Proofing, Baka-Yoke
Category: Techniques
Tags: qualities, processes, manufacturing, error-prevention, design
Explanation
Poka-Yoke (Japanese for 'mistake-proofing') is a concept developed by Shigeo Shingo as part of the Toyota Production System. It refers to any mechanism in a process that helps prevent human errors or makes errors immediately detectable before they cause defects.
**Core Principle**:
Humans inevitably make mistakes. Rather than relying on training, attention, or willpower to prevent errors, poka-yoke designs the process or environment so that errors either cannot occur or are caught instantly.
**Types of Poka-Yoke**:
1. **Prevention (Control)**: Makes it physically impossible to make the error
- USB plugs that only fit one way
- Car ignition that won't start unless in Park/Neutral
- Software form validation that prevents invalid input
2. **Detection (Warning)**: Alerts the operator immediately when an error is made
- Car door chime when keys are left in ignition
- Spell-check underlining misspelled words
- Alarms for out-of-range values in monitoring systems
3. **Facilitation**: Makes the correct action easier than the incorrect one
- Color-coded connectors
- Checklists with forced completion
- Default settings configured for the common case
**Poka-Yoke Design Principles**:
- Design for the error, not the person
- Make errors impossible, or make them obvious
- Stop the process at the source of the error
- Use simple, low-cost solutions
- Implement as close to the error source as possible
**Everyday Examples**:
- Microwaves that stop when the door opens
- Elevator doors with sensors preventing closing on people
- Software 'undo' functionality
- Confirmation dialogs before irreversible actions
- Auto-save in document editors
**In Knowledge Work and Software**:
- Linters and type systems that catch errors before runtime
- Database constraints that prevent invalid data
- CI/CD pipelines that block deployments with failing tests
- Templates that ensure required fields are filled
- Git hooks that enforce commit message formats
Poka-yoke reflects a systems-thinking approach: instead of blaming people for mistakes, design the system so mistakes cannot propagate into defects.
Related Concepts
← Back to all concepts