The archive · Work & Ways of Doing · Operational decision · 1961–1963
Toyota's poka-yoke makes errors impossible instead of catching them later
In 1961 Toyota engineer Shigeo Shingo began designing errors out of work itself — 'poka-yoke' became lean's mistake-proofing standard.
Toyota Motor Corporation
What it had to solve
In 1961 Shigeo Shingo, an industrial engineer working with Toyota, saw that errors were treated as the worker's fault and defects were only found later by inspection and rework. His alternative was to make the mistake physically difficult or impossible to commit in the first place.
How it works
In 1961 Shigeo Shingo, an industrial engineer working with Toyota Motor Corporation, introduced poka-yoke, a system for preventing specific defects, faulty products and machine damage by making errors hard or impossible to commit. His starting point was that a defect caught by inspection has already cost the company; the cheaper question is how to stop it forming at all.
Shingo's mechanisms could be electrical, mechanical, procedural or visual — guide pins that only fit one way, sensors that stop a machine when a part is missing, switches that check a component is seated, or checklists that block the next step until the current one is done. He first called the approach 'baka-yoke,' meaning foolproofing, until a worker at Arakawa Body Company refused to use devices carrying such an insulting name; in 1963 the term was changed to 'poka-yoke,' or mistakeproofing.
Poka-yoke applied the zero-defects idea as a team-based floor improvement strategy: errorproofing either prevents an error from becoming a defect or detects it immediately so one mistake cannot multiply. The Fabricator described its reach as extending beyond the shop floor to sales, order entry, purchasing and product development, where the cost of a mistake is often higher.
Why it lands
- Prevention beats inspection: stopping an error at its source avoids the rework, scrap and repair that catching it later guarantees.
- Physical and procedural design removes dependence on attention, so quality does not rely on workers never slipping.
- Detecting an error the moment it happens stops it from propagating into many defective parts.
- Renaming the tool from 'foolproofing' to 'mistakeproofing' treated workers as allies rather than suspects — a condition for the method being adopted at all.
What it did
Poka-yoke moved quality control from inspection to prevention, so parts could be produced correctly from the first piece. The method spread from Toyota's factories into sales, order entry, purchasing and product development, and later into service industries such as restaurants and healthcare.
What you can take
Assume the error will happen and design it out: prevention costs less than inspection, errors are process problems rather than personal failings, and the tool's name must respect the people using it.
Since then
Poka-yoke became a standard element of the Toyota Production System and, through Shingo's writing on zero quality control, part of the global lean-manufacturing toolkit. Businesses far beyond carmaking now use the same logic: color-coded fuel cans, assembly fixtures that only fit one way, restaurant checklists and surgical checklists all borrow the principle that the best inspection is the one that never lets the error happen.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe the brief you are staring at, and see who has been given the same problem.
Free account · 3 free questions · no card