
- Search forums
- National and International Business System Standards
- ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards

5D and 8D as an option, can it be both or one of them in the system?
- Thread starter YAZIDM
- Start date Jul 29, 2010
Hi, Our system just practice 5D as for our Corrective Action record. Since most of the customer asking for 8D , should i remove 5D from the procedure and replace it with 8D or is it possible to have both? My boss is asking can it be both in the procedure since he want the 5D to be used internally.
YAZIDM said: Hi, Our system just practice 5D as for our Corrective Action record. Since most of the customer asking for 8D , should i remove 5D from the procedure and replace it with 8D or is it possible to have both? My boss is asking can it be both in the procedure since he want the 5D to be used internally. Click to expand... What are the elements of your 5D procedure? If you use both, but your customers ask for the 8D one, how will you ensure that you use the 8D one for them? Is this only iif/when they insist?
Hi Jane / qusys, Actually this is the first time I saw 5D, fyi, I’m the freshie new guy who taking care the QMS. Our 5D consist; D1: Define the Problem D2: Define & Verify the Root Cause(s) D3: Identify & Verify Proposed Permanent Corrective Action D4: Implement Permanent Corrective Action D5: Action to Prevent Re-occurrence While for 8D ; D1: Identify Team Member/Roles & Responsibilities D2. Define the Problem D3. Implement & Verify Interim Containment Actions(s) D4. Define & Verify Root Cause(s) D5. Identify & Verify Proposed Permanent Corrective Action(s) D6. Implement Permanent Corrective Action(s) D7. Action(s) to Prevent Re-Occurrence D8. Communicate Results & Recognize Team As we all well know, nowadays ALL customers demanding 8D. But my supr. asking me whether is it possible to have them both in the system, reason is 5D for internal use and 8D for external. To me, i will agree with qusys....I’m not sure about this. The procedure only mentions one report that is 5D. My boss wants them both which is ‘as an option’. My concern is will I face any problem in future especially during audits? I believe it’s explainable as what my boss said, but in term of requirement or possibility or necessary maybe logic? Beside "add-in" 8D as an option, should I amend anything on the procedure? Please review attachment. Were gonna arrange Internal audit this coming sept and ISO audit is soon after that. thanks in advance
Attachments
- QA,PROC-13-01,MAL EDI 1 Corrective Action_.pdf 54.1 KB Views: 1,205
- QA,PROC-13-03,MAL EDI 1 Customer Complain.pdf 134.9 KB Views: 733
There's nothing wrong with using multiple models, but as some have pointed out, people need to know which to use when. To me the 5D is simply the 8D without use of a team. Many problems do not require a team.
YAZIDM said: ................. should i remove 5D from the procedure and replace it with 8D or is it possible to have both?.................... Click to expand... You had literally paint yourself into a corner or tie your own hands. Your procedures shouldn't be that restrictive. It should just mention the use of appropriate problem solving techniques - bearing in mind that the different techniques or methods are useful into different situations.
Duke Okes said: There's nothing wrong with using multiple models, but as some have pointed out, people need to know which to use when. To me the 5D is simply the 8D without use of a team. Many problems do not require a team. Click to expand... Excellent advice, with which I agree. I don't see it as a divide between 'external' and 'internal' use - why should or would it be. Some issues require a team approach, with others it would be overkill. Key point is to be clear about who decides which approach is to be used when - eg, a manager deciding (NOT someone deciding on the basis of which is 'easiest'.
Duke Okes said: There's nothing wrong with using multiple models, but as some have pointed out, people need to know which to use when. To me the 5D is simply the 8D without use of a team. Many problems do not require a team. Click to expand... Duke, I guess i'll agree with that, not all problem req a team. it does make sense
Does anyone know where I can download a thorough 5D CAR form?
Similar threads
- Started by SLandry92
- Mar 29, 2022
- Started by Jolande
- Apr 1, 2021
- Started by PG Ltd
- Oct 2, 2020

- Started by adir88
- Apr 8, 2020
- Started by perdrix
- Jul 20, 2017
- Started by RSEGRIGGY
- Nov 11, 2016
- Started by Boingo-boingo
- Jun 27, 2013
- Started by v9991
- Aug 23, 2011
- Replies: 30
- Jul 30, 2011
- Started by Howard Lee
- Mar 30, 2009
- Replies: 17

- Started by Sidney Vianna
- Jun 12, 2007
- Replies: 21

- Started by Marc
- Dec 31, 2006
- Started by soton
- Aug 30, 2006
- Apr 5, 2006
- Replies: 10
- Started by tarheel
- Sep 3, 2002
- Replies: 228
- Started by choices
- May 7, 2002
- Replies: 11
- Started by zatro
- Feb 18, 2023
- Started by beatrizlaranjeiro
- Mar 9, 2022
- Started by Hari Varma
- Feb 8, 2022
- Started by Gerald Leo
- Aug 27, 2021
- Started by floats
- Jun 4, 2021

- Started by dinaroxentool
- Feb 12, 2021
- Started by sherin marshiyana
- Nov 12, 2020

- Started by gunnyshore
- Aug 18, 2020
- Started by mpfizer
- Mar 3, 2020
- Started by Michael_M
- Jun 19, 2019
- Started by david316
- Jun 5, 2019
- Jun 4, 2019
- Started by Gaby
- Apr 25, 2019
- Started by SACHIN GUPTA
- Apr 11, 2019

- Started by Ed Panek
- Mar 15, 2019
- Started by pyo
- Mar 7, 2019
- Started by Barbara49
- Dec 10, 2018
- Started by nurtu1
- Apr 25, 2018
- Started by rewalvh
- Jan 18, 2018

- Started by Ajit Basrur
- Aug 11, 2017
- Started by Mark Meer
- Jul 28, 2017
- Replies: 25
- Started by Omar.
- Jun 16, 2017
- May 4, 2017
- Started by nurhakim
- Dec 28, 2016
- Started by Tyler C
- Sep 28, 2016
- Started by Rambo
- Aug 30, 2016
- Started by SteveK
- May 13, 2015
- Started by kanklam
- Feb 12, 2015
- Started by maxximase
- Dec 30, 2014
- Replies: 14
- Started by kazengg
- Sep 9, 2014
- Started by milagre
- Aug 7, 2014
- Started by Willy Wonka
- Aug 6, 2014
- Started by warrock
- Jul 1, 2014
- Started by leetimothyj
- May 7, 2014
- This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register. By continuing to use this site, you are consenting to the use of cookies. Accept Learn more…
- Choosing the Right Corrective Action Form

To choose the right corrective action form you need to understand the D(s) involved with corrective action. The D stands for Discipline. There are 3 main corrective action types and these are 5D, 8D, and 9D. There are 9 different Ds that support each type. These are D1, D2, D3, D4, D5, D6, D7, D8 and D9.
This article explains the differences between the Dx steps and how to select a corrective action method that fits a given situation.
D1, D2, D3, D4, D5, D6, D7, D8 and D9 are the individual steps within a corrective action process.
5D, 8D, and 9D are the full corrective action methods. They consist of the Dx (where x is 5, 8 and 9) corrective action steps and include the previous steps. 8D consist of D1, D2, D3, D4, D5, D6, D7 and D8 steps. 5D consist of the D1, D2, D3, D4 and D5 steps. 9D consist of the D1, D2, D3, D4, D5, D6, D7, D8 and D9 steps.
If you create a 5D corrective action form, you need to make sure you include the D1, D2, D3, D4 and D5 steps. The same is true for a 8D and 9D corrective action form.

8D Manager Software with 5D, 8D, 9D, and RMA report generator. Corrective action software for every company needs.
The Dx Steps of the Corrective Action Form
D1 stands for forming a team.
D2 stands for identifying a problem.
D3 describes the containment actions you take to prevent the problem from getting to a customer. Or if it is at the customer, how you get it away from the customer.
D4 stands for identifying the root cause of the problem.
D5 describes the corrective actions you take to permanently fix or remove the problem.
D6 describes the preventive actions you take to further prevent the problem from occurring again.
D7 identifies the verification steps you take to make sure D3 through D7 (and D9) are complete.
D8 stands for congratulating the team.
D9 stands for risk and / or safety actions taken as the result of the corrective action.
For more details on the Dx steps, see this article .

Differences between Corrective Actions
Short corrective action form usually require a 5D investigation. Which means you form a team, you identify a problem, you take containment actions, you identify the root cause and you issue corrective action.
More important corrective actions require an 8D investigation. This includes the 5D investigation plus you conduct preventive actions, you verify all the previous actions and you congratulate the team.
Some companies require an 9D investigation which includes the 8D and add Risk / Safety Actions.
Selecting a Corrective Action Form Method.
Many companies struggle with determining the corrective action method that best suits them. In fact, for many small companies, or companies new to corrective action, they may have not documented their method or given it much thought. Because of this, they may use different approaches depending on the individual handling the complaint. This causes an unwanted amount of variation when it comes to conducting corrective actions. Further, this causes confusion at the customer location, confusion with auditors and confusion with management.
I recommend a multi method approach based on the situation. Below is a flowchart that you can use for selecting a corrective action form depending on the situation. Please download and edit to your needs.
You can use this flowchart whether the problem / complaint / defect / issue started internally or externally.

Harmful to the Individual
The first question, you should answer... could this problem cause harm to an individual? If this defect can hurt someone then conduct a full 9D investigation. You need to make sure these defects don’t escape your company. Your corrective action must assure you permanently fix the problem. In addition you need to make sure the root cause of the defect doesn’t spread to other parts. If people were harmed or could be harmed, you need to address this too. The 9D investigation assures these actions occur.
Does the Problem Affect the QMS?
The new requirements of ISO 9001:2015 requires Risk Analysis. Plus, ISO based most of the other QMS standards on the ISO 9001:2015 standard. Auditors now audit for Risk Management and how it affects your QMS. If the problem or defect affects the QMS, you need to conduct Risk Analysis on that issue. This means you should conduct a 9D corrective action form investigation and make sure the identified risks feed into your corrective action software ( 8D Manager! ) and your QMS Management review.
Normal vs Non Normal Issue
Company’s usually set up inspection stages to catch possible normal issues. Inspections include process, final, receiving, SPC, shipping and many others. If the issue got past the inspection and caused any unsuspected costs to the company, then issue an 8D Analysis.
What kind of unsuspected costs?
- Machine Damage
- Production Delay
- Management Meetings
If the issue was found at your customer receiving inspection, how do you classify this? It is up to your company and your customer. They may require an 8D Analysis. Or they may require a simpler 5D Analysis. For example if the customer finds a label issue, then 5D may be sufficient. If they find defects and the customer cannot use the parts then 8D may be needed.
If your customer found the issue during their processing with your parts, then classify that as unsuspected costs and you should issue an 8D Analysis.
Normal Inspection Problem
If the defect was found during normal internal inspection then this would only require a 5D analysis. The inspection is there to catch that issue. The 5D will find the root cause and implement the actions to further prevent it. If you find the issue to be constantly reoccurring then you may want to upgrade the corrective action to an 8D analysis
Document Verification Actions
For 8D corrective action process you need to verify the actions were completed. You usually prove this with just a name and date of the verification. You want to make sure the verification takes place by someone different than the person conducting the action.
However, when addressing external (found by a customer) issues with the 8D process and with any 9D corrective action, you should describe how you conducted the verification. Describe exactly what the person did to make sure the action was executed.
8D Manager Software
This article discussed the differences between D8 steps and the 8D steps. It also provided a flowchart for selecting an appropriate corrective action method.
Companies face the difficulties of issuing the exact corrective action approach and keeping everything for corrective action together. 8D Manager lets you simplify all of this. You can quickly issue 5D, 8D, 9D corrective actions and create professional reports. 8D Manager assures you don’t skip a step. 8D Manager lets the corrective action be as simple or as complex as you need. 8D Manager stores them all in one location and you can review and edit any of them quickly and easily.

5 Why Problem Solving
Learn 5 why problem solving and how this connects to 8D problem solving. See how to use 5Y analysis for customer corrective actions.

Dealing with Customer Complaints
Best methods when dealing with customer complaints. We recommend reaction to business complaints, consumers complaints, and product complaints.

Corrective and Preventive Action Management Systems for ISO 9001.
We break down the differences between corrective and preventive action management systems and preventive maintenance for ISO 9001

Corrective Action Forms Implementation and Measurement Tips
Tips on issuing corrective action forms, measuring corrective actions preventive action and creating an effective corrective action system.

Root Cause Corrective Action System documentation
Describes the important items to include in your Root Cause Corrective Action System. Corrective Action is critical to your ISO 9001 certification.

Learn 8D Eight Disciplines!
Learn the 8D Eight Disciplines, see it in action, and apply global 8D software to your business.

Corrective Action Software in Action
See how to use corrective action software to solve customer complaints. Here is a detailed example of 8D Manager in Action.

Root cause analysis
Root cause analysis (RCA) is a process designed for use in investigating and categorizing the root ...

Preventive Corrective Action With 6 Steps
An effective Preventive Corrective Action may require many integral processes that function together for best results. These processes may include

Discusses 8D Problem Solving Details and 8D Reports.
Review this for detail information on 8D problem solving. This article discusses your customer requirements for 8D reports.

How to Handle Customer Complaints
Learn to how to handle customer complaints. Your intitial response sets the tone and builds a relationship with your customer.

Sound Containment Theory is Important to Keeping Customers.
Execution of containment theory prevents escaping defects and improves customer satisfaction. We describe the best approaches to containing defects.

8D Manager, Corrective Action Software for Instant Download.
Download 8D Manager Today. Only $89. Prevent corrective action mistakes that may harm your relationship with your customer. Use 8D Manager for your corrective action software. Satisfaction guaranteed.
8D Manager FAQ

Concerns for Business Owners
Dealing with concerns for business owners and a golden book that helps address them.

Block Out Negative Comments
Tips to block out negative comments. What to do for your business, before, during and after you receive a negative review.
Would you prefer to share this page with others by linking to it?
- Click on the HTML link code below.
- Copy and paste it, adding a note of your own, into your blog, a Web page, forums, a blog comment, your Facebook account, or anywhere that someone would find this page valuable.
Stay in Touch
- Contact & Follow
- The QA Blog
- StreamLining
- Data Analysis
- Brainstorming
- Benchmarking
- Control Plan
- Cost of Quality
- On Time Delivery
- Corrective Action
- Calibration
- Document Control
- Traceability
- Material Control
- Preventive Action
- Risk Management
- Knowledge Mgmt
- Staff Suggestions
- Training Software
- Team Building
- Employee Evaluation
- Communication
- Characteristics
- Setting Goals
- Project Management
- Virtual Teams
Other Business
- Public Speaking
- Copywriting
- Building Security
- Information Security
Website Info
- Terms & Conditions
- Anti Spam Policy
- Privacy Policy
What is 5D and 8D?
What is meant by 8d, is 8d a six sigma, what is 5d automotive, what does 8d stand for in problem solving, basic difference between 3d 4d 5d 8d music || headphones reqd....
What is 5d problem-solving?
What are the 5 whys in problem-solving, what is 5d technology, what is 5d company, what are the 8 steps of an 8d.
- D1 – Put Together A Team.
- D2 – Define the Problem.
- D3 – Implement a Temporary Fix.
- D4 – Identify Root Causes and Chose a Solution.
- D5 – Confirm The Solution Resolves The Problem.
- D6 – Fully Implement the Solution.
- D7 – Prevent Recurrence.
Why is 8D important?
Which six sigma is best.
- Six Sigma Black Belt. Black belts are experts and agents of change. They provide training in addition to leading projects.
- Six Sigma Master Black Belt. This is the highest level of Six Sigma achievement.
Is 7 sigma possible?
What is 8d reality, what does 8d feel like, what is 8d and 9d, what is 5d structure, what are the benefits of 5d.
- Accurate Cost Estimation & Forecasting. ...
- Detailed Quantity Take-Offs. ...
- Real-time Changes to Quantity Take-offs as per Design Modifications. ...
- Faster Decision Making Process. ...
- Improved Collaboration Among Stakeholders. ...
- Assistance in Swift Material Procurement.
What is 5D leadership?
What is 7d dimension, what is a 5d image, is virtual reality 5d, what is the 5 whys techniques, is 5 whys lean or six sigma, what are 5 whys in six sigma.

Eight Disciplines of Problem Solving (8D)
– Eight Disciplines of Problem Solving –
⇓ Introduction to 8D
⇓ What is 8D
⇓ Why Apply 8D
⇓ When to Apply 8D
⇓ How to Apply 8D

Introduction to Eight Disciplines of Problem Solving (8D)
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 fix and implement a long-term solution to prevent recurring problems. When it’s clear that your product is defective or isn’t satisfying your customers, an 8D is an excellent first step to improving Quality and Reliability.
Ford Motor Company developed this problem solving methodology, then known as Team Oriented Problem Solving (TOPS), in the 1980s. The early usage of 8D proved so effective that it was adopted by Ford as the primary method of documenting problem solving efforts, and the company continues to use 8D today.
8D has become very popular among manufacturers because it is effective and reasonably easy to teach. Below you’ll find the benefits of an 8D, when it is appropriate to perform and how it is performed.
What is Eight Disciplines of Problem Solving (8D)
The 8D 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 in order to avoid not only the problem at hand but also other issues that may stem from a systemic failure.
8D 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.

Why Apply Eight Disciplines of Problem Solving (8D)
The 8D methodology is so popular in part because it offers your engineering team a consistent, easy-to-learn and thorough approach to solving whatever problems might arise at various stages in your production process. When properly applied, you can expect the following benefits:
- Improved team oriented problem solving skills rather than reliance on the individual
- Increased familiarity with a structure for problem solving
- Creation and expansion of a database of past failures and lessons learned to prevent problems in the future
- Better understanding of how to use basic statistical tools required for problem solving
- Improved effectiveness and efficiency at problem solving
- A practical understanding of Root Cause Analysis (RCA)
- Problem solving effort may be adopted into the processes and methods of the organization
- Improved skills for implementing corrective action
- Better ability to identify necessary systemic changes and subsequent inputs for change
- More candid and open communication in problem solving discussion, increasing effectiveness
- An improvement in management’s understanding of problems and problem resolution
8D was created to represent the best practices in problem solving. When performed correctly, this methodology not only improves the Quality and Reliability of your products but also prepares your engineering team for future problems.
When to Apply Eight Disciplines of Problem Solving (8D)
The 8D problem solving process is typically required when:
- Safety or Regulatory issues has been discovered
- Customer complaints are received
- Warranty Concerns have indicated greater-than-expected failure rates
- Internal rejects, waste, scrap, poor performance or test failures are present at unacceptable levels

How to Apply Eight Disciplines of Problem Solving (8D)
The 8D process alternates inductive and deductive problem solving tools to relentlessly move forward toward a solution. The Quality-One approach uses a core team of three individuals for inductive activities with data driven tools and then a larger Subject Matter Expert (SME) group for the deductive activities through brainstorming, data-gathering and experimentation.
D0: Prepare and Plan for the 8D
Proper planning will always translate to a better start. Thus, before 8D analysis begins, it is always a good idea to ask an expert first for their impressions. After receiving feedback, the following criterion should be applied prior to forming a team:
Collect information on the symptoms
Use a Symptoms Checklist to ask the correct questions
Identify the need for an Emergency Response Action (ERA), which protects the customer from further exposure to the undesired symptoms
D1: Form a Team
A Cross Functional Team (CFT) is made up of members from many disciplines. Quality-One takes this principle one step further by having two levels of CFT:
- The Core Team Structure should involve three people on the respective subjects: product, process and data
- Additional Subject Matter Experts are brought in at various times to assist with brainstorming, data collection and analysis
Teams require proper preparation. Setting the ground rules is paramount. Implementation of disciplines like checklists, forms and techniques will ensure steady progress. 8D must always have two key members: a Leader and a Champion / Sponsor:
- The Leader is the person who knows the 8D process and can lead the team through it (although not always the most knowledgeable about the problem being studied)
- The Champion or Sponsor is the one person who can affect change by agreeing with the findings and can provide final approval on such changes
D2: Describe the Problem
The 8D method’s initial focus is to properly describe the problem utilizing the known data and placing it into specific categories for future comparisons. The “Is” data supports the facts whereas the “Is Not” data does not. As the “Is Not” data is collected, many possible reasons for failure are able to be eliminated. This approach utilizes the following tools:
- Problem Statement
- Affinity Diagram (Deductive tool)
- Fishbone/Ishikawa Diagram (Deductive tool)
- Problem Description
D3: Interim Containment Action
In the interim, before the permanent corrective action has been determined, an action to protect the customer can be taken. The Interim Containment Action (ICA) is temporary and is typically removed after the Permanent Correct Action (PCA) is taken.
- Verification of effectiveness of the ICA is always recommended to prevent any additional customer dissatisfaction calls
D4: Root Cause Analysis (RCA) and Escape Point
The root cause must be identified to take permanent action to eliminate it. The root cause definition requires that it can be turned on or off, at will. Activities in D4 include:
- Comparative Analysis listing differences and changes between “Is” and “Is Not”
- Development of Root Cause Theories based on remaining items
- Verification of the Root Cause through data collection
- Review Process Flow Diagram for location of the root cause
- Determine Escape Point, which is the closest point in the process where the root cause could have been found but was not
D5: Permanent Corrective Action (PCA)
The PCA is directed toward the root cause and removes / changes the conditions of the product or process that was responsible for the problem. Activities in D5 include:
- Establish the Acceptance Criteria which include Mandatory Requirements and Wants
- Perform a Risk Assessment / Failure Mode and Effects Analysis (FMEA) on the PCA choices
- Based on risk assessment, make a balanced choice for PCA
- Select control-point improvement for the Escape Point
- Verification of Effectiveness for both the PCA and the Escape Point are required
D6: Implement and Validate the Permanent Corrective Action
To successfully implement a permanent change, proper planning is essential. A project plan should encompass: communication, steps to complete, measurement of success and lessons learned. Activities in D6 include:
- Develop Project Plan for Implementation
- Communicate the plan to all stakeholders
- Validation of improvements using measurement
D7: Prevent Recurrence
D7 affords the opportunity to preserve and share the knowledge, preventing problems on similar products, processes, locations or families. Updating documents and procedures / work instructions are expected at this step to improve future use. Activities in D7 include:
- Review Similar Products and Processes for problem prevention
- Develop / Update Procedures and Work Instructions for Systems Prevention
- Capture Standard Work / Practice and reuse
- Assure FMEA updates have been completed
- Assure Control Plans have been updated
D8: Closure and Team Celebration
Teams require feedback to allow for satisfactory closure. Recognizing both team and individual efforts and allowing the team to see the previous and new state solidifies the value of the 8D process. Activities in D8 include:
- Archive the 8D Documents for future reference
- Document Lessons Learned on how to make problem solving better
- Before and After Comparison of issue
- Celebrate Successful Completion

8D and Root Cause Analysis (RCA)
The 8D process has Root Cause Analysis (RCA) imbedded within it. All problem solving techniques include RCA within their structure. The steps and techniques within 8D which correspond to Root Cause Analysis are as follows:
- Problem Symptom is quantified and converted to “Object and Defect”
- Problem Symptom is converted to Problem Statement using Repeated Whys
- Possible and Potential Causes are collected using deductive tools (i.e. Fishbone or Affinity Diagram)
- Problem Statement is converted into Problem Description using Is / Is Not
- Problem Description reduces the number of items on the deductive tool (from step 3)
- Comparative Analysis between the Is and Is Not items (note changes and time)
- Root Cause theories are developed from remaining possible causes on deductive tool and coupled with changes from Is / Is Not
- Compare theories with current data and develop experiments for Root Cause Verification
- Test and confirm the Root Causes

Example: Multiple Why Technique
The Multiple / Repeated Why (Similar to 5 Why) is an inductive tool, which means facts are required to proceed to a more detailed level. The steps required to determine problem statement are:
- Problem Symptom is defined as an Object and Defect i.e. “Passenger Injury”
- Why? In every case “SUV’s Roll Over”
- Why? In every case, it was preceded by a “Blown Tire”
- Why? Many explanations may be applied, therefore the team cannot continue with another repeated why past “Blown Tire”
- Therefore, the Problem Statement is “Blown Tire”
- Why? Low (Air) Pressure, Tire Defect (Degradation of an Interface) and High (Ambient) Temperature
- Counter measures assigned to low pressure and tire defect
This example uses only 4 of the 5 Whys to determine the root causes without going further into the systemic reasons that supported the failure. The Repeated Why is one way to depict this failure chain. Fault Tree Analysis (FTA) could also be used.

Learn More About Eight Disciplines of Problem Solving (8D)
Quality-One offers Quality and Reliability Support for Product and Process Development through Consulting, Training and Project Support. Quality-One provides Knowledge, Guidance and Direction in Quality and Reliability activities, tailored to your unique wants, needs and desires. Let us help you Discover the Value of 8D Consulting , 8D Training or 8D Project Support .
Contact Us | Discover the Value!
(248) 280-4800 | [email protected]
Remember Me
- Don't have an account? Register
- Lost your password? Click here
- Already have an account? Log in

- Lean Six Sigma
8D Problem Solving Report
8D stands for 8 Disciplines. It is a methodology that emphasizes “No problem should be repeated but fixed permanently”.
8D Problem Solving Method originally evolved during Second World War. But it became an official methodology in 1974, when it was used by US Government for its Military Operations as ‘Military Standard 1520’. Later it was adapted and popularized by Ford Motors with slight modification in the methodology.
The below are the D’s in 8D approach:

Figure 1: 8D Problem Solving Approach
1D – Team Formation: The first and foremost step not only in 8D but also in any other initiative or project is Team Formation, for any initiative cannot be successful without a right team. The team selected should be committed, competent, co-ordinated, cross-functional with representation from all teams, and should be knowledgeable in 8D methodology.
3D – Interim Containment Actions: Once the problem is described, before heading up to problem solving, the team should fix the effect of the problem, especially on customers. It might involve actions like isolating the items affected, replacing defective parts, before it reaches the customers. This step is mainly to prevent the problem from reaching the market and customers, which might become a competitive disadvantage and reduce customer loyalty.
4D – Root Cause Analysis: After taking containment actions, the team should involve in identifying the root cause(s) for the problem. Methods and tools like 5-Why Analysis , Fishbone diagram , Pareto Analysis , 7 Old QC tools , New QC tools etc. can be used for identifying the root cause. An important point to be noted is: Whatever method is used for RCA , it should be data & fact based.
5D – Formulate Corrective Actions: After successfully arriving at the root cause, the team should formulate corrective actions to be taken to correct the problem. Tools like Brain storming, Affinity diagram etc. can be used.
6D – Validate Corrective Actions: After arriving at the corrective actions, the team should validate whether the solutions are effective. There are several tools like Accelerated life testing , simulation etc. available for this purpose. Then the solution can be implemented in the process. The solution approach from step 4-6 should be repeated until the problem is completely eliminated.
7D – Preventive Action: Identifying and implementing corrective actions is only a temporary solution that keeps the system running or is like ‘Living with the problem by taking counter measures’. The permanent solution is to identify a potential long term solution that will not allow the problem (similar problems) from occurring into the system again. Sometimes corrective action will be a costly, time being measure. Preventive action makes changes in the system, upstream or downstream processes so that the entire system is modified or aligned for ‘Problem Free’ operations.
8D – Team and Individual Recognition: Once the problem is completely solved, the team and the extra-ordinary contributors must be rewarded and recognized appropriately. This will act as a motivation factor for other employees.
These are the steps of 8D methodology. To summarize, 8D is a holistic, systematic and proven methodology for problem solving.
Previous post: Change Management
Next post: Project Portfolio Management

- 10 Things You Should Know About Six Sigma
- Famous Six Sigma People
- Six Sigma Software
Recent Posts
- Control System Expansion
- Energy Audit Management
- Industrial Project Management
- Network Diagram
- Supply Chain and Logistics
- Visual Management
- Utilizing Pareto Charts in Business Analysis
- Privacy Policy
- Terms of Service

- Related Topics
8D Resources
- Case Studies
8D Related Topics
- Brainstorming
- Continuous Improvement
- Fishbone Diagram
- Nine Windows
- Problem Solving
- Shainin System™
- Total Quality Management (TQM)
- Quality Resources /
- Eight Disciplines 8D
What are the Eight Disciplines (8D)?
Quality Glossary Definition: Eight disciplines (8D) model
The eight disciplines (8D) model is a problem solving approach typically employed by quality engineers or other professionals, and is most commonly used by the automotive industry but has also been successfully applied in healthcare, retail, finance, government, and manufacturing. The purpose of the 8D methodology is to identify, correct, and eliminate recurring problems, making it useful in product and process improvement.
The 8D problem solving model establishes a permanent corrective action based on statistical analysis of the problem and focuses on the origin of the problem by determining its root causes. Although it originally comprised eight stages, or disciplines, the eight disciplines system was later augmented by an initial planning stage.
How to Use the 8D Approach
- D0: Plan - Plan for solving the problem and determine the prerequisites.
- D1: Use a team - Select and establish a team of people with product/process knowledge.
- D2: Define and describe the problem - Specify the problem by identifying in quantifiable terms the who, what, where, when, why, how, and how many (5W2H) for the problem.
- D3: Develop interim containment plan; implement and verify interim actions - Define and implement containment actions to isolate the problem from any customer.
- D4: Determine, identify, and verify root causes and escape points - Identify all applicable causes that could explain why the problem occurred. Also identify why the problem was not noticed at the time it occurred. All causes shall be verified or proved, not determined by fuzzy brainstorming. One can use 5 Whys and cause and effect diagrams to map causes against the effect or problem identified.
- D5: Choose and verify permanent corrections (PCs) for problem/nonconformity - Through preproduction programs, quantitatively confirm that the selected correction will resolve the problem for the customer.
- D6: Implement and validate corrective actions - Define and implement the best corrective actions (CA).
- D7: Take preventive measures - Modify the management systems, operation systems, practices, and procedures to prevent recurrence of this and all similar problems.
- D8: Congratulate your team - Recognize the collective efforts of the team. The team needs to be formally thanked by the organization.

List of the Eight Disciplines (8D)
You can also search articles , case studies , and publications for 8D resources.
Introduction To 8D Problem Solving
A Disciplined Approach ( Quality Progress ) Nothing causes anxiety for a team quite like the release of a corrective action preventive action (CAPA) system and accompanying eight disciplines (8D) model. Follow this step-by-step explanation of 8D to reassure your team and get results.
In the Loop ( Quality Progress ) An 8D report is a quality report suppliers use to inform a customer about the status of complaint-related actions. Use this refresher to help track the status of customer complaints.
Featured Advertisers

A systematic approach to nonconformity management and continuous improvements are the key elements of every management system.
8D methodology uses a structured eight step approach to problem solving. The objective is to face the problem and discover the weaknesses in the management systems that permitted the problem to occur in the first place. The output of an 8D process is an 8D report.
The steps in 8D Report are also called “disciplines,” hence the name 8D Report. The steps are:
1D: Team Formation
8D procedures are used for solving exact problems. The approach is based on a team working together to solve a problem. Teamwork must be coordinated and guided. The team should include only competent persons actively involved in the process and who have been assigned a task or responsibility in subsequent steps. Efficient teams are usually not big.
2D: Problem Description
The more clearly the problem is defined the more likely it will be resolved. Problem solving must be based on facts, not opinions. It is important to clarify the issue type, what is wrong, when did it happen, how big the failure extent is and how many times has it happened. The description must be specific and easy to understand. If possible, a supposed cause should be specified. A complete problem description offers the team directions to solve the problem and helps them prioritize tasks. For example, the fact that defective products were already sent to a customer is very important in deciding which containment actions to take and in prioritizing those actions.
Good description is a foundation for later problem solving.
3D: Interim Containment Actions
In this 8D Report step we try to limit the problem extent and protect our customer. Interim containment actions are a “first aid” that protects the customer from the problem until we define the root cause and implement permanent corrective actions.
Containment actions must not introduce any new problems. They have to be carefully documented with precise information (product codes, lot numbers, dates, etc.). This information can then be used to verify effectiveness of performed actions.
4D: Root Cause Analysis
To effectively prevent a problem from occurring again we have to find the root cause of this problem and remove it. In rare situations there could be more than one root cause. To identify the root cause, a systematic and well-documented analysis is needed. Each possible cause should be tested against the problem description and test data. Root cause is often hidden by other causes and can be hard to find. There are many methods that can be used during the analysis. For example, is /is not, 5 Whys, Ishikawa Fishbone and others.
5D: Corrective Actions
The goal of corrective actions is to remove the root cause and prevent the problem from ever happening again. If good corrective actions have been taken we should never have to write another 8D report for this problem. In this step we are concentrated on a specific event or problem that has already arisen.
The corrective actions have to be carefully documented. For each action a responsible person should be identified and the date when the action is planned to be implemented should be selected. When an action has been finished the actual date of implementation and results should be recorded.
For each root cause identified there are usually many corrective actions needed.
6D: Verification of Corrective Actions
The purpose of this 8D Report step is to verify if the actions taken in step 5D have removed the root cause. If we discover that the root cause has not been completely removed, then we have to point out additional measures. It is sometimes necessary to return to root cause analysis in step 4D and repeat the cycle.
Looking for 8D software?
Give 8DReport.com a try!

7D: Preventive Actions
At first glance this step is very similar to step 5D . The difference between these two steps in 8D Report is in the reason why we perform them and in final goal. Actions in step 5D are meant to prevent an existing problem from happening again. In contrast, preventive actions remove causes for a potential problem and prevent it from ever happening. 7D actions are proactive and oriented towards a potential event in the future.
Actions are usually based on results of FMEA analysis or observations of negative trends. Often, concrete problems encourage us to think about other problems that could arise on the same product or about the same problem arising on another product or process.
8D: Team and individual recognition
At the end of an 8D process is the time to recognize the team efforts and special team member contributions. This is also a good point to document lessons learned.
This is a chance for the Champion to express thanks to those who have helped in dealing with this problem.

Published: November 7, 2018 by Ken Feldman

It’s easy to feel overwhelmed by the number of different approaches to problem solving. Some of the most common ones are PDCA , DMAIC , A3, 6S , Agile , 5 Whys , fishbone diagrams , and others. In this article, we’ll look at the 8D process for problem-solving and process improvement. We will present the benefits of 8D along with some best practices and an example of how to use it. This will provide you with some practical applications for use in your own organization.
Overview: What is the 8D process?
The history of 8D is somewhat controversial. While everyone seems to agree that the popularity of the approach can be credited to Ford Motor company, the basis of the process is a little less clear. Senior leadership at Ford saw the need for the Powertrain division to have a methodology where teams could work on recurring problems.
In 1986, work began to develop a manual and training course that would create a new approach to solving engineering design and manufacturing problems. The title of this manual was Team Oriented Problem Solving (TOPS), and it was first published in 1987. But where did the original idea come from?
Many give credit to the U.S. War Production Board, which developed a simple, four-step approach in 1945 for improving job methods. Here’s what they looked like.

Image source: allaboutlean.com .
In reality, the 8D process is officially known as the Eight Disciplines of Problem-Solving. To make things a little more confusing, it’s really nine steps. While originally developed as 8 steps or disciplines, it was subsequently revised to include a step zero, which was to plan and prepare for solving the problem.

Image source: ASQ.org .
Let’s provide a little more detail for each step.
- D0 — Plan: Collect information and data on the problem symptoms. Decide what preparations will be needed to complete the 8D process. Decide whether you will need an Emergency Response Plan to minimize or mitigate the immediate impact of your problem on the customer.
- D1 — Create a team: Put together a cross-functional team consisting of a core group plus a selection of subject matter experts ( SMEs ). Be sure to provide everything the team will need to be successful, including any training needed to properly execute the process.
- D2 — Define and describe the problem: Using relevant data, describe the problem in as detail as possible. Be sure to focus on your problem at this point, not your solution.
- D3 — Contain the problem: Protect your customer by creating containment actions to prevent any further negative impact to them.
- D4 — Identify, describe, and verify root causes: You can use a multitude of tools such as the 5 Whys, fishbone diagrams, brainstorming , and others to identify potential root causes. Use data to validate your root causes.
- D5 — Choose corrective actions: Select the most appropriate actions to resolve and eliminate the root causes of your problem.
- D6 — Implement and validate your corrective actions: Implement your recommended solutions and corrective actions, and continue to monitor to assure yourself that they actually solved your problem.
- D7 — Take preventative measures: Revise your systems to proactively try to prevent these and similar problems from arising in the future.
- D8 — Congratulate your team: Communicate the work of the team and celebrate their efforts.
3 benefits of the 8D process
It goes without saying that removing problems, improving your process, and preventing future problems will provide many benefits to your organization. Here are a few.
1. Simple and effective
The 8D process has been compared to the PDCA model. Like PDCA, 8D is structured, organized, and simple in concept.
2. Drives you to the root cause
By following the sequential steps, this process should lead you to the elimination of your problem and prevent it from arising again.
3. Team approach
The use of a cross-functional team composed of a core group of people working in the problem area as well as subject matter experts contributing on an as needed basis will give you the synergy of combined knowledge and experience that should lead you to a solution.
Why is the 8D process important to understand?
While simple in concept, there are a number of things you should understand that will make this process both effective and efficient.
Elimination of the root cause
If you understand and follow the 8D steps, you will be able to eliminate — or at least mitigate — the negative impact of your problem.
Discipline
The 8D steps are sequential and build on each other. If you have the discipline to stay on track, you will optimize the use of the 8D process.
Problem-solving tools
8D is a process and methodology. You will need to understand the purpose of each step so you can apply the proper problem-solving tools in each step.
An industry example of 8D
A consumer product company located in Mexico City was experiencing an increase in its delivery trucks returning without having made product deliveries to its customers. There did not seem to be an obvious reason or solution, so the president of the company chartered a team to look into the problem. He assigned the company’s Lean Six Sigma Master Black Belt to put together and facilitate a team and chose to use the 8D problem-solving methodology.
He followed the process by first having a planning and preparation meeting to lay out the plan for analyzing the problem. He suggested that some of the delivery supervisors go out into the field to see if they can observe any unusual conditions. They also collected some data and recorded their observations.
A vigorous brainstorming session ensued in which the team listed all the possible reasons the problem was occuring. These potential root causes were validated by the data that was collected and the observations of the supervisors. They discovered the trucks were coming back without delivering all of the product because the customers didn’t have enough money to pay for the product. These were very small customers who had to pay cash on delivery.
The question then became: Why didn’t they have enough money? The next root cause was that the trucks were arriving later in the day, after the customer had already paid for most of their other deliveries and thus had no money left. Why were the trucks arriving so late? Because they got stuck in traffic because they left the yard too late. Why were they leaving so late? Because they were loading the trucks and doing the paperwork in the morning.
Eventually, the team arrived at a solution that had the trucks loaded, prepped, and ready to go when the drivers arrived early in the morning. The result was a dramatic reduction in returned goods and a significant increase in cash flow. The president was confident that the use of the 8D process got them to the right solution quickly and efficiently.
3 best practices when thinking about the 8D process
Like most of the other problem-solving approaches, there are some recommended practices that will help you and your team be successful. Here are a few that will help you stay on track.
1. Pick the best team that you can
Don’t seek volunteers, but hand-select the best team members that are available. It will be their knowledge and expertise that will make the team successful. Likewise for the team facilitator or leader.
2. Take your time
Don’t rush to solutions or what you think is the root cause of your problem. Thoroughly explore your problem so that the solutions that you eventually come up with will resolve the problem and prevent future occurrences. Think creatively.
3. Be specific about what your problem is
Use data to help you understand your problem. Don’t just rely on anecdotal stories or assumptions to decide the root cause of your problem.
Frequently Asked Questions (FAQ) about 8D
1. when should i use the 8d process.
Use this process when you’re trying to solve for safety or regulatory issues, increasing customer complaints, warranty costs (which indicate greater-than-expected failure rates), internal rejects, waste, scrap, and poor performance or test results.
2. Can the 8D process be used in non-manufacturing processes?
Yes. While the 8D process was developed in the manufacturing function of Ford Motor Company, it can just as easily be applied in any type of process or function where you are experiencing problems.
3. What is the difference between the 8D and 5D process?
For a less complex problem, you may decide to use a 5D process. This simplified process will have you form a team, identify your problem, implement containment actions, identify the root cause, and implement corrective actions to eliminate the problem.
So, what is the 8D process?
The 8D process, also known as the Eight Disciplines of Problem Solving, is a method developed at Ford Motor Company used to resolve problems. It is focused on product and process improvement.
The purpose of 8D is to identify, correct, and eliminate recurring problems. It establishes a permanent corrective action based on a problem analysis and determination of the root causes. Although it was originally comprised of eight stages, or “disciplines,” it was later revised to nine to include a planning and preparation stage.
About the Author
Ken Feldman

IMAGES
VIDEO
COMMENTS
Personally I do not know 5D methodology. Most common is 8D , well known in the automotive industry. This is a standards adopted by mostly
Differences between Corrective Actions ... Short corrective action form usually require a 5D investigation. Which means you form a team, you identify a problem
The 5 D's stand for Describe/Draw, Define, Do, Decide, and Declare. This is a problem-solving strategy for which solving begins by making a prediction, and then
The 8D problem solving process is a detailed, team oriented approach to solving critical problems in the production process. The goals of this method are to
Eight Disciplines of Problem Solving (8D). 8D method is a team based problem solving approach/process of 8 critical steps with a.
5D – Formulate Corrective Actions: After successfully arriving at the root cause, the team should formulate corrective actions to be taken to correct the
The 8D problem solving model establishes a permanent corrective action based on statistical analysis of the problem and focuses on the origin of the problem
D5: Verify Permanent Corrections (PCs) for Problem that will resolve the problem for the customer: Using pre-production programs, quantitatively confirm that
The difference between these two steps in 8D Report is in the reason why we perform them and in final goal. Actions in step 5D are meant to prevent an existing
3. What is the difference between the 8D and 5D process? ... For a less complex problem, you may decide to use a 5D process. This simplified