Watch The Video
Watch The Video
Watch The Video
This Template should only be used by someone trained in the techniques presented he
8D, or 8 Disciplines, is an 8 step problem solving methodology for both products and processes. It is best suited to existing problem
defects where the cause is unknown. 8D is not suitable for problem prevention, problems of variation or waste elimination.
Begin by clicking the 'Preliminary Data' hyperlink below. Then proceed sequentially through each Discipline (D0, D1 . . . D8)
The 8 Disciplines
D0 Preliminary Data
D1 Team selection
D2 Problem Definition
D3 Contain problem
D4 Identify Root Cause
D5 Identify Corrective Action
D6 Implement
D7 Prevent Recurrence
D8 Congratulate Team
8D Summary Report
Notes:
1. There are several tabs in this workbook, with at least 1 tab dedicated to each of the eight disciplines.
2. Discipline 1 is D1, Discipline 2 is D2, etc.
3. When more than 1 tab is used for a given discipline, a D4-1, D4-2 . . . format is used.
4. Each tab contains the instructions, templates and decision tools appropriate for that discipline.
esented herein
. D8)
D0 - Preliminary Data
Watch the Video
8D Instructions
Next >>>
Customer:
Customer Address:
Date of Failure:
Time of Failure:
Failure Rate:
Tracking Number:
Product Name:
D1 - Team Selection
Watch the Video
8D Instructions
Next >>>
Dept Name Role Responsibilities
Pro(cess/duct)
Ensure corrective actions do not conflict with required inputs
Supplier
Pro(cess/duct)
Customer Ensure corrective actions do not conflict with required outputs
Other As needed
D2 - Problem Definition
Watch the Video
What is the product ID or reference number? What ID's or reference # are not affected?
WHAT
Where does the problem occur? Where is it not occurring but could?
WHERE
Where was the problem first observed? Where else might it occur?
When was the problem first reported? When was the problem not reported?
WHEN
Can the problem be isolated? Replicated? Is there a trend? Has the problem occurred previously?
OTHER
What is the start of the pro(cess/duct)? What is the end of the pro(cess/duct)?
Based on answers to the questions above, please describe the problem and/or the opportunity
ESCRIPTION
PROBLEM
DESCRI
PROB
Note: the description of the problem should use a noun - verb format and not have any opinions, judgments,
assumptions, presumed causes, solutions, blame or compound problems contained in it.
Next >>>
D3 - Contain Problem
Watch the Video
Use the Checklist and Risk Assessment below to manage the Containment Action
These actions are temporary until permanent corrective action is taken
8D Instructions
Containment Checklist
Problem Definition Yes
Team selection No
Risk Assessment No
Containment recommendation No
Communication Plan No
Containment agreement No
Risk Assessment
Severity Occurrence Detection Risk
Failure Containment Action Taken
1-10 1-10 1-10 Number
10 10 10 1000
Rating → 1 5
Severity Nuisance or distraction Loss of primary function
Occurrence Unlikely Moderate frequency
Detection Detectible Difficult to detect
Communication Plan
Delivery
Audience Objective Feedback Measure Key Message
Method
Person to reach What are we seeking? Telecon, email, meeting, IM, How will we know the message What are we
Awareness, support, decision, Text, Videocon, etc. was received? doing & why?
advocate, advice, assistance
Next >>>
5 5 5 125
5 10
primary function Loss of life or loss of significant $
erate frequency Almost certain
fficult to detect Cannot detect
Key Message Assigned Due date Failure
What does it What does the What support Who will Completion
mean to the person need can the person deliver the date
person? to do expect from us? message
differently?
Next >>>
D4 - 1 Identify Root Cause
Watch the Video
Select one or more tools below to help identify Root Cause
8D Instructions
)
se use l Te
c au ty o f n a
nt roo
t vi se o
x ity eme d je cti s (ea u ncti
le ir n
sub
s F tu
omp equ to fi of v ene
r e s X
orsS
ol
C eR ilit
y el uiti qu
i ac t
Root Cause Tool To Tim Ab Lev Int Re #F
IS / IS NOT M H H L M M M
Fault Tree M M H L L H M
Process Map L L L L H L L
5 Why's L L M M H L L
Multi Vari H M H L L L M
FMEA M H M M M M H
Pareto L L L L H L H
Fish Bone L M L M H M M
Inter-relationship Diagram M L H L M M H
Current Reality Tree M M M L L M L
Scatter Plots L L H L M L L
Concentration Chart L L L L H L L
Design of Experiments H H H L L M L
Tree Diagram L L L L H M H
Brainstorming L L L H H M L
Regression Analysis L L H L H L L
Artificial Neural Networks H M H L L L H
Component Search L M H L H L H
L = Low M = Medium H = High
am
a l Te
on
ncti ied
Stud
s
a c tor
#F
D4 - 2 IS / IS NOT
Watch the Video
Root Cause List Complete the 'Problem Definition' on tab D2 Before Proceeding
8D Instructions
0 0
What is (describe) the defect? What is not the defect? 0
0 0
Where does the problem occur? Where is it not occurring but could? 0
WHERE
0 0
Where was the problem first observed? Where else might it occur? 0
0 0
When was the problem first reported? When was the problem not reported? 0
WHEN
0 0
When was the problem last reported? When might it reappear? 0
0 0
Why is this a problem? Why is this not a problem? 0
0 0
WHY
What is the start of the pro(cess/duct)? What is the end of the pro(cess/duct)?
0 0
Lot #: 0 Application: 0 Failure Rate: 0.00%
0
MISC
Based on answers to the questions above, please describe the problem and/or the opportunity
ESCRIPTION
PROBLEM
0
PROB
DESCRI
Highlight the differences between IS and IS NOT and identify possible causes
START HERE
Differences Changes Date & Time Possible Cause
Customer A & B are long time Customer C added in the last 1 month ago New customer onboarding
customers, Customer C is not month process
Possible Cause 2
Possible Cause 3
Possible Cause 4
Possible Cause 5
Possible Cause 6
Possible Cause 7
Possible Cause 8
Possible Cause 9
Possible Cause 10
Possible Cause 11
Possible Cause 12
Select "+" when both "IS" and "IS NOT" are explained by the Possible Cause.
s
es
pr r
oc
6
ng e
di m
se
e
us
us
us
us
us
ar sto
u
Ca
Ca
Ca
Ca
Ca
Ca
bo cu
le
le
le
le
le
le
on ew
ib
ib
ib
ib
ib
ib
ss
ss
ss
ss
ss
ss
N
Po
Po
Po
Po
Po
Po
+
∑+ 1 0 0 0 0 0
∑- 0 0 0 0 0 0
Total 1 0 0 0 0 0
RESULTS
Based on IS / IS NOT, the most likely causes(s) are:
Order ∑+ Cause
1 1 New customer onboarding process
2 0 Possible Cause 2
3 0 Possible Cause 3
4 0 Possible Cause 4
5 0 Possible Cause 5
6 0 Possible Cause 6
7 0 Possible Cause 7
8 0 Possible Cause 8
9 0 Possible Cause 9
10 0 Possible Cause 10
11 0 Possible Cause 11
12 0 Possible Cause 12
Possible Cause. Select "-" when "IS" or "IS NOT" is explained by the Possible Cause.
10
11
12
7
9
e
se
us
us
us
us
us
u
Ca
Ca
Ca
Ca
Ca
Ca
le
le
le
le
le
le
ib
ib
sib
ib
ib
ib
ss
ss
ss
ss
ss
s
Po
Po
Po
Po
Po
Po
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
D4 - 3 Fault Tree
Watch the Video
Root Cause List Using the basic fault tree symbols on the left, construct a fault tree here
8D Instructions
Example:
Light Doesn't
Turn On
Event
Switch
Inoperable No Bulb
Logic "OR" Gate Power Faulty
Contacts
Burned Bulb
Basic Event Failure Not Repairman
Equipment Not Burned
Visible Failure Available Out
Connector
Start
Start Receive
Match Order
Process Order price to quote
Step 1
Process
Step 2 Yes Enter order in
No Price system
Match?
Return to
customer
Decision
Possible Root Cause of order delay: cannot find quote to match price
Connector
cess map
Instructions:
No
Why did this occur? How is this confirmed?
Therefore I forgot to fill it up Yes
No
Why did this occur? How is this confirmed?
The fuel gage is not working Fuel gage testing
Therefore Yes
No
Why did this occur? How is this confirmed?
Therefore I forgot to have it repaired Yes Maintenance records
No
Why did this occur? How is this confirmed? See
I didn't put it on the repair list when it broke Yes
Root Cause
Instructions:
STEP 1 : Define the problem. What is the product, process or service that has failed.
STEP 3 : Answer: Does this reason need to ne confirmed? If No proceed to next 'Why?'
If Yes, then record how confirmation was made.
ed?
STEP 4 : Repeat Step 2 & 3 until Root Cause is identified.
STEP 5 : Verify Root Cause by starting at the probable Root Cause and connecting
ed? it to the previous cause using 'Therefore'
ed? STEP 7 : If there is a logical connection between each pair of statements back
ds to the problem then you have likely found the Root Cause
ed? See D6
failed.
xt 'Why?'
ting
D4 - 6 Multi Vari
Watch the Video
Root Cause List
8D Instructions
STEP 1 : Define the problem. What is the product, process or service that has failed
STEP 2: Using a Families of Variation (FOV) tree, identify the potential root causes to be included in the study - see below
STEP 6: Multiply the results in 3, 4 and 5 to determine the total number of units to be studied (Cell: L42)
STEP 7: Develop the data collection plan (Row 47). This should be automatically created for you.
STEP 8: Collect data (Column H beginning at cell H48) & select alpha risk (Cell: I178)
Failure (Unit)
Within Between
Unit Units Over Time
Example: Widget to Widget Line to Line Shift to Shift
1. WU1 to WU1 1. BU1 to BU1 1. OT1 to OT1
2. WU2 to WU2 2. BU2 to BU2 2. OT2 to OT2
3. WU3 to WU3 3. BU3 to BU3 3. OT3 to OT3
4. WU4 to WU4 4. BU4 to BU4 4. OT4 to OT4
5. WU5 to WU5 5. BU5 to BU5 5. OT5 to OT5
Sub-Total: 5 Sub-Total: 5 Sub-Total: 5 125
Obs [n]: Time [a]: Time [a]: Time [a]: Time [a]: Time [a]:
1 15.2038 9.9244 6.3712 12.138 5.8427
Units [b]: 1
12,218.41
12,943.50
16180.72
RESULTS
Based on the FMEA, the most likely causes(s) are:
Order RPN Cause
1 128 Quote filing not properly organized
2 64 Customer references wrong quote
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
9 0 0
10 0 0
11 0 0
12 0 0
ffects Analysis
Actions
Resp. Actions Taken
Recommended O
D
S C
E
E C
What are the T
V U
actions for E R
Who is responsible What are the E R
reducing the C P
for the completed actions R R
T N
occurrence of the I E
recommended taken with the I
cause, or
action? recalculated RPN? T N
improving Y C
O Rating
detection? N
E
Hazardous without warning Very High and almost inevitable Cannot detect or detection with very low probability
Loss of primary function High repeated failures Remote or low chance of detection
Loss of secondary function Moderate failures Low detection probability
Minor defect Occasional failures Moderate detection probability
No effect Failures unlikely Almost certain detection
D4 - 8 Pareto
Watch the Video
Complete the Pareto and select the high count causes as potential root causes
Instructions:
aterials
STEP 1 : Define the problem. What is the product, process or service that has
STEP 2 : Starting with 'Materials' or any other label, ask: is there anything ab
might contribute to the problem. Record it next to one of the arrow
STEP 3 : Repeat asking "is there anything about materials that might contribu
Record each result next to an arrow.
Problem
STEP 4 : Repeat Step 2 & 3 for each successive category.
STEP 5 : Identify the candidates that are the most likely Root Cause
STEP 6 : If further "screening" is necessary, assess the likely Root Causes usin
and "Implement" matrix, selecting items marked 1, then 2 . . . 4 as p
achines
rvice that has failed.
use
Step 7: For each issue, record the arrows "in" and "out"
Possible Root Causes:
1. Want to avoid embarrassment Step 8: Issues with the highest "out" are possible
2. Don't think it will help Root Causes
D4 - 11 Current Reality Tree
Watch the Video
Using the basic Current Reality Tree symbols on the left, construct a Current Reality Tree here
UDE
AND"
Competent people People want to be Standard Practices
don't need Standard viewed as are incorrect
Practices competent
No system in place to
create and update
standard practices
Standard Practices
are not valued by the
company
Tree here
Instructions:
s
he
D4 - 12 Scatter Plot
Watch the Video
Follow the directions on the right to complete the Scatter Plot
Root Cause List
8D Instructions
Data Points
X Y 70
38.26 2.081381
91.23 4.706895
60
106.29 3.649935
268.31 9.622546 R
50
470.63 25.962171
216.82 7.124237
307.75 7.199636 40
213.78 9.542106
Y
352.17 16.402771 30
128.26 10.687631
125.44 9.089371 20
185.70 11.430855
119.93 5.731392 10
158.64 7.569877
186.30 9.673238 0
292.41 17.305745 0 100 200 300 400 500 600 700 800
338.46 19.560302
405.83 27.898421
X
227.94 15.441851
285.26 19.425977
192.43 12.254396
248.85 30.174186
512.06 37.54775
545.07 48.281938
186.95 20.595593
208.56 17.888325
182.72 19.081187
459.35 40.326252
414.24 30.300325
276.57 31.892381
254.89 22.175021
368.50 22.243916
203.20 11.651808
363.92 29.876299
46.60 3.377931
506.60 45.387671
225.27 14.434076
340.61 28.64869
193.25 14.264056
170.16 9.112769
161.13 10.187908
131.80 11.596628
279.55 20.186701
161.96 11.07718
512.89 29.678582
807.69 59.404809
177.67 12.047774
539.72 45.28834
Instructions:
Step 1. Enter data in columns A & B (Cells: A9 & B9)
Step 2. Position the red lines parallel to the existing 'best fit' line
so that all data points are between the red lines
Step 3. Identify the upper and lower spec for 'Y'
Step 4. Calculate the vertical distance between the red lines: R
Step 5. Conclude: 'X' is a root cause when:
(Upper Spec - Lower Spec) * 0.2 > = R
Upper Spec: 60
Lower Spec: 20
R: 26
STEP 1 : Define the problem. What is the product, process or service that has failed.
STEP 2 : Draw a diagram of the item under consideration. A sketch, engineering drawing or process map works well.
D4 - 14 Design of Experiments
23 Factorial Design with up to 5 Replicates
Watch the Video
Root Cause List
8D Instructions
Page 51
40.00 40.00 40.00
30.00 30.00 30.00
20.00 20.00 20.00
10.00 10.00 10.00
0.00 0.00
D4-14
0.00
ave - ave + ave - ave + ave - ave +
REGRESSION MODEL
UNCODED CODED TO FIND AN UNCODED FACTOR SETTING REQUIRED TO ACHIEVE A GIVEN RESPONSE:
High Low High ? Low 1. Select factor settings for 2 of the 3 factors and enter them in as "coded values" (Cells B56, B57
A: 180 160 1 0.55 -1 2. From the Excel Ribbon above select Data > What-If Analysis > Goal Seek
3. In the dialogue Box, Set Cell D57 . . .
4. To value = whatever Response value you desire
Page 52
D4-14
5. By changing cell B56 or B57 or B58 (whichever one was left blank from 1. above)
6. Select OK then OK
7. Enter the uncoded equivalent of 'High' in cell B63 and the 'Low' in cell C63. See answer in 8. b
8. So ... A = 1 coded and A = 175,5 uncoded
Page 53
D4-14
Instructions:
Page 54
D4-14
Page 55
D4-14
Page 56
D4 - 14 Tree Diagram
Watch the Video
Problem
Cause Cause
Instructions:
Step 3: Determine if all items from Step 2 are sufficient and necessary.
Ask: "are all items at this level necessary for the one on the level above?"
Step 4: Using each item from Step 2, repeat Step 2 & 3. In other words, treat
each response from Step 2 as the new problem and repeat Step 2 & 3
Step 1: Warm up . . . ask each particpant to describe their ideal job. Examples: professional golfer, photographer, travel con
Step 2: Then, describe the problem you are trying to solve to the group
Step 5: When all suggestions are received, seek clarification so everyone else understands
Step 6: Arrange all ideas into "logical" or "like" groups - use an Affinity Diagram
GB Docs
2,500,000
11,528 56,291,839
240 1,172,747 2,000,000
37 256,936
89 671,045 1,500,000
Docs
104 725,230
262 1,540,736 1,000,000
212 863,173
500,000
209 792,843
344 1,315,431 -
125 1,229,587 - 100 200 300 400 500 600
123 1,019,737
GB
181 1,262,217
117 421,386
155 835,398 Regression Equation: Docs = 204486,843 + 4031,443 * GB
182 1,427,470 R2 = 0,8164 R2 adj = 0,8124
286 1,483,527
331 1,835,340 Confidence
396 1,672,662 95% e.g. 95%
223 1,114,091 Prediction Interval
279 1,608,812 Known Predicted Lower
188 887,604 GB 500 Docs 2,220,208.4 1,688,920.0
243 1,256,176
183 996,818 Docs 3,000,000 GB 693.4
204 1,014,372
178 1,384,045
449 2,294,320
405 1,988,651
270 1,617,172
249 1,310,009
360 1,759,851
198 616,722
355 1,465,105
46 203,325
220 908,955
333 1,155,898
189 735,376
166 514,246
157 941,943
129 465,914
273 1,099,136
158 666,556
501 2,307,524
174 626,189
378 1,762,608
547 2,109,892
41 182,682
74 262,055
177 1,248,915
538 2,152,805
494 2,281,354
Analysis
Instructions:
Step 1. Enter variable names in cells A1 (X) and B1(Y)
Step 2. Enter data in columns A & B (1000 data points max)
Step 3. Select the Confidence Level of the analysis (Cell D22)
Step 4. Enter a known X (cell D25) and observe the predicted Y
(cell F25) and the prediction interval (cells H25 & I25) or . . .
Step 5. Enter a known Y (cell D27) and observe the predicted X
0 500 600 (cell F27)
Notes:
1. The Regression Equation, R2 and R2adj are located below the plot
443 * GB
Prediction Interval
Upper
2,751,496.8
D5 Identify Corrective Action
Describe and summarize the Root Cause and Corrective Actiion
8D Instructions Watch the Video
Next >>>
Next >>>
D6 Implement and Verify
Implement the Corrective Action and Validate Effectiveness
8D Instructions Watch the Video
STEP 1 STEP 2
The 3 Corrective Actions: Verifying Root Cause can
1. CA 1 1. Design of Experiements
2. Hypothesis Testing
2. CA 2 3. Components Swapping
4. Regression Analysis
3. CA 3 5. On/Off Switching
6. Process Capability
STEP 3 7. Tukey Quick Test (see S
Tukey Quick Test: 8. Control Charts
1: Select a sample of 8 from the process with the defect 9. Sampling
2: Implement the first Corrective Action from the above list
3: Select a second sample of 8 from the process
4: Rank the sample readings from low to high
5: Identify each as either 'good' or 'bad'
6: Verify Root Cause then return to 1. above for next Corrective Action
STEP 4
Sample Set # Reading Good/Bad
1 1 Bad Beginning at Sample 1, # 1 and moving down the list,
1 2 Bad the number of consecutive Bad units = 3
1 3 Bad
1 4 Good
1 5 Good Beginning at Sample 2, # 16 and moving up the list,
1 6 Good the number of consecutive Good units = 7
1 7 Good
1 8 Good
2 9 Bad
2 10 Good Total 'End Count' 10
2 11 Good
2 12 Good
2 13 Good Based on the Total 'End Count of 10, there is 99% confidence
2 14 Good that the likely Root Cause is an actual Root Cause
2 15 Good
2 16 Good
Next >>>
g Root Cause can be accomplished using a variety of tools, such as, but not limited to:
n of Experiements
thesis Testing
onents Swapping
ssion Analysis
ff Switching
ss Capability
y Quick Test (see Step 3)
ol Charts
ling
in Sample 1
in Sample 2
nfidence
Next >>>
D7 Prevent Recurren
Ensure Corrective Actions Prevent Re
Watch the Video
8D Instructions
Low Control
Low Effort Verbal * Written * Visual * SPC * Mistake Pr
Process: Incomplete 31
Too complex 30
Difficult to understand 8, 30
Poor Design/sequence 30
Unfamiliar with process 1, 5, 8, 9, 12
No transparency 1, 3, 5, 9
Unaware of process 2, 10
Inputs not understood 5, 7, 9
Outputs not understood 5, 7, 9
Poor Spec Limits 25
Not formalized 11
Inconsistent use 5
Lack of process training 1, 2, 3, 5, 6, 7, 9
Poor/no documentation 5, 6, 7, 8, 9, 12
Variation 5, 23, 24
Poor decision rules 12
High Control
Visual * SPC * Mistake Proofing * New Design High Effort
Next >>>
Next >>>
8D Instructions
Describe Activities
Next >>>
8D Summary Report
D0 WHO IS EFFECTED BY THE PROBLEM? Tracking Number: 0
Customer: 0 1st Person to report problem: 0
Address: 0 Product Manager: 0
Date of Failure: 0 Value Stream Manager: 0
Time of Failure: 0 Description of use: 0
Part No.: 0 8D Report Number:
Product Name: 0
D1 TEAM MEMBERS D2 PROBLEM DESCRIPTION
Champion: 0 0
Team Leader: 0
Process Owner: 0
Supplier: 0
Customer: 0
SME: 0
QA: 0
Other: 0
PICTURE OR SKETCH OF FAILURE
D4 ROOT CAUSE
LRC 1
LRC 2
LRC 3
D5 CORRECTIVE ACTION
CA 1
CA 2
CA 3
2.
Yes
3.
Yes
D8 TEAM RECOGNITION
0
APPROVAL Name Signature Date