ACADEMY · FREE MODULE 5 OF 11

M5 · Root Cause Analysis

8 min video with captions · one-page job aid · short quiz

Job aid

From a problem to a cause you can prove

Root cause analysis finds the process that makes a problem happen, and checks it with data before anyone fixes anything. Fixing the symptom only buys time.

Step Ask Tool
1 State it What is wrong, where, since when, and how much against normal? Problem statement: no cause, no blame, no fix in it
2 Widen What could cause it? Fishbone: 4+ categories, 12+ causes, then choose a bone
3 Deepen Why? And why again? 5 Whys down one branch; each answer a fact you can check; stop at a process you can change
4 Sort What do we see, what makes it worse, what makes it happen? Symptom · contributing cause · root cause
5 Verify Does removing it switch the problem off? Check the data, compare before/after rates, or run a small trial

Fishbone categories: physical work: people, methods, machines, materials, measurement, environment. Services: people, methods, systems, data, policies, environment.

5 Whys rules: one branch at a time. If an answer names a person ("someone made an error"), ask why the system let it happen, and keep going.

Watch out for: a cause hidden in the problem statement · stopping at "human error" · a fishbone with one busy bone · fixing before verifying.

Examples

Industry Problem Root cause Verified
✈ Airline MRO Outflow valve on ZZ-RMB replaced 3 times in 2 months (norm < 1 a year) Task card had no torque value; not updated after a service bulletin No fault in 2 of 3 removed valves; 90 days on the revised card: 0 removals
⚙ Manufacturing 4.2% oversize bores on CNC lathe 3 (baseline 0.8%) No tool-life review when the bar-stock material changes 200-part trial, inserts changed at 300: 0.5%
🏦 Banking/Services Outbound payment failures 0.6% → 1.4% of daily volume No step to review partner change notices against our interfaces 9 in 10 rejections carry "field too long"; one-week test back to 0.6%
✚ Healthcare 12 late 08:00 doses in 2 weeks (2 before) Delivery route changed without checking ward schedules: a support process, not nursing n/a (supplemental example)
📦 Logistics Mis-ships 0.3% → 0.9%, mostly two look-alike items Slotting rules don't check for look-alike items n/a (supplemental example)

All examples are fictional.

Quiz

Answer each question first; the answer and why open after you choose or press “Show the answer”. Nothing is saved or sent.

Pass mark: 4 of 5 questions. Q5 counts as correct at 4 of 5 rubric points.

Q1 · Airline MRO · Symptom, contributing, root

Scenario: On fictional aircraft ZZ-RMB, the cabin pressure outflow valve was replaced three times in two months for the same fault message. The team found that the connector had backed out because it was never torqued to a value. The task card says only "secure connector": it was written before a service bulletin added a torque value. The repeat-defect history is not shown to the next shift.

Question: Which item is the root cause?

Q2 · Manufacturing · Verify the cause

Scenario: Since week 10, 4.2% of shafts from fictional CNC lathe 3 have an oversize bore, against a 0.8% baseline. A harder bar stock arrived in week 10. Inserts (the cutting tips) are still changed at a fixed count of 500, a count set for the old material. The team thinks the root cause is that tool life isn't reviewed when the material changes.

Question: Which check would best verify that root cause?

Q3 · Banking/Services · Problem statement

Scenario: A fictional bank's payments team is writing up a rise in failed outbound payments.

Question: Which problem statement is complete and measurable?

Q4 · Logistics · Transfer question

Scenario: At a fictional warehouse, wrong items sent to customers ("mis-ships") rose from 0.3% to 0.9% of orders in October, mostly for two products that look almost the same. Pickers took the neighboring product because the two were stored side by side. That happened because the storage plan ("slotting": deciding where each product goes) was redone by product size, and the slotting rules don't check for look-alike items. October was also the busiest month of the year.

Question: Which is the root cause?

Q5 · Build exercise (learner's choice)

Task: Pick a problem that keeps coming back in your own work (or use this case: a team's weekly report goes out late 3 weeks in 5 since a new data system went live in May; before that it was late about once a quarter). Write:

  1. A problem statement in four parts.
  2. A fishbone with at least 4 categories and at least 12 possible causes.
  3. One 5 Whys ladder down one bone.
  4. How you would verify the root cause with data before fixing it.

All examples are fictional.