Table of Contents
8D Problem Solving
A structured 9-step methodology for resolving complex quality problems as a team — from emergency response to systemic prevention.
Start Your 8D ReportWhat Is 8D Problem Solving?
8D (Eight Disciplines) is a team-oriented problem-solving methodology developed for complex, recurring quality issues. It distinguishes between the occurrence cause (why the defect happened) and the escape cause (why it was not caught), and drives systemic changes to prevent recurrence. It is widely required by automotive, aerospace, and defense customers (e.g., IATF 16949, AS9100).
When to Use 8D
- Customer complaints requiring a formal written response (e.g., 8D report submission)
- Recurring defects that simpler CAPA or corrective action approaches have not resolved
- Complex problems requiring cross-functional investigation (engineering, quality, production, supplier)
- Automotive or manufacturing supplier requirements (IATF 16949, VDA, Ford 8D, GM SQAM)
The 9 Disciplines (D0–D8)
Each discipline builds on the previous one. D0 is a pre-step that determines whether 8D is appropriate and captures any emergency actions already taken.
| Step | Discipline | Purpose |
|---|---|---|
| D0 | Planning & Prerequisites | Capture emergency actions already taken and confirm 8D is the right approach |
| D1 | Team Formation | Assemble a cross-functional team with the skills to solve the problem |
| D2 | Problem Description | Define the problem clearly using Is/Is-Not analysis and 5W2H questions |
| D3 | Interim Containment | Protect the customer immediately while root cause analysis proceeds |
| D4 | Root Cause Analysis | Identify both the occurrence cause and the escape cause using 5 Whys, Fishbone, or other methods |
| D5 | Permanent Corrective Actions | Choose actions that directly eliminate the root cause — measurable and owned |
| D6 | Implement & Validate PCAs | Implement the corrective actions and confirm they work without creating new problems |
| D7 | Prevent Recurrence | Update systems, procedures, FMEA, and training to prevent the same problem in similar processes |
| D8 | Closure & Team Recognition | Formally close the 8D, document lessons learned, and recognize the team's efforts |
Tips for a Strong 8D
- Keep your team cross-functional — include people closest to the problem, not just quality engineers
- In D4, always distinguish the occurrence cause from the escape cause — they often require different corrective actions
- Use the Is/Is-Not analysis in D2 before starting root cause — it often eliminates 80% of unlikely causes immediately
- D7 is the most commonly skipped step — systemic changes (FMEA, control plans, training) are what prevent recurrence across all similar processes
Frequently Asked Questions
What is the difference between 8D and CAPA?
CAPA is a general framework for corrective and preventive action. 8D is a more structured, team-based methodology with explicit steps for containment, Is/Is-Not problem definition, escape cause analysis, and team recognition. 8D is preferred when customer-facing documentation is required or when root cause is unknown and cross-functional investigation is needed.
Does 8D require authentication?
No — the 8D tool is fully free and anonymous. No account is required to complete a report or download the PDF. Creating a free account lets you save and share reports by link.
Can I link my 5 Whys or Fishbone report to the 8D?
Yes — in step D4 you can paste the report ID from a 5 Whys RCA or Fishbone diagram analysis. The 8D PDF will reference those reports in the root cause section.