Structured 8D problem solving for customer complaints and quality issues. D0-D8 phases with containment, root cause analysis, and escape point identification. USE WHEN user says '8D', 'eight disciplines', 'customer complaint', 'corrective action', 'root cause analysis', 'containment', 'escape point', or 'problem solving report'.
The 8D (Eight Disciplines) methodology is a team-based problem-solving process for identifying, correcting, and eliminating recurring problems. Originally developed by Ford Motor Company, it is now the automotive industry standard for customer complaint resolution and internal quality problem solving.
| Skill | Integration Point |
|---|---|
| A3CriticalThinking | Root cause analysis methods |
| PFMEA | Update FMEAs with new failure modes discovered |
| ControlPlan | Update Control Plans with new controls |
| AutomotiveManufacturing | Work instructions and process changes |
| InternalAudit | Verify effectiveness through audit |
| Phase | Name | Purpose | Timeframe |
|---|---|---|---|
| D0 | Prepare | Emergency response, symptom assessment | Immediate |
| D1 | Team | Form cross-functional team | 24 hours |
| D2 | Problem | Define problem clearly | 48 hours |
| D3 | Containment | Protect customer, stop bleeding | 24-72 hours |
| D4 | Root Cause | Identify true root cause(s) | 2-4 weeks |
| D5 | Corrective Actions | Develop permanent solutions | 2-4 weeks |
| D6 | Implementation | Implement and verify | 1-4 weeks |
| D7 | Prevention | Prevent recurrence systemically | Ongoing |
| D8 | Closure | Recognise team, close report | After verification |
Before formal 8D begins, immediate actions to protect:
Customer Protection
Symptom Assessment
**8D Trigger Criteria
| Trigger | 8D Required? |
|---|---|
| Customer complaint | Yes |
| Field failure | Yes |
| Safety/regulatory | Yes (expedited) |
| Internal scrap >threshold | Recommended |
| Repeat occurrence | Yes |
| High severity PFMEA item | Recommended |
| Role | Responsibility | Required? |
|---|---|---|
| Champion/Sponsor | Remove barriers, approve resources | Yes |
| Team Leader | Coordinate activities, report status | Yes |
| Process Expert | Deep process knowledge | Yes |
| Quality Engineer | Data analysis, methodology | Yes |
| Production Rep | Shop floor perspective | Yes |
| Customer Rep | Customer perspective | If applicable |
| Supplier Rep | Supplier perspective | If applicable |
| Subject Matter Experts | Specific technical knowledge | As needed |
5W2H Analysis:
| Question | Answer |
|---|---|
| What is the problem? | Specific defect/symptom |
| Where was it found? | Location (customer, inspection, operation) |
| When was it found? | Date, time, shift, production lot |
| Who found it? | Person, inspection method |
| Why is it a problem? | Impact to customer/function |
| How many are affected? | Quantity, frequency, trend |
| How was it detected? | Detection method used |
IS / IS NOT Analysis:
| Factor | IS | IS NOT | Distinction |
|---|---|---|---|
| What | [Observed defect] | [Similar but not this] | |
| Where | [Location found] | [Where not found] | |
| When | [Time first seen] | [Time not seen] | |
| Extent | [Scope affected] | [Not affected] |
Good problem statement:
"Outer diameter of part #12345 measures 25.08-25.12mm (spec: 25.00 ±0.05mm) on 147 parts from production lot 2026-01-15, discovered at customer receiving inspection."
Bad problem statement:
"Parts are out of spec" (too vague)
| Location | Action Required |
|---|---|
| In-process (WIP) | Quarantine, sort, disposition |
| Finished goods | Quarantine, sort, disposition |
| In-transit | Recall or intercept |
| At customer | Sort, replace, rework on-site |
| In field | Service campaign if needed |
Before releasing containment:
Critical Question: Where should this have been caught?
| Stage | Did we have detection? | Why did it escape? |
|---|---|---|
| Source inspection | ||
| In-process inspection | ||
| Final inspection | ||
| Functional test | ||
| Audit |
Occurrence Root Cause: Why did the defect occur?
Detection Root Cause (Escape Point): Why wasn't it caught?
| Tool | Best For | Reference |
|---|---|---|
| 5-Why | Simple cause chains | reference/root-cause-tools.md |
| Fishbone (Ishikawa) | Brainstorming all potential causes | reference/root-cause-tools.md |
| IS/IS NOT | Narrowing down causes | D2 output |
| Comparative Analysis | When similar items are OK | Compare good vs bad |
| Timeline Analysis | Process-related issues | Sequence of events |
| Fault Tree | Complex failure modes | Top-down logic |
| Guideline | Description |
|---|---|
| Ask "why" until physical root cause | Not stopping at symptoms |
| Stay in your control | Don't blame customer or supplier without evidence |
| Verify each step | Each "because" must be proven |
| Multiple branches OK | May have multiple root causes |
| Stop when actionable | Root cause should suggest solution |
Verification Methods:
| Method | Description |
|---|---|
| Re-creation | Reproduce defect by applying root cause |
| Elimination | Remove root cause, verify defect stops |
| Statistical correlation | Data shows cause-effect relationship |
| Physical evidence | Forensic analysis confirms cause |
Root cause is verified when:
| Type | Addresses | Example |
|---|---|---|
| Permanent Corrective Action (PCA) | Occurrence root cause | Change process parameter |
| Detection Improvement | Escape point | Add inspection step |
| Systemic Prevention | Recurrence | Update FMEA/Control Plan |
Prefer higher-order controls:
| Level | Type | Effectiveness | Example |
|---|---|---|---|
| 1 | Eliminate | Highest | Design change removes failure mode |
| 2 | Substitute | High | Different material/process |
| 3 | Engineering control | Medium-High | Poka-yoke, fixture change |
| 4 | Administrative | Medium | Procedure change, training |
| 5 | Detection | Lowest | Additional inspection |
Each corrective action must be:
Before implementing corrective actions:
| Verification | Validation |
|---|---|
| Did we implement the action correctly? | Did the action solve the problem? |
| Check implementation | Check effectiveness |
| Immediate | Over time |
| Method | Description | Duration |
|---|---|---|
| Before/After comparison | Metric improvement | 1-3 months data |
| Control chart | Process stability | 25+ subgroups |
| Capability study | Cpk improvement | Per standard |
| Audit | Process compliance | Scheduled |
| Zero defects | No recurrence | 3-6 months |
| System | Update Required |
|---|---|
| PFMEA | Add failure mode, update S/O/D, add controls |
| Control Plan | Add/modify inspection, update reaction plan |
| Work Instructions | Incorporate process changes |
| Training | Update training materials, retrain |
| Lessons Learned | Document for future reference |
| Similar Products | Apply to similar parts/processes |
Apply learning across:
Retain 8D reports for:
templates/8d-report.md - Full 8D report templatereference/root-cause-tools.md - 5-Why, Fishbone, IS/IS NOTreference/verification-methods.md - How to verify root cause and effectiveness| Customer | ICA Due | RCA Due | Full 8D Due |
|---|---|---|---|
| OEM Tier 1 | 24 hours | 10 days | 30 days |
| Standard | 48 hours | 15 days | 45 days |
| Internal | 72 hours | 20 days | 60 days |
Format: 8D-[YYYY]-[SEQ]
Example: 8D-2026-001
| Severity | Approval Required |
|---|---|
| Safety/Regulatory | Quality Manager + GM |
| Customer complaint | Quality Manager |
| Internal >£1000 | Quality Manager |
| Internal <£1000 | Quality Engineer |
# Generate 8D for customer complaint
"Create 8D for customer complaint: [describe problem]"
# Root cause analysis assistance
"Help me do 5-Why analysis for [problem]"
"Generate fishbone diagram for [defect type]"
# Corrective action development
"Recommend corrective actions for [root cause]"
# 8D review
"Review this 8D for completeness"