Poka-Yoke (Mistake-Proofing) Analysis

Description

Systematically classifies and applies control and warning devices that prevent errors or make them immediately evident at the point of occurrence.

Shingo distinguished between errors (human slips) and defects (their consequences) and argued defects can be eliminated by catching errors at source. Poka-yoke devices use contact, fixed-value or motion-step methods and act either as controls (stopping the process) or warnings (signalling). John Grout's work systematised the approach for services and design. In UX the idea survives as 'forcing functions' or 'constraints' from Norman, but the systematic process of analysing each error-prone step, choosing a detection method and preferring controls over warnings is rarely followed. Done properly, it pairs with an error analysis such as SHERPA and yields measurable defect reductions.

Attributes

Loss type
Renamed
Effort
Days

Steps

  1. List error-prone steps from error analyses, logs or tests, with their resulting defects.
  2. For each, decide whether the error can be prevented (control) or only detected (warning), preferring prevention.
  3. Choose a detection method: contact (checking a property), fixed-value (counting required items) or motion-step (checking sequence).
  4. Design the device: input constraints, interlocks, checklists that block progress, validation at entry.
  5. Estimate the cost of false blocking and design a safe override path for legitimate exceptions.
  6. Measure defect rates before and after and monitor overrides for misuse.

Sources

  • Shingo, Zero Quality Control: Source Inspection and the Poka-Yoke System (1986)
  • Grout, Mistake-Proofing the Design of Health Care Processes (AHRQ, 2007)

Also known as

  • Poka-yoke
  • Mistake-proofing
  • Error-proofing
  • Forcing functions

Categories

  • Accessibility
  • Human Factors & Error