8D (EIGHT DISCIPLINES) PROBLEM SOLVING PROCESS

The 8D Problem Solving Process is used to identify, correct and eliminate the recurrence of
quality problems.
8D is a problem-solving methodology for product and process improvement. It is structured
into eight disciplines, emphasising team synergy. The team as whole is better and smarter
than the quality sum of the individuals. Each discipline is supported by a checklist of
assessment questions, such as what is wrong with what, what, when, where, how much.

8D (Eight Disciplines) Problem Solving

Process

1. Use Team Approach

Establish a small group of people with the
knowledge, time, authority and skill to solve the
problem and implement corrective actions. The
group must select a team leader.

2. Describe the Problem

Describe the problem in measurable terms.
Specify the internal or external customer
problem by describing it in specific terms.

3. Implement and Verify Short-Term

Corrective Actions
Define and implement those intermediate
actions that will protect the customer from the
problem until permanent corrective action is
implemented. Verify with data the effectiveness
of these actions.

4. Define end Verify Root Causes

Identify all potential causes which could explain
why the problem occurred. Test each potential
cause against the problem description and
data. Identify alternative corrective actions to
eliminate root cause.

5. Verify Corrective Actions

Confirm that the selected corrective actions will
resolve the problem for the customer and will
not cause undesirable side effects. Define
other actions, if necessary, based on potential
severity of problem.

6. Implement Permanent Corrective Actions

Define and implement the permanent
corrective actions needed. Choose on-going
controls to insure the root cause is eliminated.
Once in production, monitor the long-term
effects and implement additional controls as
necessary.

7. Prevent Recurrence
Modify specifications, update training, review
work flow, improve practices and procedures to
prevent recurrence of this and all similar
problems.

8. Congratulate Your Team

Recognize the collective efforts of your team.
Publicise your achievement. Share your
knowledge and learning.

Page 1 of 4
Page 2 of 4
 8D Report Ref No: Sample
General Information
Title: Customers description Organisation: Supplier
Status: Open/Closed Opened Date: Date informed
Type: Quality Closed Date: By Customer
Customer Ref: Customer/Reject Number Last Update: Last actioned By: Author

D0 – Symptom

Symptom (1 of 1 ): Effect experienced by Customer

Description/Qualification: Describe the effect in detail in terms the customer can understand

D0 – Emergency Response Action (ERA)

ERA (1 of 1 ):
Is ERA required YES/NO Implemented Removed

Description: Description of ERA or reason why team did not instigate –

Yes/No? Yes/No?
example all product quarantined, 100% inspect prior to ship?

D1 – Team
Name Role Telephone E-mail
Name only required Champion Contact number E-mail address
Team Leader
Team Members

D2 - Problem Description
Statement: A simple statement derived from ‘What is Wrong with What’
Description: What: What is it – Description, Type, Part Number, Serial Number etc?
When: What date was it first seen/reported?
Where: Where it was first reported? Customer premises, On receipt, In-process, during test etc.
How Big How many – 4 out of 20, all products, One isolated incident?

D3 – Interim Containment Action (ICA)

ICA (1 of 1 ): What has been done to ensure Verified Implemented Validated Removed
continuance of shipped parts to Date ICA put in Date ICA Date ICA
the customer? place validated removed
Description: Verification
A description on how parts are Description: How has the containment action been verified?
being controlled and the Does the defined inspection method work, is it
method whereby this is verified effective and could it be maintained long term
and how good stock is whilst a permanent fix has been put in place. Has
identified. customer approved the containment action?

E.g. – ‘x’ number of parts Validation

visually inspected against Description: How has the containment action been validated?
criteria of reported defect, by
Have we identified what could go wrong with
trained inspection personnel
prior to release for shipment. the plan and have preventive and
These parts identified by label contingency actions been considered?
on outer box stating – 100%
inspected and verified OK
stock.
D4 – Root Cause ( 1 of ):
Description
 D5/D6 – Permanent Corrective Actions (PCA)
a. Is there a root cause (a single verified reason that
accounts for the problem)? Root Cause PCA (1 of 2 ):
b. Is there more than one potential root cause?
c. What factor(s) changed to create this problem? What Description:
data is available that indicates any problem in the Description of method and actions used to introduce
manufacturing or process design? Permanent Corrective Action(s)
d. Does each item on the potential root-cause list account a. What criteria have been established for choosing a
for all known data? Has each item been verified (used to PCA for the root cause and escape point?
make the effect come and go)? b. What choices have been considered for the PCA's?
e. How did we verify this root cause? c. Have we overlooked better choices?
d. Does this root cause explain all the facts compiled at d. Do we have the right experience on this team to
D2? make this decision?
f. Has the root-cause analysis gone far enough (do we e. What risks are associated with this decision and how
need to know why this root cause happened)? should they be managed?
g. How did you determine assignment of percent f. What are the possibilities that this choice, once
contribution? implemented, will create other troubles?
h. Combined, do the items on the potential root-cause list g. Can our customer live with this resolution?
account for 100 percent of the problem (is the desired h. Will our containment continue to be effective until our
performance level achievable)? choice can be implemented?
i. What resources will be required for PCA
implementation? Do we have these resources?
j. What departments will need to be involved in the
planning and implementation of this decision?

Date Verified: Date verified

% contribution: All one cause?

Verification Description: Date Verified Date Implemented Date Validated

Verification of root cause supported by documented evidence,

data or visual reproduction OK/NOK parts
Verification a. What evidence (proof) do we have that
Description: this will resolve the problem at the root-
cause level?
b. Did our verification methods make
allowances for variations in the frequency (or
patterns) created by the cause?
c. Which variables did we measure during
the verification step? Do these indicators
constitute sound verification?

D4 – Associated Escape Point Description:

a. Does a control system exist to detect the problem?

b. Has the current control system been identified? Does
this control system represent a change from the original
design?
c. Has it been verified that the control system is capable of
detecting the problem?
d. Is the identified control point closest to the root Validation Description of method used to validate
cause/potential root cause? Description: effectiveness of elimination of the root cause
e. Is there a need to improve the control system? of the problem

Date Verified:
Verification Description:
Description of how escape point was verified:
a. What evidence (proof) do we have that this will resolve D7 – Prevent Recurrence Actions (PRA)
the problem at the root-cause level? Root Cause PRA (1 of ):
b. Did our verification methods make allowances for
variations in the frequency (or patterns) created by the Description;
cause?
c. Which variables did we measure during the verification Have all changes been documented (FMEA, control plan,
step? Do these indicators constitute sound verification? process flow, Inspection criteria)?

What actions have been taken to correct similar operations or

processes that may exhibit similar problem areas?

Implemented: Date
D7 – Systemic Prevent Recommendation(s)
Responsible Organisation: Person / Department Date Created:
Recommendation ( 1 of ): FMEA,
Control Plan, Work Instruction etc
Process Flow
Work Instruction etc

D8 – Recognise Team and Individual Contributions

Author: Date:
Recognition: Who:
When:
How:

Authorisation for Closure

Name Signature Mandatory to close Date
Customer
Supplier
Other As specified

Attachments
Description File Name Attached By Date Attached
Documents which provide supporting verification and
Validation. Inspection Reports, FMEA’s Control Plans
SPC charts, Cpk data. Photographic evidence.
Action Plans, Timelines, etc
THIS INFORMATION MAY BE EMBEDDED

Additional Information