The formal complaint lands and the customer email asks for "a complete 8D by Friday." Half the plants I know open the last 8D they closed, swap the part number and the date, and send it out. The customer always notices.
The 8D, eight disciplines, is a structured problem solving method in eight steps, from forming the team to preventing recurrence, used mostly by automotive and corporate customers when a formal complaint demands a documented response.
D1 through D3: before anyone touches the cause
D1 forms the team, and it has to be cross functional: process, quality, maintenance and someone from the floor, not just quality signing alone. D2 describes the problem, and the same rule applies here as in any root cause analysis: what fails, where, since when and how much, with data instead of adjectives.
D3 is containment: the temporary action that protects the customer while the investigation runs. You can tell when a plant confuses D3 with the final fix, because then containment stays installed forever and nobody ever goes back to the real problem.
D4: this is where the fishbone diagram and the 5 whys live
D4 is root cause analysis, and it is where everything else I work with teams actually lives: the fishbone diagram to open the fan of possible causes, the 5 whys to drive down to the origin on the branch that survives, and the discipline of requiring evidence before accepting either one. A D4 without those three pieces is an opinion with a discipline number attached.
You have seen the first three disciplines. Now comes the one that decides whether the whole 8D was worth anything.
D5 is where nearly every 8D falls short
D5 defines the permanent corrective actions, and this is where I see the same mistake I see in FMEA. The fastest action to write is usually a detection action, one more inspection, instead of an occurrence action, the one that actually lowers how many defects get made. A D5 full of new inspections looks great at audit and does nothing to scrap.
Every permanent action you choose in D5 should go back and update your FMEA, because the 8D describes a failure the FMEA did not see or rated wrong. If that update never happens, the FMEA keeps describing a process that no longer exists, and the next 8D on the same line starts over from zero.
D6 through D8: implement, prevent and close it well
D6 implements and validates that the permanent action actually worked, using the same data used to prove the cause, not an opinion that "it looks better now." D7 is prevention: checking whether the same failure mode can exist on other lines, other products or the design FMEA, not just closing the line where it appeared. D8 recognizes the team, and it sounds minor, but it is the discipline that decides whether the next formal complaint finds people willing to sit down again.
Three ways an 8D stays a format
- Copying the last 8D and only swapping the part number and the date. The customer always notices.
- Moving to D5 without D4 having a cause proven by evidence. Corrective actions built on an unproven cause almost never correct anything.
- Closing D7 without touching the FMEA or the control plan. Prevention that never gets written into a document lives only as long as someone remembers it.
Start here
Open the last 8D you closed. Check D5: count how many actions lower occurrence and how many only lower detection. If the second column is longer, that 8D was complete on paper and short on results.
The 8D workshop runs 16 hours on a real case from your plant, with follow up coaching on days 10, 20 and 45. If you already have the formal complaint on your desk, tell me which line it is on.
What is the difference between 8D and A3?
8D is what automotive and corporate customers usually require when there is a formal complaint, with a fixed eight discipline format. A3 is more flexible and works better for internal improvement. Many plants use both, depending on who is asking.
Why did my 8D not lower scrap even though it passed the audit?
Almost always because D5 got filled with detection actions, which find more defects, instead of occurrence actions, which make fewer. Check that box first.
Does an 8D have to update the FMEA?
Yes, if you want it to matter. The 8D describes a failure the FMEA did not anticipate or rated wrong. Without that update, the FMEA keeps describing a process that has already changed.