Ford 8D Problem Solving Roadmap
The complete 8 Disciplines (D0–D8) of Ford's structured problem-solving methodology. Each discipline includes the key question, recommended techniques, 8D report deliverables, and direct links to CILS Tools Hub.
D4 Dual Root Cause Requirement — Root Cause AND Escape Point
The Ford 8D methodology explicitly requires two root causes to be identified in D4:
Root Cause of the Defect
Why did the defect occur? What process, design, or system failure caused the non-conformance?
Escape Point (Why it reached the Customer)
Why did the detection/control system fail to catch the defect before it reached the customer?
Both must be addressed with separate PCAs in D5/D6 and systemic actions in D7.
ICA vs PCA vs ERA — Understanding the Difference
ERA (D0)
Emergency Response Action
Immediate customer-protection action before root cause is known. Reactive. Can be "None Required".
ICA (D3)
Interim Containment Action
Temporary band-aid to contain the symptom while root cause is being found. Must be removed when PCA is validated.
PCA (D5/D6)
Permanent Corrective Action
Permanently eliminates the root cause AND the escape point. Verified in production. Replaces the ICA.
How to Structure a Ford 8D Problem Solving Report
What is an 8D Report? The 8D report is the structured document that records all eight disciplines. It serves as the official evidence of your corrective action process for customers, regulators, and internal quality systems. Every field must be completed with factual, data-backed statements.
D0 — Trigger and ERA: Document whether an ERA was needed and what was done. Even "None Required" must be a documented decision.
D2 — Problem Statement quality: The D2 Is/Is Not table is the centrepiece of the report. Every dimension (Object, Defect, Location, Time, Magnitude) must be populated. A vague D2 leads to wrong root cause conclusions in D4.
D4 — Two root causes: The report must show separate sections for Root Cause of the defect and Root Cause of the escape. Each must be verified with data — not just stated.
D6 — Validation evidence: Include control charts, capability data (Cpk before/after), or field return data showing the PCA is working in production. This is the most-scrutinised section by customers.
D7 — Systemic actions: This section is what separates a good 8D from a great one. Show updated FMEAs, revised SOPs, Poka-Yoke installations, and horizontal deployment actions. Many customers audit D7 specifically.
Timing: An initial response (D0-D3) is typically expected within 24-48 hours. A complete 8D is typically expected within 30 days. Complex problems may require 60-90 days — communicate timeline to customer proactively.
8D vs DMAIC — When to Use Each
Ford 8D — Use When:
- External customer complaint or warranty return
- Safety or regulatory quality escape
- Supplier quality issue requiring formal SCAR response
- Specific, known defect with an identifiable symptom
- Response needed within days/weeks
- Customer requires an 8D format response
DMAIC Six Sigma — Use When:
- Chronic, systemic process problem (not a single event)
- Root cause is unknown and multiple factors are suspected
- Statistical analysis and DOE needed
- Project runs over 3-12 months
- Significant data collection and baseline study needed
- Breakthrough improvement in process sigma is the goal
Note: 8D and DMAIC are complementary — an 8D D4 root cause analysis often uses the same statistical tools as DMAIC Analyse phase. The key difference is scope, timeline, and trigger.