ForgeShiftCompass
QualityPractice B4

Poka-Yoke / Error Proofing

Poka-Yoke is an error-proofing discipline that designs the work so mistakes either can't happen, or get caught at the moment they happen — without relying on operator vigilance.

  • Assessment3 questions
  • Templates1
  • Root causeISHIKAWA-6M

What world-class looks like

Every process step's most likely defect has either a mistake-prevention or mistake-detection device that requires no operator attention.

How mature is your operation?

These are the questions Compass asks for this practice, and the levels it scores you against.

Error source identification

Systematically cataloguing which process steps produce errors and what type of mistake drives each one.

How do you identify where errors enter the process?

Level 1 → 5World class at level 4

  1. We find errors at final inspection or from customer complaints only
  2. We know rough areas from experience but have no structured list
  3. We use defect data and walk the process to identify error-prone steps
  4. We map every process step against its most likely mistake type and causeWorld class
  5. Structured error source analysis is embedded in every new process launch and change review

Error-proofing device design

Selecting and implementing physical or digital mechanisms that prevent or detect specific errors.

How do you respond when an error source is identified?

Level 1 → 5World class at level 4

  1. We retrain the operator or add an inspection step
  2. We sometimes add a jig or fixture but it depends on the engineer's initiative
  3. We apply error-proofing devices to our highest-impact defect sources
  4. For every identified error source we specify a prevention or detection device before closing the actionWorld class
  5. Formal error-proofing reviews are part of our process design gate; devices are validated before production release

Effectiveness verification

Confirming that installed error-proofing devices actually prevent or detect the target mistake.

How do you confirm that an error-proofing device is working?

Level 1 → 5World class at level 4

  1. We assume it works if defects drop — no formal check
  2. We monitor defect rates after installation for a few weeks
  3. We run a deliberate failure test — intentionally introduce the error to verify the device catches it
  4. Each device has a documented validation test and a pass/fail criterion; we re-test periodicallyWorld class
  5. Device effectiveness is tracked by actual defect-escape rate; devices with escapes are redesigned, not just re-trained around

Where to start

  • Error-proofing device workshop

    Quality · L1→L2 · Low complexityCloses · Error-proofing device design
  • Deliberate-failure validation protocol

    Quality · L2→L3 · Low complexityCloses · Effectiveness verification
Root-cause methodISHIKAWA-6M

Next steps

Scoring your operation against Poka-Yoke / Error Proofing takes a few minutes and needs no account.