Eightd

8D Problem Solving Skill

Overview

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

8D Phase Overview

D0: Prepare for the 8D Process

Emergency Response Actions (ERA)

Before formal 8D begins, immediate actions to protect:

1. Customer Protection

   • Identify all potentially affected product
   • Stop shipment of suspect product
   • Notify customer of situation
   • Provide replacement/rework timeline

2. Symptom Assessment

   • What is the symptom?
   • When was it first detected?
   • How much product is affected?
   • Is this a safety/regulatory issue?

3. **8D Trigger Criteria

D0 Outputs

• Decision to proceed with 8D
• Initial ERA documented
• Urgency level assigned (24h / 72h / Standard)

D1: Establish the Team

Team Composition

Team Size

• Ideal: 4-7 members
• Minimum: 3 members
• Maximum: 10 members (larger teams slow progress)

D1 Outputs

• Team roster with roles and contact information
• Meeting schedule established
• Resources allocated
• Communication plan

D2: Describe the Problem

Problem Description Techniques

5W2H Analysis:

IS / IS NOT Analysis:

Problem Statement Format

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)

D2 Outputs

• Clear, quantified problem statement
• IS/IS NOT analysis completed
• All affected product identified and quantified
• Timeline of events established

D3: Interim Containment Actions (ICA)

Containment Scope

Containment Actions

1. Sort - 100% inspection to separate good/bad
2. Hold - Quarantine suspect product
3. Replace - Provide conforming product
4. Enhanced inspection - Temporary additional checks
5. Process change - Temporary parameter adjustment

Containment Verification

Before releasing containment:

• Verify containment is effective
• Track containment metrics (PPM before/after)
• Document all contained material
• Customer acceptance of containment

Escape Point Analysis

Critical Question: Where should this have been caught?

D3 Outputs

• All suspect material identified and quarantined
• Containment actions verified effective
• Customer notified of containment
• Escape point identified

D4: Root Cause Analysis

Root Cause Categories

Occurrence Root Cause: Why did the defect occur?

• Process, machine, material, method, environment

Detection Root Cause (Escape Point): Why wasn't it caught?

• Inspection method, frequency, capability, training

Root Cause Analysis Tools

5-Why Guidelines

Root Cause Verification

Verification Methods:

Root cause is verified when:

• Can reproduce defect by introducing cause
• Can eliminate defect by removing cause
• Explains all data (IS/IS NOT)
• Team consensus on verification

D4 Outputs

• Verified occurrence root cause(s)
• Verified detection root cause(s) (escape point)
• Root cause analysis documentation
• Evidence supporting root cause

D5: Develop Corrective Actions

Corrective Action Types

Corrective Action Hierarchy

Prefer higher-order controls:

Corrective Action Criteria

Each corrective action must be:

• Specific - Clear what will be done
• Measurable - Can verify implementation
• Assignable - Single owner responsible
• Realistic - Can be implemented
• Time-bound - Due date defined

Risk Assessment

Before implementing corrective actions:

• Will action introduce new risks?
• Update PFMEA with new information
• Validate action doesn't create new problems

D5 Outputs

• List of corrective actions with owners and dates
• Risk assessment of each action
• PFMEA updates identified
• Control Plan updates identified

D6: Implement and Verify Corrective Actions

Implementation Steps

1. Plan - Detailed implementation plan
2. Communicate - Notify all affected parties
3. Train - Train operators on changes
4. Execute - Implement changes
5. Verify - Confirm actions completed
6. Validate - Confirm actions are effective

Verification vs Validation

Effectiveness Verification

D6 Outputs

• All corrective actions implemented
• Implementation verification completed
• Effectiveness validation initiated
• Updated documentation (WI, Control Plan, FMEA)

D7: Prevent Recurrence

Systemic Prevention Actions

Horizontal Deployment

Apply learning across:

• Similar parts on same equipment
• Similar processes in other areas
• Similar failure modes in PFMEA
• Supplier processes if applicable

D7 Outputs

• FMEA updated with new failure mode
• Control Plan updated
• Work instructions revised
• Training completed
• Lessons learned documented
• Horizontal deployment completed

D8: Recognise Team and Close

Closure Criteria

• Root cause verified
• All corrective actions implemented
• Effectiveness verified (no recurrence period)
• FMEA/Control Plan updated
• Work instructions updated
• Training completed
• Customer accepts closure (if customer complaint)
• Lessons learned documented

Team Recognition

• Acknowledge team contribution
• Share success with organisation
• Consider formal recognition programme

8D Archive

Retain 8D reports for:

• Customer-required retention period
• Minimum 3 years per IATF 16949
• Accessible for reference and audits

D8 Outputs

• 8D report complete and approved
• Customer acceptance (if applicable)
• Archive in quality records
• Team recognised

Templates

• templates/8d-report.md - Full 8D report template

Reference Materials

• reference/root-cause-tools.md - 5-Why, Fishbone, IS/IS NOT
• reference/verification-methods.md - How to verify root cause and effectiveness

MNMUK-Specific Guidelines

Response Timeframes

8D Numbering

Format: 8D-[YYYY]-[SEQ] Example: 8D-2026-001

Approval Authority

Quick Reference

# 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"