The 5 Whys is a technique used in
the Analyze phase of the Six Sigma DMAIC methodology. The 5 Whys is a great Six
Sigma tool that doesn’t involve a statistical hypothesis and in many cases can
be completed without a data collection plan.
Asking “Why?” may be a favorite
technique of your three year old child in driving you crazy, but it could teach
you a valuable Six Sigma quality lesson. The 5 Whys is a technique used in the analyse phase of the Six Sigma DMAIC methodology. It’s a great Six Sigma tool that doesn’t involve data segmentation, hypothesis test, regression or other advanced statistical tools, and in many cases can be completed without
a data collection plan.
By repeatedly asking the question
“Why” (five is a good rule of thumb), you can peel away the layers of symptoms
which can lead to the root cause of a problem. Very often the ostensible reason
for a problem will lead you to another question. Although this technique is
called “5 Whys,” you may find that you will need to ask the question fewer or
more times than five before you find the issue related to a problem.
Benefits Of The 5 Whys
Help identify the root cause of a problem.
Determine the relationship between
different root causes of a problem.
One of the simplest tools; easy to
complete without statistical analysis.
When Is 5 Whys Most Useful?
1. When problems involve human factors or interactions.
2. In day-to-day business life; can be used within or without a Six Sigma
project.
How To Complete The 5 Whys
1. Write down the specific problem.
Writing the issue helps you formalize the problem and describe it completely.
It also helps a team focus on the same problem.
2. Ask Why the problem happens and
write the answer down below the problem.
3. If the answer you just provided
doesn’t identify the root cause of the problem that you wrote down in step 1,
ask Why again and write that answer down.
4. Loop
back to step 3 until the team is in agreement that the problem’s root cause is
identified. Again, this may take fewer or more times than five Whys.
5 Whys Examples
Problem Statement: Customers are
unhappy because they are being shipped products that don’t meet their
specifications.
1. Why are customers being shipped
bad products? - Because manufacturing built the products to a
specification that is different from what the customer and the sales person
agreed to.
2. Why did manufacturing build the
products to a different specification than that of sales? - Because the sales person expedites
work on the shop floor by calling the head of manufacturing directly to begin
work. An error happened when the specifications were being communicated or
written down.
3. Why does the sales person call
the head of manufacturing directly to start work instead of following the
procedure established in the company? – Because the “start work” form
requires the sales director’s approval before work can begin and slows the
manufacturing process (or stops it when the director is out of the office).
4. Why does the form contain an
approval for the sales director? – Because the sales director needs to be
continually updated on sales for discussions with the CEO.
In this case only four Whys were
required to find out that a non-value added signature authority is helping to
cause a process breakdown.
Problem Statement: You are on your
way home from work and your car stops in the middle of the road.
1. Why did your car stop? – Because
it ran out of gas.
2. Why did it run out of gas? – Because
I didn’t buy any gas on my way to work.
3. Why didn’t you buy any gas this
morning? – Because I didn’t have any money.
4. Why didn’t you have any money? – Because
I lost it all last night in a poker game.
5. Why did you lose your money in
last night’s poker game? – Because I’m not very good at “bluffing” when I
don’t have a good hand.
As you can see, in both examples
the final Why leads the team to a statement (root cause) that the team can take
action upon. It is much quicker to come up with a system that keeps the sales
director updated on recent sales or teach a person to “bluff” a hand than it is
to try to directly solve the stated problems above without further
investigation.
No comments:
Post a Comment