8D — Eight Disciplines Problem Solving

8D is a structured, team-based problem-solving methodology used to identify, correct, and prevent recurrence of quality problems. Developed by Ford Motor Company, it is the standard customer-facing corrective action format across the automotive supply chain.

Why companies use it

·Provides a standardised format for customer-facing corrective action reports, accepted across the automotive industry
·The structured approach prevents jumping to solutions before root cause is understood
·The containment step (D3) protects customers from continued exposure while root cause is being investigated
·D7 (Preventive Action) and D8 (Team Recognition) ensure learnings are embedded in the system, not just the individual

What hiring managers look for

·Customer-facing quality engineers spend a significant portion of their time writing 8D reports
·The ability to write a concise, credible 8D report under customer pressure is a practical skill
·Quality managers look for candidates who understand the difference between containment, correction, and prevention
·Experience using root cause analysis tools (5 Whys, fishbone, Is/Is Not) within the 8D framework is expected

Typical interview questions

Walk me through the 8 disciplines of the 8D methodology.

What is the difference between D3 (Containment) and D5 (Permanent Corrective Action)?

A customer has called with a field complaint about product failure. What do you do in the first 24 hours?

How do you verify that a root cause is the true root cause before implementing a corrective action?

Describe a real 8D you have led. What root cause analysis tools did you use and what was the corrective action?

Common mistakes

·Moving directly to D5 (Permanent Corrective Action) without establishing D3 (Containment) — customers keep receiving defects while you investigate
·Using 5 Whys and stopping at a proximate cause rather than the systemic root cause
·Writing D5 corrective actions that are actually containment actions — "sort and screen" is not a permanent fix
·Skipping D7 (Preventive Action) — preventing recurrence in similar products and processes is what distinguishes 8D from fire-fighting
·Documenting an 8D without evidence — root cause must be validated with data, not just asserted

Real engineering example

A supplier of precision machined aerospace components received a customer 8D request after flight-critical dimensions were found out of tolerance. D3 contained the problem by quarantining all parts from the same batch and expediting 100% inspection. Root cause analysis (5 Whys + Ishikawa) revealed that a worn cutting tool had not been flagged by the tool life management system due to a software configuration error. D5 corrective action fixed the configuration; D7 extended the check to all seven similar CNC cells across the facility.

Topics covered

8Dproblem solvingcorrective actionroot causeautomotivequality