Reading time: ~6 min
If the customer just sent a non-conformance report, this is the article. 8D problem solving training is the structured response we owe a customer when something we shipped didn’t perform — the eight disciplines, in order, signed off by us, audited by them. It’s the version of problem-solving an OEM expects from its supply base, and it’s also the version most teams run badly the first three times they’re asked to.
This article is the working version of 8D as we run it: the eight disciplines, where they map onto Kobetsu Kaizen, and the moves that decide whether the customer signs off on D8 the first time or sends the report back twice. For the underlying 3-step methodology that powers each discipline, see our pillar guide on problem solving methodology.
What 8D problem solving training actually teaches
8D — the Eight Disciplines of problem solving — was formalised at Ford in the late 1980s as the corrective-action protocol asked of its supply base when a defect reached the customer. It’s now standard across automotive, aerospace, and any industry where a non-conformance triggers a structured customer-response.
The eight disciplines:
| # | Discipline | What it does |
|---|---|---|
| D0 | Emergency response | Contain immediate risk before anything else. “Is the customer’s line still running?” |
| D1 | Team | Name the cross-functional team. Quality, manufacturing, engineering, supply chain. |
| D2 | Problem description | What, where, when, who, how, how much. (This is 5W2H by another name.) |
| D3 | Containment | Stop bad parts from reaching the customer while we work the cause. |
| D4 | Root cause | The technical and systemic cause. 5 Whys, Fishbone, Pareto. |
| D5 | Corrective action | The chosen permanent fix. |
| D6 | Implement & verify | Roll out the fix, measure that it worked. |
| D7 | Prevention | Update controls (FMEA, control plan, standard work) so it can’t happen again. |
| D8 | Closure & recognition | Customer sign-off. Team thank-you. Lessons logged. |
That’s the format. The format is the easy part. The hard part is doing each step honestly under the time pressure a real complaint creates.
Why 8D is Kobetsu Kaizen wrapped in a customer protocol
The 8D format and Kobetsu Kaizen share the same DNA: observe before you interpret, align meaning before you analyse, define the real problem before you act. The difference is who’s watching.
In an internal Kobetsu Kaizen cycle, we run the 3G observation, the 5W2H Meta Probe, and the real-problem definition at our own pace, with our own team. In 8D problem solving training, the same disciplines run with a customer waiting on the other end of an email — and a clock that’s already counting down. The customer often dictates the response window: 24 hours for D0/D1/D2, 7 days for D3, 30 days for D4/D5/D6, 60 days for D7/D8. Sometimes faster.
Skip 3G in an internal Kobetsu Kaizen cycle and we waste a week. Skip 3G in 8D and the customer rejects D3 — and the relationship takes the hit.
A useful mental model: 8D is the customer-facing wrapper around the same Lean DNA. 3G lives inside D2/D3, 5W2H inside D2, Why-Why inside D4, PDCA inside D5/D6, FMEA inside D7. None of this is new for a team with solid Kobetsu Kaizen reps — 8D is the cover sheet.
This is why 8d problem solving training material that teaches the eight steps without the underlying methodology produces teams who fill the form correctly and still ship defective parts. The form is the deliverable; the method makes the form true.
The five mistakes we see most often in 8D
After fifteen years watching automotive and aerospace teams run 8D, five patterns separate the reports the customer accepts the first time from the ones that bounce:
- D3 containment that isn’t actually containing. The team writes “100% inspection added” but doesn’t define how, by whom, with what gauge, against what acceptance criteria. The customer asks. The 8D bounces.
- D4 root cause that’s a single sentence (“operator error”). Operator error is never the root cause; it’s the place causal analysis gives up. A real D4 has at least two layers — technical cause and systemic cause.
- D5 corrective action that’s the same as D3 containment. If 100% inspection is the permanent fix, the team didn’t analyse causes. The customer reads this as: “You haven’t actually fixed it — you’re inspecting the symptom.”
- D7 prevention that doesn’t update FMEA or the control plan. Without that, the same cause re-emerges on the next variant or the next program.
- D8 closure with no recognition or lessons-logged step. Skipping it teaches the team that 8D is a chore. Recognition is what turns the protocol into a habit.
Each of these failures comes from running the form without the methodology. Which is why the teams we coach run their first 8Ds inside the Kobetsu Kaizen reps from our Ninja Problem Solving course before the customer’s clock starts.
When to use 8D vs other problem-solving methodologies
A short map of when 8D is the right tool versus the alternatives:
- Use 8D when the trigger is external — a customer complaint, a regulatory finding, a non-conformance report. The customer expects the eight-discipline format. Don’t argue.
- Use Kobetsu Kaizen (3G + 5W2H + define) when the trigger is internal — a metric drop, an audit finding, a recurring issue. No customer to satisfy on format; pure problem-solving.
- Use A3 when we want a one-page reporting format on top of either methodology. A3 is a format, not a methodology.
- Use Six Sigma DMAIC when the problem requires statistical analysis at scale — process capability, variation reduction, projects spanning months. Six Sigma is heavier and more statistical than 8D.
- Pair 8D with FMEA in D7 — FMEA is preventive (anticipate before it happens), 8D is reactive (respond after it has). They share the control plan.
Most operations teams don’t need to pick one — they need fluency in 3G + 5W2H underneath all of them. The format changes; the discipline doesn’t.
In short
- 8D problem solving training is the structured response a customer expects when we shipped something defective. Eight disciplines, D0 through D8.
- 8D is Kobetsu Kaizen wrapped in a customer-complaint protocol. The Lean DNA underneath is identical; the wrapper changes who’s watching.
- Five common failures: weak D3 containment, “operator error” root causes, D5 = D3, D7 that doesn’t update FMEA, D8 with no recognition.
- 8D is reactive (customer-triggered). Kobetsu Kaizen is internal. A3 is a format. DMAIC is statistical-heavy. FMEA is preventive.
- Most teams don’t need to pick a methodology — they need fluency in 3G + 5W2H beneath all of them.
FAQ
Q1: What training is needed for 8D problem solving? A1: Effective 8D problem solving training has two layers. The surface layer — the eight disciplines and the report format — is what most paid courses cover. The deeper layer is the Lean methodology (3G, 5W2H, real-problem definition) that decides whether each D is filled in honestly. Train the methodology first; the format becomes paperwork.
Q2: What are the 8D problem-solving techniques? A2: Each discipline uses a specific Lean tool: D2 uses 5W2H to describe the problem; D3 uses containment-and-verification logic; D4 uses 5 Whys and Fishbone for root cause; D5/D6 use PDCA for corrective action and verification; D7 uses FMEA and the control plan for prevention. The disciplines are the order; the techniques are what each step uses.
Q3: Is 8D part of Six Sigma? A3: No. 8D came from Ford in the late 1980s as a customer-complaint protocol; Six Sigma came from Motorola as a statistical quality methodology. They share some tools (5 Whys, Fishbone, control plans) but they’re separate frameworks. 8D is reactive and customer-facing; DMAIC (the Six Sigma core) is statistical and project-driven.
Q4: What is 8D and FMEA, and how do they fit together? A4: FMEA (Failure Mode and Effects Analysis) is preventive — anticipate failure modes before they happen. 8D is reactive — respond when a failure has already reached the customer. They meet in D7 (Prevention): a closed 8D should update the FMEA and the control plan so the cause can’t re-emerge. Running 8D without updating FMEA is the most common reason the same defect appears in the next variant.
Q5: Can I get 8D problem solving training online for free? A5: The free Ronin Problem Solving course on Lean Trainings teaches the underlying Kobetsu Kaizen methodology that powers each 8D discipline. The Ninja-level course adds applied 8D reps with mentor feedback. The eight-discipline format itself is public domain; what makes the training valuable is the methodology underneath.
The next time a customer NCR lands in the inbox, we either fill the eight boxes and hope the report stays accepted — or we run real Kobetsu Kaizen reps inside each discipline. The Ninja Problem Solving course on Lean Trainings is the structured version of that path, with applied 8D coaching on real complaints. The Ninja-level certification is the verifiable credential. Enroll in the Ninja Problem Solving course →
