What is the 8D problem-solving process?
8D problem-solving process
The 8D problem-solving process provides a clear, eight-step framework to correct product and process problems. Each discipline guides teams on what to do and when to do it. 8D is used across many industries, particularly automotive and aerospace.
The 8D process covers all key aspects of problem management:

- Problem description and reporting
- Stakeholder and SME management
- Containment of the problem
- Establish the facts
- Root cause analysis
- Problem correction
- Problem prevention
- Reporting and recognition
When an 8D is completed and recorded, the result is a report showing how and why a solution was reached. Some organizations require detailed Corrective Action reports from suppliers when an issue is found.
8D (Eight Disciplines) workflow
Discipline 0 (D0): Summary
Name the 8D investigation for easy identification. Then define a short, factual problem statement:
- Describe what is affected
- Describe the symptoms
- Identify potential consequences and impact
Be clear and factual; avoid opinions and non-facts.
Discipline 1 (D1): Form the team
Start with the responsible person and expand as the investigation evolves. The team should be cross-functional and include process owners and key stakeholders:
- Subject matter experts (SMEs)
- Process owners
- Customer and supplier representatives
Discipline 2 (D2): Describe the problem
Record all relevant information, clearly and objectively. Consider including:
- Customer identity
- All known facts
- Who, what, when, where
- Is / is-not lists
Discipline 3 (D3): Interim containment actions
Define immediate actions to prevent the situation from worsening. Containment is short-term and may be costly. Sometimes none is necessary. Examples:
- Notifications and communications
- Concessions and permits
- Extra product checks
Discipline 4 (D4): Root cause analysis
Perform failure analysis and investigations to determine root cause(s). Keep records of all analysis performed. Choose tools that fit the problem:
- Fishbone (Ishikawa) diagram
- 5-Whys
- Root cause statement
Discipline 5 (D5): Permanent corrective actions
Identify and compare potential corrective actions. Techniques like Six Hats or random word can help ideation. Provide rationale for each option. Assess suitability and risk (FMEA):
- List possible solutions
- Select the best candidates
- Use FMEA to assess risk and pitfalls
Create an implementation plan with owners and due dates.
Discipline 6 (D6): Implement and validate
Deploy changes and monitor effectiveness. Capture data that demonstrates corrective actions are working and reference it here.
Discipline 7 (D7): Prevent recurrence
Define actions to stop the same problem recurring. Consider:
- Updating procedures and policy
- Updating standards
- Improving KPIs
Apply changes to similar products or processes where relevant.
Discipline 8 (D8): Closure and team recognition
Close the investigation and share success:
- Summarize the investigation
- Document lessons learned
- Publicize success and recognize contributors
Things to consider
- Consider using professional 8D software
- Make 8D your primary method of corrective action management and reporting
- 8D works for product problems, process issues and broader improvement opportunities