Introduction To Eight Disciplines Of Problem Solving (8D)
1. Introduction
The Eight Disciplines of Problem Solving (8D) is a problem-solving methodology designed to find the root cause of a problem, devise a short-term solution, and implement a long-term solution to prevent recurring problems. When your product is defective or is not satisfying your customers, an 8D is an excellent first step to improving Quality and Reliability.
The problem-solving process is a detailed, team-oriented approach to solving critical problems in the production process. The goals of this method are to find the root cause of a problem, develop containment actions to protect customers and take corrective action to prevent similar problems in the future.
The strength of the 8D process lies in its structure, discipline, and methodology. 8D uses a composite methodology, utilizing best practices from various existing approaches. It is a problem-solving method that drives systemic change, improving an entire process to avoid not only the problem at hand but also other issues that may stem from a systemic failure.
The evolution of 8D starting early development in Ford, became a popular and useful tool to address major customer complaint and improve quality8D has grown to be one of the most popular problem-solving methodologies used for Manufacturing, Assembly and Services around the globe. Read on to learn about the reasons why the Eight Disciplines of Problem Solving may be a good fit for your company.
2. Learning Objectives
Participants can expect to learn and develop skills to confidently:
- Perform 8D step by step.
- Facilitate an effective 8D.
- Participate in 8D exercises.
- Define root causes and mechanisms of failure.
- Set up a Cross Functional Team (CFT)
- Determine effective Interim Containment Action
- Manage and store 8D content (Lessons Learned) for future use.
- When to select and utilize tools such as:
- 5 Why
- Ishikawa/Fishbone
- Affinity
- Is / Is Not
- Statistical Process Control (SPC)
- Poka Yoke (Error Proofing)
- Link 8D to Failure Mode and Effects Analysis (FMEA)
- Understand links to Control Plan
- Complete the 8D format correctly.
3. Duration
- Time: 9.00 a.m. – 5.00 a.m.
- Days: 2 days
4. Target Group
Engineers, Quality Engineers, Quality Managers, Customer Quality Engineers, Supplier Quality Engineers.
5. Language
English
6. Course Outline
1. 8D Overview
a) Team Problem Solving Principles
b) Process Description (9 Step Process)
c) Team Structure (Cross Functional Team)
2. Review Of Analytical Tools In 8D
a) Brainstorming Rules
b) Ishikawa / Fishbone
c) Affinity Diagram
d) Control Chart
e) Relationship between 8D and FMEA
3. D0 – Awareness Of The Problem/Plan For The 8D
a) Problem Symptom
b) Quantified Symptom
c) Criteria for 8D Continuance
4. D1 – Establish The Team
a) Roles and Responsibilities
b) Team Preparation
c) Agenda and Rules
d) Core Team and SMEs
5. D2 – Define Problem Statement
a) Repeated Why
b) Affinity Diagram
c) Is / Is Not
d) Workshop on Problem Statements and Brainstorming
e) Workshop on Problem Description Development
6. D3 – Interim Containment Action (ICA)
a) Reassuring the customer
b) Containment Plan
c) Verify containment plan effectiveness
d) Emergency Response Action (ERA)
e) Interim Containment Action (IRA).
7. D4 – Identify And Evaluate Root Cause/RCA
a) Process Mapping
b) Human Factors
c) Comparative Analysis
d) Root Cause Theories
e) Root Cause Verification
f) Escape Point
g) Workshop on Root Cause Analysis
8. D5 – Permanent Corrective Action (PCA)
a) Methods for Selecting PCA
b) Correction and Prevention
c) Error Proofing
d) Verification of PCA
9. D6 – Implementation And Validation Of PCA
a) Plan, Do, Study, Act (PDSA) Implementation Plan
b) Change Management
c) Stakeholders
d) Validation Criteria and Sample Size
10. D7 – Prevent Occurrence
a) Risk Management
b) Processes and Procedures
c) Lessons Learned
d) Looking forward in time
e) Link 8D to Failure Mode and Effects Analysis (FMEA)
11. D8 – Closure And Congratulate The Team
a) Lesson learned.
b) Communicating across organization.
c) Congratulate the team.
d) Archive of Documents and learning

