When a customer reports a quality problem, they want three things: protection from more bad parts, an understanding of why it happened, and confidence it won't happen again. The 8D method — eight disciplines — is a widely used, structured approach that delivers all three. It originated in the automotive industry and is now common across manufacturing, especially where customers request a formal problem-solving report.
D0: Prepare and decide whether 8D is needed
Not every problem needs 8D. Use it for customer complaints, repeated defects, safety-related issues or problems with significant cost. Gather initial information: what product, how many, where found, and whether the customer has given deadlines.
D1: Form the team
Assemble a small cross-functional team with the knowledge to solve the problem: quality, production, engineering, maintenance, and suppliers where relevant. Appoint a leader responsible for driving the 8D to completion.
D2: Describe the problem
Define the problem precisely. A useful approach is "is / is not": what is the defect, and what similar defect is not occurring; where is it found, and where not; when did it start, and when not; how many, and how many not. A precise description narrows the search for causes. Include photos, measurements and quantities.
D3: Containment actions
Protect the customer immediately. Containment may include sorting stock at your site, in transit and at the customer, adding 100% inspection temporarily, holding suspect lots, or supplying replacement parts. Containment is not the solution — it buys time to find one. Record what was contained, where and with what result.
D4: Root cause analysis
Find why the problem occurred and why it wasn't detected. Tools include 5 Why, fishbone (Ishikawa) diagrams, process data analysis and experiments. Verify the root cause: can you switch the problem on and off by changing the suspected cause? Address two root causes:
- Occurrence root cause — why the defect was created.
- Escape root cause — why the defect wasn't detected before it reached the customer.
See 5 Why analysis.
D5: Choose and verify permanent corrective actions
Select actions that eliminate the root causes — not just inspect them out. Examples: modify the process, add error-proofing, change a tool, revise a specification, improve a supplier's process. Verify that each action will work before full implementation, through trials or analysis.
D6: Implement and validate
Implement the corrective actions, remove containment once they're proven effective, and validate with data — for example, several production lots with no recurrence. Record evidence of implementation and results.
D7: Prevent recurrence
Extend the learning: update FMEAs, control plans, work instructions and training; apply the fix to similar products and processes; update design standards. This step turns one solved problem into a systemic improvement.
D8: Recognise the team and close
Close the 8D formally, share lessons learned and recognise the team's contribution. Recognition matters: it encourages thorough problem solving next time.
Common 8D mistakes
- Treating containment as the solution.
- Stopping at "operator error" as a root cause.
- Not verifying the root cause.
- Ignoring the escape root cause.
- Corrective actions that rely on "more careful inspection".
- Never checking effectiveness after closure.
Linking 8D to your quality system
8D is most powerful when connected to complaints, NCRs and CAPA. A complaint opens an 8D; containment and corrective actions become tracked CAPA items with owners and due dates; effectiveness checks are scheduled automatically; lessons feed into control plans and FMEAs. See CAPA software.
Customer formats and timelines
Many customers expect containment (D3) within 24 hours, root cause (D4) within days and full closure within weeks, using their own report format. Software that guides each discipline and generates reports in the required format saves time and keeps you within deadlines. See complaint management.
Talk to us about digitising 8D and CAPA.
A short example
A customer reports cracked plastic housings at assembly. D1: team of quality, moulding supervisor, tool room and process engineer. D2: cracks at one boss, from three lots produced in one week, on one cavity of a four-cavity mould. D3: stock at the plant and in transit sorted; suspect cavity blocked; 100% inspection of the boss added temporarily. D4: occurrence root cause — a cooling channel partially blocked in that cavity, causing residual stress; escape root cause — the visual check didn't include that boss and the crack appeared only under assembly load. D5–D6: cooling channel cleaned and a flow check added to mould maintenance; assembly-load test added to first-piece approval; containment removed after five clean lots. D7: flow checks added to all moulds' PM plans; control plan updated. D8: team recognised and lessons shared with the tool room.
Frequently asked questions
When should we use 8D instead of a simpler method?
Use 8D for significant problems — customer complaints, recurring defects, safety-related issues — where a structured, documented approach is needed. Simpler problems can use 5 Why.
How long should an 8D take?
Containment within hours or a day; root cause and corrective action often within weeks. Customers usually set timelines for each step.
Who should be on the 8D team?
People with knowledge of the product and process — quality, production, engineering, and sometimes suppliers or maintenance.
What's the difference between occurrence and escape root causes?
Occurrence explains why the defect was created; escape explains why it wasn't detected before reaching the customer. Good 8Ds address both.
Can 8D reports be generated by software?
Yes. Complaint and CAPA software can guide each discipline and generate the 8D report in the customer's format.
Can 8D be used for supplier problems?
Yes. Many manufacturers require suppliers to submit 8D reports for supplier-caused defects, and track their responses and effectiveness in the same system as internal 8Ds.
