In an earlier blog post, we said that defect prevention depended on understanding the root cause(s). Because this is such an important part of the problem-solving process, let’s explore it further.
“Five Times Why” is probably the best-known method for root cause analysis, but it’s often represented in an overly simplistic manner, as though each question has only one answer. The reality is that completing a Five Times Why is more difficult than it seems, takes longer than it seems, and requires discipline on the part of the person asking why. In this blog, we’ll share with you some specific do’s and don’ts that will accelerate your learning.
How "Five Times Why" Looks in Theory
There’s a problem on the shop floor: a machine breakdown or a defective product. You get immediately notified and rush to the “scene of the crime” before it gets contaminated and the clues disappear. You engage with the person closest to the problem, typically the operator, and start the Five Times Why conversation with direct access to the actual problem. For example, you’re at the workstation where the problem occurred, with the actual defective product in your hands.
You can now initiate the dialogue, starting with you describing the problem and asking the first why. Let’s say it’s a defective product due to a torn gasket. It could go something like this: “Jane, this is the defect I’d like to explore with you, so we can get down to the root cause and find a way to prevent it from happening again. First, here’s the defect: it’s this torn gasket. Can you explain to me why this product has a torn gasket?”
Jane then gives you a single unambiguous cause, for example, “it’s because the gasket slipped when I placed the top cover before final assembly, and the screw went through the gasket material instead of through the hole”. You would then ask “why did the gasket slip when you placed the top cover”, and Jane would again provide you with a single, clear cause such as “the label machine is too close above the jig, and I have only a one-inch clearance to place the top cover on top of the base, so sometimes it makes contact with the gasket and moves it”. Then you ask why the label maker is so close, and so on until you end up with a perfect root cause and a perfect countermeasure that eliminates the problem once and for all, and everybody’s happy.
The practice is often very different
You can probably see why this would not go well right from the start. Even though you were careful not to sound accusatory (for example, you explained that your intent was to find a prevention countermeasure, not a person to blame, and you used “we” to show that it was a team effort), it’s unlikely that Jane heard it that way. She’s the one who assembled the bad product, and she’s primed to expect the worst. The line is stopped, her supervisor is hovering nearby with an unhappy face, and maybe she can hear her colleagues making snide remarks. In other words, this is not a good environment to perform an objective root cause analysis. Jane may well be defensive and choose her words carefully. Her main objective may be to make you go away as soon as possible, so she can get back to work. This would not be conducive to a good root cause analysis.
Culture is Critical
If the culture on the shop floor (or the company) does not encourage teamwork, prevention, and continuous improvement, no amount of tools will be enough. This is an inconvenient reality of lean, but it cannot be ignored. Culture often takes the form of a “chicken and egg” problem that frightens people into inaction and renouncement. If your organization has a written policy on quality or continuous improvement, this will often provide you with the needed cover to get started. Do not resign yourself to thinking that you can’t influence the culture: within your area of responsibility, you can. It needs to be a team effort, however, and your first step before trying the Five Whys method is to explain what you are trying to achieve and explain why it requires active participation by all. Your communication campaign should end with a clear, yes-or-no answer to the question: “are you willing to commit yourself to work this way?” The description of what “this way” means is up to you, but here are a few suggestions:
- Operators are THE experts in how the process works (details are important)
- Expect people to bring their whole person to work (not just a pair of hands)
- Expect every individual to become a problem-solver. Respect for people doesn’t mean being nice and polite (although that’s desirable too), it means believing in them and challenging people to realize their potential
- Never be satisfied with the way things are today
- Attack waste, not people
- The leader’s role is to develop people
- Don’t give answers even when you know them: people learn from the problems they solve, not those that are solved for them.
- Leaders don’t blame, and team members don’t come up with excuses when you focus on factual problem-solving.
- The goal is to create an organization of experienced problem-solvers
- The only source of truth is the genba (the real place, the shop floor)
- Where you spend your time is the true measure of what you value
- Verify assignment completion with your own eyes
How to carry out Root Cause Analysis with the Five Times Why method
- React quickly so that you can find the root causes before they disappear
- Start at the point of occurrence of the problem, with the actual product in hand, and at the actual place where the problem occurred.
- Explain to the person there what you are doing. For example “We want to prevent this defect, but the only way we can do that is by first understanding the true root cause. You and I are going to work together to go step by step, identifying why things happened, and in this way, we’ll dig to find the root cause. I need you as an equal partner in this: you know the process and the conditions better than I do, so I’ll keep asking you why many times. I know it’s uncomfortable because it may feel like I’m putting you on the spot, but it’s absolutely not about blaming anyone. Even if someone made a mistake, we won’t blame them, because all of us make mistakes. But if we understand what happened, we can find ways to prevent a mistake from turning into a problem”.
- At the top of your notebook, write a short description of the problem and circle it. Ask the person “what’s the immediate cause of this problem?”
- Do not let the person jump toward the root cause. We must proceed step by step to understand the whole sequence of cause and effect.
- When a cause is provided, check it. If it doesn’t make sense or you’re not sure you understand, ask for an explanation or ask to be shown. Once you’re satisfied with a cause, you can write it immediately below the circled problem, and circle it.
- Draw an arrow from the cause to the problem to indicate the causal chain.
- Often, there is more than one immediate cause. In that case, write them side by side and below the problem (effect), with an arrow from the cause to the effect. Not only that, but you must also understand how these causes work together:
- If they must all be present for the effect to take place, write AND in between them. This indicates that a single cause is not sufficient to make the problem occur: it is the conjunction of two or more causes that does so.
- If any cause, by itself, can make the problem occur, write OR in between them: each cause creates a parallel chain of cause-and-effect that leads to the problem.
- For each circled cause, ask “why did this happen?” and continue adding causes, going down the page.
- Your notebook will look something like this:
- Continue asking “why?” down each causal chain until you have found the root cause or root causes.
- Note that even though the tool is called “Five Times Why”, you will not always find the root cause at the fifth why. Sometimes, it takes more, sometimes less. So, how will you know when you’ve hit the root cause? As long as the causes become more specific, keep going. When your next cause starts getting more general or harder to address, stop. For instance, when you start answering “why?” with “it’s a management decision”, or “lack of training”, you’ve passed the optimal root cause. Similarly, when the answer is “lack of standard”, that might be a good point to stop, because you now know exactly what the standard needs to include.
- Just because you’ve identified the root cause(s), you’re not done yet! Remember that your goal is to implement countermeasures that will actually prevent the problem from occurring again. If possible, this takes the form of poka yokes (see our previous blog post), but it could also be introducing new standards.
Finally, take one more look at the tree diagram above. How many root causes are there? How many need action?
The answer may surprise you: you only need to find one preventive countermeasure, for Cause 126.96.36.199.1 The reason is that if you can prevent the left branch from ever occurring, the two branches on the right won’t be enough to cause the problem.
It’s very important to involve your “discussion partner” throughout the Five Times Why process. Show them the causal diagram as you add to it, and make sure it still makes sense to your partner. Also, at some point, you may need to continue the discussion with another person. For example, a machine operator may carry you all the way to a broken sensor, but to understand why the sensor broke, you may need to talk with an engineer or maintenance technician.
Five Times Why is one of the most powerful tools you will find in the lean toolbox, but don’t fool yourself into thinking it’s easy: it takes 15 to 30 minutes to complete in the best of cases, and you can’t underestimate the importance of making your discussion partner feel at ease and not on trial. Like anything else, it’s repeated practice that will yield the results you seek.