The 8D steps explained
The eight disciplines are ordered on purpose: each step depends on the quality of the one before it. A weak problem statement in D3 will corrupt every root cause candidate in D4. This page describes what actually happens in each step in a real investigation, and where each step commonly fails.
Key takeaways
- D1: pick the smallest team that can actually decide, not the largest that could attend.
- D2: describe the problem with observable facts, scope, timing and affected quantity.
- D3: contain the suspect population while the investigation continues.
- D4: prove the root cause by turning the defect on and off — not just by explaining it.
- D5–D6: select a permanent corrective action, then implement and validate it with objective evidence.
- D7–D8: update PFMEA, control plan and lessons learned before closure.
The 8D workflow graph
The end-to-end investigation path
The trigger is a real defect, complaint, escape or repeated nonconformance that needs a structured response.
Assemble the team, stop the bleed and describe the problem precisely before any root-cause work starts.
Use evidence to prove the cause and then verify the corrective action in production.
Standardise the fix and update the management system so the same failure cannot reappear elsewhere.
Close the loop, capture lessons learned and make the case searchable for the next team.
D1 — Establish the team
Assemble a cross-functional team with process knowledge, product knowledge, customer knowledge and the authority to change things. A team of ten with no decision-makers will not close an 8D.
- Sponsor or champion (authority to allocate resources).
- Team leader (owns the 8D end-to-end).
- Subject-matter experts: process, product, quality, supplier.
- Customer contact (or single interface to the customer).
D2 — Problem Description
Define the problem with measurable facts before assigning a cause. Use Is / Is-Not to state what happened and what did not happen, then quantify the scope.
- What: exact defect signature or complaint.
- Where: line, cavity, tool, shift, plant or region.
- When: first and last observation, frequency and pattern.
- How many: affected units out of the relevant population.
D3 — Interim Containment
Protect the customer and the suspect population while the investigation continues. Define the containment scope, owner, method, traceability and exit criterion; containment is not proof of a cause.
- Quarantine or controlled hold for the defined suspect population.
- Sorting or inspection method where appropriate.
- Clear ownership and customer communication.
- Evidence that containment is operating and can eventually exit.
D4 — Identify the root cause
Identify the root cause of the defect (why it happened) and the escape cause (why controls did not catch it). Both must be proven, not asserted.
Proof means you can reproduce the defect by turning the suspected cause on, and prevent it by turning it off. If you cannot switch the defect on and off, you have a hypothesis — not a root cause.
D5–D6 — Corrective action and verification
D5 selects permanent corrective actions. D6 implements them in production and verifies that the defect does not recur. Verification uses production data over a defined observation window — not a one-off lab result.
D7–D8 — Prevent and close
D7 updates the systems that allowed the escape: PFMEA, control plan, work instructions, poka-yoke, supplier requirements, training. D8 closes the case, recognises the team and captures lessons learned so a similar problem does not require a new 8D.
Frequently asked questions
- What is the difference between root cause and escape cause?
- Root cause explains why the defect was produced. Escape cause explains why detection controls did not catch it. Every 8D needs both.
- How many people should be on an 8D team?
- Usually 4–7. Small enough to decide, cross-functional enough to cover process, product, quality and the customer interface.
- Can I run D2 and D3 in parallel?
- Problem description and interim containment may run in parallel. What you cannot do is start D4 before D2 is quantified and the immediate risk is controlled.
Related guides
Run this D-step inside a structured workspace
Qhubio is a structured 8D workspace: evidence-grounded phases, phase-gated approvals and audit-ready exports.