What is 8D problem solving?
8D (short for Eight Disciplines) is a team method for solving a problem that has already happened, usually a defect a customer found. It walks you from "we have a problem" to "it's fixed, and it can't come back" in eight steps, D1 through D8, plus a preparation step called D0.
Ford Motor Company made 8D popular in the auto industry in the late 1980s through its "Team Oriented Problem Solving" approach. D0 was added later. Today it's used well beyond automotive, anywhere a customer expects a disciplined answer to "what happened, and what are you doing about it?"
The 8 disciplines (D0 to D8)
- Prepare and react. Decide whether this problem needs a full 8D. If anyone is at risk, take emergency action right away (stop shipments, warn the customer) before forming the team.
- Form the team. A small, cross-functional group with the knowledge, time and authority to fix it. Name a leader and a champion (sponsor) who can clear roadblocks.
- Describe the problem. State it as the customer sees it, in measurable terms. Use 5W2H (What, Where, When, Who, Why, How, How many) and an Is / Is Not table to narrow it down. No guessing at causes yet.
- Contain it. Protect the customer now, while you investigate. Find suspect product everywhere: in process, in stock, in transit and at the customer. Sort it, and record what you checked and what you found.
- Find and verify the root cause. Find two causes: why it happened (occurrence) and why you didn't catch it (escape). Use 5 Whys and a fishbone diagram, then prove the cause with data: ideally you can turn the problem on and off.
- Choose permanent corrective actions. For each verified root cause, pick the action that removes it, and show it will work (trial, test or data) before rolling it out.
- Implement and validate. Put the fix in place, remove containment only when the data says it's safe, and show over time that the problem is gone.
- Prevent recurrence. Make the fix permanent: update the FMEA, control plan, work instructions and training, and look for the same risk on similar products and lines.
- Recognize the team and close. Confirm the customer agrees it's closed, record lessons learned, and thank the people who did the work.
What goes in an 8D report?
The 8D report is the document that records each discipline. It's what a customer usually asks for when they send a complaint, and it's often updated in stages: the first version may only cover D0–D3 (what you know and how you're protecting them), with D4–D8 added as the investigation finishes.
| Section | What the reader wants to see |
|---|---|
| Header | Complaint number, part number, customer, dates, team leader, status |
| D2 Problem | A clear, measurable problem statement and the Is / Is Not facts |
| D3 Containment | Where you looked, how many you checked, how many were bad, and proof the containment works |
| D4 Root cause | Occurrence and escape root causes, with the evidence that proves them |
| D5–D6 Corrective action | The permanent fix for each root cause, who did it, when, and the data showing it worked |
| D7 Prevention | Which documents changed (FMEA, control plan, work instructions) and where else you applied the fix |
| D8 Closure | Lessons learned and sign-off |
D4 in practice: occurrence and escape
D4 is where most 8Ds succeed or fail. Two habits make the difference:
- Ask "why" for both paths. "Why did we make it?" leads to the process cause. "Why didn't we catch it?" leads to the detection gap. A good 8D fixes both.
- Verify, don't vote. A fishbone brainstorm gives you possible causes. Only data turns a possible cause into the root cause.
Here's what a short 5 Whys chain can look like (an illustrative example, not a real case):
| Why? | Occurrence: why did it happen? | Escape: why wasn't it caught? |
|---|---|---|
| 1 | Seal installed upside down | Final check only looks for "seal present" |
| 2 | Seal fits the groove either way | Camera program wasn't set to check orientation |
| 3 | No feature on the part or fixture prevents wrong orientation | Orientation wasn't listed as a requirement when the check was set up |
| → | Root cause: process allows the seal to be installed both ways (no error-proofing) | Root cause: detection requirement missing from the control plan |
Notice how both root causes point to a document or design to change, not a person to blame. That's usually a sign you've gone deep enough.
8D vs. 5 Whys, A3 and FMEA
| Tool | How it relates to 8D |
|---|---|
| 5 Whys / fishbone | Root cause tools you use inside D4. 8D is the full process around them. |
| A3 / PDCA | Similar logic on one page; common for internal improvement. 8D adds formal containment and is the usual format for customer complaints. |
| DMAIC | A longer, data-heavy project method for chronic problems or improvement goals. 8D is faster and aimed at a specific problem. |
| FMEA | Prevention, done before problems happen. In D7, every new cause an 8D finds should go into the FMEA. |
Common 8D mistakes
- Skipping containment to jump straight to the "fix." The customer needs protecting first.
- "Operator error" as the root cause. Ask why the process allowed the error. Retraining alone rarely stops a repeat.
- Only fixing the occurrence cause. If you don't fix the escape, the next different defect will slip through the same gap.
- Closing without proof. D6 needs data over time, not just "action complete."
- Never doing D7. If the FMEA and control plan didn't change, the lesson isn't saved.
8D questions people ask
What does 8D stand for?
Eight Disciplines: the eight steps D1 to D8 of the problem-solving method. Most versions add D0 for preparation and emergency response.
What is an 8D report?
The written record of an 8D: the problem description, containment, verified root causes, corrective actions, prevention steps and closure. Customers commonly request one when they report a defect.
How long does an 8D take?
It depends on the problem and on your customer's requirements. Containment usually comes first and fast; root cause and validation take longer because they need evidence. Follow any deadlines your customer sets.
Who should lead an 8D?
Someone who knows the product or process and can run a team meeting, usually from quality or engineering, with a champion (sponsor) who has the authority to approve changes.
Is 5 Whys enough on its own?
For a simple problem, sometimes. For a customer complaint, 5 Whys usually sits inside D4 of an 8D, which adds containment, verification and prevention around it.
