8D Problem Solving Guide
Structured approach to root cause analysis.
What is 8D?
8D (Eight Disciplines) is a structured problem-solving methodology developed by Ford Motor Company to identify, correct, and eliminate recurring problems.
When to Use 8D
- Customer Complaints: Formal response to customer quality issues
- Recurring Problems: Issues that keep happening despite corrections
- Major NCRs: Significant non-conformances requiring thorough investigation
- Safety Issues: Problems affecting product safety or regulatory compliance
- Supplier Quality: Formal problem resolution with suppliers
The 8 Disciplines
D0: Prepare & Plan
Purpose: Emergency response and initial assessment
- Determine if 8D is appropriate
- Implement emergency response actions
- Gather initial symptom data
- Estimate resources needed
D1: Establish the Team
Purpose: Form a cross-functional team
- Identify team members with process knowledge
- Assign team leader/champion
- Define roles and responsibilities
- Establish meeting cadence
D2: Describe the Problem
Purpose: Define the problem clearly
- Use 5W2H (Who, What, Where, When, Why, How, How Many)
- Quantify the problem with data
- Distinguish symptoms from causes
- Document IS/IS NOT analysis
D3: Interim Containment Actions
Purpose: Protect the customer
- Implement temporary fixes
- Sort/screen suspect inventory
- Increase inspection frequency
- Verify containment effectiveness
D4: Root Cause Analysis
Purpose: Find the true root cause
- Use 5-Whys analysis
- Create Ishikawa (fishbone) diagram
- Verify root cause with data
- Identify escape point
D5: Permanent Corrective Actions
Purpose: Develop long-term solutions
- Identify potential solutions
- Evaluate alternatives
- Select best corrective action
- Verify no new problems created
D6: Implement & Validate
Purpose: Put solutions in place
- Implement corrective actions
- Remove containment actions
- Monitor results
- Confirm problem is solved
D7: Prevent Recurrence
Purpose: Systemic prevention
- Update procedures and standards
- Modify FMEA and Control Plans
- Share lessons learned
- Apply to similar products/processes
D8: Congratulate the Team
Purpose: Recognize team efforts and close the 8D
- Acknowledge individual and team contributions
- Document lessons learned
- Archive the 8D report
- Celebrate success
Creating an 8D Report in Buttress QMS
Step-by-Step Guide
Step 1: Navigate to 8D
Click 8D in the left sidebar, then click + New 8D Report
Step 2: Enter Basic Information
- Title: Brief description of the problem
- Source: Customer complaint, NCR, audit finding, etc.
- Supplier: If supplier-related
- Part Number: Affected product
- Customer: If customer-initiated
Step 3: Work Through Each Discipline
Complete each D0-D8 section with evidence, dates, and responsible parties. Each section can be saved independently as you progress.
Step 4: Attach Documents
Upload supporting evidence: photos, data, analysis worksheets, test results.
Step 5: Submit for Review
Once complete, submit the 8D for approval. Generate a PDF report for customer submission if needed.
Root Cause Analysis Tools
5-Whys Analysis
Ask "Why?" repeatedly (typically 5 times) to drill down to the root cause.
Problem: Customer received incorrect parts
Why 1: Wrong parts were shipped → Packaging error
Why 2: Operator picked wrong bin → Bins not clearly labeled
Why 3: Labels faded → Labels exposed to sunlight
Why 4: Bins near window → Warehouse layout issue
Why 5: No layout standard → Root cause: No warehouse layout procedure
Ishikawa (Fishbone) Diagram
Organize potential causes into categories:
- Man: People, training, skills
- Machine: Equipment, tools, maintenance
- Material: Raw materials, components
- Method: Procedures, processes
- Measurement: Inspection, calibration
- Environment: Conditions, workspace
8D Workflow
8D Status Flow
Creating
Working D1-D7
Awaiting approval
D8 complete
Typical Timeline
- D0-D3: Within 24-48 hours (containment is urgent)
- D4-D5: 1-2 weeks (thorough analysis needed)
- D6: Depends on corrective action complexity
- D7-D8: After verification period (30-90 days typical)
8D Best Practices
Do:
- Contain first, then investigate
- Include cross-functional team members
- Use data to verify root cause
- Document everything
- Communicate progress to stakeholders
- Allow time for verification
Don't:
- Skip containment to save time
- Blame individuals
- Accept "human error" as root cause
- Close without verification data
- Forget to update FMEA/Control Plans
- Rush through D4 root cause