Skip to content
LeanSuite - Lean Manufacturing Software

Free training deck

Updated · About 35 minutes

Root cause analysis training presentation: 5 whys and fishbone

Root cause analysis (RCA) is the work of finding why a problem happened, so it can be fixed for good rather than patched. This free deck teaches a team the basics in about 35 minutes. Its 18 editable slides cover symptoms versus root causes, when to use RCA, describing and containing the problem, the 5 whys, the fishbone (6M) diagram, when to use each, verifying the cause, fixing and checking, an illustrative example, the common mistakes, a fishbone activity on a real problem 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 root cause analysis training presentation: the title Root cause analysis, fix the cause, not the symptom, on a navy background with the LeanSuite logo.
18 editable slidesSpeaker notesProblem statement and containment5 whysFishbone (6M) diagramVerify, fix and checkIllustrative exampleFishbone activity4 check questions with answersPDF handout

A look inside

What is in the 18 slides

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

  • Slide 9 of the root cause analysis training presentation: 5 whys and fishbone: The fishbone diagram: six M's.
    Slide 9: The fishbone diagram: six M's
  • Slide 8 of the root cause analysis training presentation: 5 whys and fishbone: Example: 5 whys on wrong labels.
    Slide 8: Example: 5 whys on wrong labels
  • Slide 15 of the root cause analysis training presentation: 5 whys and fishbone: Try it: a fishbone on a real problem.
    Slide 15: Try it: a fishbone on a real problem
  1. 1Root cause analysis: fix the cause, not the symptomCover
  2. 2AgendaSymptoms and root causes · Describe and contain the problem · The 5 whys · The fishbone diagram · Verify, fix and check, plus an activity
  3. 3Symptoms, causes and root causesA root cause is the cause that, once removed, stops the problem coming back.
  4. 4When to use root cause analysisProblems that keep coming back.
  5. 5Step 1: Describe the problemWhat, where, when and how much: facts, not guesses.
  6. 6Step 2: Contain it firstProtect the customer and the next process.
  7. 7The 5 whysAsk why the problem happened, then why that happened, until you reach a cause you can act on.
  8. 8Example: 5 whys on wrong labelsAn illustrative example of one 5 whys chain.
  9. 9The fishbone diagram: six M'sMan (people), Machine, Method, Material, Measurement, Mother Nature
  10. 10How to run a fishbone sessionWrite the problem statement at the head of the fish.
  11. 115 whys or fishbone?Many teams use both: the fishbone to list causes, the 5 whys to go deep on the likely ones.
  12. 12Step 3: Verify the root causeCheck it with data or a test before you act.
  13. 13Step 4: Fix it and checkChoose a countermeasure that removes or controls the root cause.
  14. 14Common mistakesJumping to a solution before defining the problem.
  15. 15Try it: a fishbone on a real problemA 15-minute team activity
  16. 16Check your understanding4 check questions
  17. 17AnswersThe answers, to discuss
  18. 18Key points and next stepsNext: check the two causes we picked, by the dates we set.

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 one problem that has come back recently. The activity slide takes the team through it step by step; allow 15 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 symptom and a root cause?
A symptom is what you see. The root cause is why the process allowed it; removing it stops it coming back.
2. What are the six M's?
Man, machine, method, material, measurement and mother nature.
3. Why contain before the root cause work?
To protect the customer and the next process while the cause is found.
4. Why is human error not a root cause?
It does not explain why the process allowed the error. Ask why again until you reach something you can change.

After the session

Put it on the wall

Free printable posters 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

Root cause analysis training presentation: common questions

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.

Schedule Demo