The 8D problem-solving process, without the box-ticking
8D is the discipline most quality teams claim to run and few run well — usually because they collapse three different jobs (stop it, fix it, prevent it) into one. Here is what each step is actually for.
8D ("Eight Disciplines") is a structured method for resolving recurring defects. The steps run D0 plan → D1 team → D2 describe the problem → D3 interim containment → D4 root cause → D5 permanent corrective action → D6 implement & validate → D7 prevent recurrence → D8 close & recognize the team. The discipline that matters most: containment, correction, and prevention are three separate jobs — screening out bad parts is not the same as fixing the cause, which is not the same as stopping it from ever returning.
The nine disciplines
- D0Plan & emergency response. Decide 8D is warranted, and if the situation is dangerous, contain immediately — before the formal team even forms.
- D1Build the team. Cross-functional, with the process knowledge and authority to actually change things. Wrong team, wrong fix.
- D2Describe the problem. Specific and quantified — what, where, when, how many (5W2H). "Bad parts" is not a problem statement; "12% short shots on cavity 3 since the resin lot change" is.
- D3Interim containment. Stop defective product reaching the customer while the cause is still unknown: 100% screening, quarantine, rework. Temporary by design.
- D4Identify & verify root cause. Not the first plausible cause — the verified one. Tools: 5 Whys, fishbone, and turning the cause on and off to confirm it.
- D5Choose & verify corrective action. Select the permanent fix for the verified cause and prove it works before rollout.
- D6Implement & validate. Deploy it and confirm the defect rate actually dropped and stayed down — with data, not optimism.
- D7Prevent recurrence. Change the systems that allowed it: update the control plan and FMEA, error-proof the step, propagate the lesson to sister lines.
- D8Close & recognize. Document, close, and credit the team. Skipping this quietly kills the appetite for the next 8D.
Where teams go wrong
- Stopping at containment. Screening becomes permanent because the cause was never found. You are now paying forever to catch a defect you could have eliminated.
- Skipping verification (D4). Acting on the first guess. If you never turned the suspected cause on and off, you have a hypothesis, not a root cause.
- Confusing D5 with D7. Fixing this batch's cause without changing the system that let it happen — so it returns through a different door six months later.
- No data at D6. Declaring victory without confirming the rate dropped. Verification is a measurement, not a meeting.
Where this gets slow by hand
The bottleneck is rarely the template — it is D2 and D4. Writing a quantified problem description means pulling production records, defect logs, material lots and process traces into one timeline. Verifying root cause means correlating that defect against process drift, incoming material, and equipment history across batches. Done manually, that assembly is the multi-week part of a "two-week" 8D, and it is where weak problem statements and unverified causes slip through.
A quantified D2 and a verified D4, in minutes
Niobia assembles the problem description from the actual data — defect rate, affected units, the change point — and correlates the defect against process drift (SPC), incoming material, and equipment history to surface and rank candidate root causes. It fuses signals that normally live in separate tools into one testable hypothesis, then files the closed investigation as searchable institutional memory — so the next time the same signature appears, the matching 8D surfaces instantly instead of being re-solved from scratch. The disciplines stay yours to run; the weeks of data assembly don't.
Frequently asked
What are the 8 disciplines of 8D?
D1 build the team, D2 describe the problem, D3 implement interim containment, D4 identify and verify the root cause, D5 choose and verify the permanent corrective action, D6 implement and validate it, D7 prevent recurrence, and D8 recognize the team. A preliminary D0 plans the response and triggers emergency containment if needed — nine steps in total.
What is the difference between containment and corrective action?
Containment (D3) is temporary: it stops defective product reaching the customer while the cause is still unknown — 100% screening, quarantine. Corrective action (D5–D6) addresses the verified root cause so the defect stops being produced. Containment buys time; corrective action fixes the problem.
Why does 8D separate root cause from prevention?
Fixing the root cause (D5–D6) stops the current defect, but D7 prevents recurrence by changing the systems that allowed it — updating control plans and FMEA, error-proofing the step, and propagating the lesson to sister lines so the failure cannot return through a different door.