Professional Documents
Culture Documents
Fax:
Email:
Website:
Note how each answer becomes the next question. It is vital that each Why question uses the
previous answer because that creates a clear and irrefutable link between them. Only if questions
and answers are linked is there certainty that an effect was due to the stated cause and thus the
failure path from the event to its root is sure.
Date:
Problem Statement: On your way home from work your car stopped in the middle of the road.
Estimated Total Business-Wide Cost: Taxi fare x 2 = $50, Lost 2 hours pay = $100, Order was late to Customer
because Storemen did not get to work in time to despatch delivery and Customer imposed contract penalty of $25,000,
Lost Customer and all future income from them, estimated to be $2Million in the next 10 years.
Recommended Solution: Carry a credit card to access money when needed.
Latent Issues: Putting all the money into gambling shows lack of personal control and responsibility over money.
Why Questions
1. Why did the car stop?
2. Why did gas run?
3. Why didn't you buy
gas this morning?
4. Why didn't you have
any money?
5. Why did you lose
your money in last
night's poker game?
3W2H Answers
(with what, when, where, how, how much)
Evidence
Solution
6. Why
Phone:
Fax:
Email:
Website:
Figure 1 shows a partial Why Tree for a stalled car (the complete Why Tree would be a monster).
The analysis team uses their collective experience and knowledge of the causes of a stalled car to
logically develop the first level of the Why Tree. Once we identify all the possible first level causes
of the problem we then ask the Why question to find the real first level cause.
A passenger car can stall from electrical system failure, OR from fuel system failure, OR by loss of
engine compression. Each cause is presumed independent of the other and so the connections to the
top failure event are known as OR gates. For each of the three causes we can set off and develop
the next layer of causes. After the second level of causes we can image third level causes for each
one of them. After the third level we build the fourth level, and on and on and on we can rush until
there are many branches, with dozens of boxes in our Why Tree of the causes and effects. If you
, thrown away your
, and almost
certainly you have the wrong root cause.
It is wasteful of time and people to build an entire Why Tree of a failure incident in the first meeting
unless all the evidence is known down to the true root cause. Figure 1 shows the top of a Why Tree
with three branches going towards possible root causes. Two of those branches will prove to be
unnecessary and their development is pointless. At each level the true failure path should be
identified by the evidence and the other possibilities eliminated. There is no value spending time in
a 5-Why failure analysis developing branches that did not cause the top failure event. (If you were
conducting a risk analysis, and not a failure analysis, you would develop all the branches.)
The approach to take with a 5-Why root cause analysis is to start the Why Tree with the top failure
event and identify all first level causes. Use the evidence and logic to prove which one(s) brought
about the incident. Once the first level cause(s) are confirmed you tackle level two causes and
confirm which of them produced the level one effects, and so on. In Figure 2 the first Why
question to ask
believable evidence is that the engine would not restart. The level two question become
A critical component failure in any of the three systems that allow an
internal combustion engine to work electrical, fuel and mechanical will stop the engine.
Failure
Event
Engine stopped
First Level
Causes
Ignition failure
Lost compression
Second Level
Causes
Phone:
Fax:
Email:
Website:
evidence, you are guessing. If you guess, I have no sympathy for what later happens to you and the
analysis. It is just plain wrong to accept any answer to the Why question only with real evidence
or impeccable logic can you know the true cause. If you have sure evidence then you and the
analysis team will know the right answer to the level two question. If you do not have true evidence
you will direct people on the team to go and investigate the event and come to the next meeting
with hard facts so that the true failure path can be identified.
Car stalled at intersection
and would not restart
Failure
Event
Engine stopped
First Level
Causes
Ignition failure
Second Level
Causes
Lost compression
No spark in
cylinder
Spark plugs
not arcing
Distributor
leads
damaged
Points set
wrong
Third Level
Causes
Distributor
not working
Distributor
damaged
Leads
loose
Electrical
supply fault
Fifth Level
Causes
Water in
distributor
Distributor
not sealing
Distributor
cover open
Fourth Level
Causes
Distributor
body
cracked
Water over
distributor
Hosed
engine
down
Drove thru
deep water
puddle
Sixth Level
Causes
Seventh
Level Causes
C:\Users\MikeS\Documents\Lifetime Reliability\LRS Maint Methodology\Understanding How to Use The 5Whys for Root Cause Analysis.docx
Phone:
Fax:
Email:
Website:
Car accident
Failure
Event
Engine stopped
First Level
Causes
Ignition failure
Lost compression
Second Level
Causes
FIRE
Fuel supply
Ignition source
Oxygen supply
First Level
Causes
Phone:
Fax:
Email:
Website:
can only be used alone if there is just one cause for each effect. You can never know if there is only
a single cause for an effect unless you first develop that level of the Why Tree.
Car stalled at intersection
and would not restart
Failure
Event
Engine stopped
First Level
Causes
Ignition failure
Second Level
Causes
Lost compression
No spark in
cylinder
Spark plugs
not arcing
Distributor
leads
damaged
Points set
wrong
Third Level
Causes
Distributor
not working
Distributor
damaged
Leads
loose
Electrical
supply fault
Fifth Level
Causes
Water in
distributor
Distributor
not sealing
Distributor
cover open
Fourth Level
Causes
Distributor
body
cracked
Water over
distributor
Hosed
engine
down
Drove thru
deep water
puddle
Sixth Level
Causes
Seventh
Level Causes
If you only use the Why Table without a Why Tree to direct you will know when there is an AND
situation because the one answer to the Why question in the Table cannot fully explain why an
event occurred. You will become uncomfortable because the logic is clearly incorrect or
incomplete. It is then vital to stop and build the Why Tree so that you can pass through the AND
gate by using a 5-Why Table for each branch.
Going to the True Root of Failure Identifying Latent Causes
In Table 1 you saw a Why Table of a delivery failure caused by a storeman not getting to work on
time. It turned out that he had lost all his money in a card game and had none to buy petrol to get to
work. Because he did not turn up a delivery was missed and the company was penalised $25,000
and lost years of future business. Though there are several possible answers listed in the Why Table
C:\Users\MikeS\Documents\Lifetime Reliability\LRS Maint Methodology\Understanding How to Use The 5Whys for Root Cause Analysis.docx