Skip to content

Free training deck

Updated · About 40 minutes

Poka-yoke (mistake-proofing) training presentation

Poka-yoke is the Japanese lean term for mistake-proofing. It means designing a step so a mistake cannot be made, or is caught at once, instead of asking people to be more careful. This free deck teaches it to a team in about 40 minutes. Its 18 editable slides cover the difference between a mistake and a defect, why people make mistakes, control and warning devices, Shingo's three methods (contact, fixed-value and motion-step), the three kinds of inspection, a ranking of fixes from strongest to weakest, a six-step way to design one, how to keep it working, an illustrative worked example, the common mistakes, a 20-minute floor activity and four check questions with answers. Every slide has speaker notes.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

The cover slide of the poka-yoke training presentationThe title Poka-yoke, mistake-proofing the work, on a navy background with the LeanSuite logo.
18 editable slidesSpeaker notesMistake versus defectControl and warning devicesContact, fixed-value and motion-stepRanking the fixSix-step design methodIllustrative exampleFloor activity4 check questions with answersPDF handout

A look inside

What is in the 18 slides

For operators, team leaders, supervisors, quality, process and maintenance engineers. Widescreen, in plain language, with speaker notes on every slide.

  • Slide 5 of the poka-yoke (mistake-proofing) training presentation: Why people make mistakes.
    Slide 5: Why people make mistakes
  • Slide 13 of the poka-yoke (mistake-proofing) training presentation: Example: a missing O-ring.
    Slide 13: Example: a missing O-ring
  • Slide 15 of the poka-yoke (mistake-proofing) training presentation: Try it: find a mistake to proof.
    Slide 15: Try it: find a mistake to proof
  1. 1Poka-yoke: mistake-proofing the workCover
  2. 2AgendaMistakes, defects and why mistakes happen · Control and warning devices, and the three methods · Ranking fixes and designing a poka-yoke · Keeping it working, example and common mistakes · Floor activity and check questions
  3. 3What poka-yoke isPoka-yoke means error-proofing: a simple device or design that stops a mistake or catches it at once.
  4. 4A mistake is not a defectShingo separated the cause from the result. Stop the mistake becoming a defect and the customer never sees it.
  5. 5Why people make mistakesForgetting, Wrong item, New to the job, Distraction, Unclear standard, Rushing
  6. 6Control devices and warning devicesA poka-yoke either stops the process or tells someone. Stopping is stronger.
  7. 7The three methodsShingo grouped poka-yoke by what it checks.
  8. 8Where you catch the errorShingo described three kinds of inspection. The earlier you catch the problem, the better.
  9. 9Examples you can point atTypical examples. Yours will be different, but the idea is the same.
  10. 10Ranking the fix, strongest firstRemove the step, Make it impossible, Stop the process, Warn the person, Inspect afterwards, Remind or retrain
  11. 11How to design one in six stepsStart from a real mistake: scrap, a customer complaint, a near miss or a high-risk failure mode in the process FMEA.
  12. 12Keeping it workingA poka-yoke that fails without anyone knowing is worse than none, because people stop checking.
  13. 13Example: a missing O-ringAn illustrative example of the six steps. Your own process will differ.
  14. 14Common mistakesUsing a sign or a retraining session when a physical fix is possible.
  15. 15Try it: find a mistake to proofA 20-minute team activity
  16. 16Check your understanding4 check questions
  17. 17AnswersThe answers, to discuss
  18. 18Key points and next stepsNext: take one mistake from your area and run the six steps.

The 40-minute session, slide by slide

  • Slides, about: 20 minutes
  • Activity (slide 15): 20 minutes
  1. Present · 14 slides

    1. 1Poka-yoke: mistake-proofing the work
    2. 2Agenda
    3. 3What poka-yoke is
    4. 4A mistake is not a defect
    5. 5Why people make mistakes
    6. 6Control devices and warning devices
    7. 7The three methods
    8. 8Where you catch the error
    9. 9Examples you can point at
    10. 10Ranking the fix, strongest first
    11. 11How to design one in six steps
    12. 12Keeping it working
    13. 13Example: a missing O-ring
    14. 14Common mistakes
  2. Do the activity · 1 slide

    1. 15Try it: find a mistake to proof
  3. Check and follow up · 3 slides

    1. 16Check your understanding
    2. 17Answers
    3. 18Key points and next steps

About 20 minutes of slides and 20 minutes of activity. Present: slides 1 to 14 (Poka-yoke: mistake-proofing the work; Agenda; What poka-yoke is; A mistake is not a defect; Why people make mistakes; Control devices and warning devices; The three methods; Where you catch the error; Examples you can point at; Ranking the fix, strongest first; How to design one in six steps; Keeping it working; Example: a missing O-ring; Common mistakes). Do the activity: slide 15 (Try it: find a mistake to proof). Check and follow up: slides 16 to 18 (Check your understanding; Answers; Key points and next steps).

Prepare happens before slide 1: read the notes and swap in your own example. Then the deck runs in order: present is slides 1 to 14, do the activity is slide 15 and check and follow up is slides 16 to 18. The check questions come before their answers, so ask first.

How to run it

Running the session

  1. 1

    Prepare

    Read the speaker notes once and swap the illustrative example for one from your own area if you have it. Print the PDF if people like a handout.

  2. 2

    Present

    The slides take about 20 minutes. Every slide has notes, so you can talk from them rather than read the slide.

  3. 3

    Do the activity

    Pick a mistake from the past month: a scrap reason, a customer complaint or a near miss. The activity slide takes the team through it step by step; allow 20 minutes.

  4. 4

    Check and follow up

    Ask the check questions before showing the answers, then agree one next step with an owner and a date before people leave.

The check questions

1. What is the difference between a mistake and a defect?
A mistake is an error made at the step. A defect is the result when it reaches the product. Poka-yoke stops the mistake becoming a defect.
2. What are the three poka-yoke methods?
Contact (shape, size or colour), fixed-value (a set count) and motion-step (a set sequence).
3. Why is a control device stronger than a warning device?
A control device stops the process, so it does not depend on anyone noticing. A warning works only if someone reacts.
4. Why test a poka-yoke regularly?
A device that fails silently is worse than none. A known bad part shows it still works.

After the session

Put it on the wall

Free printable poster on the same subject, so the team sees it every day: a PNG to download now, and print-ready PDFs from Letter to 24 x 36 in.

FAQ

Poka-yoke (mistake-proofing) training presentation: common questions

  1. Poka-yoke is Japanese for mistake-proofing. Poka means an inadvertent error and yoke means prevention. It is a design or device that stops a mistake or catches it at once.

  2. About 40 minutes: roughly 15 minutes of slides, a 20-minute floor activity and the check questions.

  3. Shingo's three methods are contact (shape, size or colour), fixed-value (a set count) and motion-step (a set sequence). The deck also covers the two functions, control devices that stop the process and warning devices that alert someone.

  4. No. The method applies to any process where a mistake can reach the product, from assembly to packing and food handling. The deck mentions IATF 16949 clause 10.2.4 for automotive suppliers, and you can drop that line if it does not apply.

  5. Yes. The PowerPoint file is fully editable, including the speaker notes. Many teams replace the illustrative O-ring example with a mistake from their own plant.

More free training decks

Training is the start. Keeping it going is the hard part.

See how plants run their audits, improvements and follow-ups in LeanSuite, on a call built around your own problem.

Book a 45-minute demo