Applying the right lean tool for a given problem follows directly from mastery
of the lean principles. This article provides an explanation of the “Five
Whys” problem-solving tool.
Proper uses of the tool:
1) As a structured approach to solve problems as they occur
2) As a framework for a team to work through a more complex problem
Improper uses of the tool:
1) To emphasize the person or blame, turning the Five Whys into the Five Whos.
2) To emphasize documentation at the expense of applying the tool. When problem-solving becomes a tedious, desk-intensive process, it is a punishment that gets used as little as possible.
Description of Five Whys tool, how-to
The Five Whys is a simple process to follow to solve any problem. It starts with writing or having an effective problem statement. Problem statements determine the direction we head next. If we get it wrong, every step that follows will be wrong. Problem statements should describe the current condition, use data where possible, and describe the gap in performance. You should also be open to changing the problem statement as you learn more during your investigation. In writing problem statements, you should avoid describing the solution, postulate as to the expected cause, be vague or ambiguous or combine multiple problems into one.
Some examples of good problem statements include:
Once the problem statement is determined, you can
begin using the Five Whys to determine the root cause. Ask why to the problem
statement and then ask
that again five times. Five is not a magic number; sometimes it might be two,
others nine. You should not try to jump whys, but precede one why at a time.
You can test each answer to your "why" by asking, "If I remove
this, will the previous answer go away?" If the answer is no, you haven’t
answered why correctly and you should explore it further. If you can’t
immediately answer a why, go and observe or collect data until you can see
the current condition clearly enough to answer. Because of this, you may not
a Five Why in one conversation, but may have to observe, collect data and other
activities at each level of why. You have gotten to the end, or the root cause,
when you can describe the cause of the problem in terms of an activity, connection
An example follows with the problem that a key piece of equipment failed.
Why did the equipment fail? Because the circuit board burned out.
Why did the circuit board burn out? Because it overheated.
Why did it overheat? Because it wasn’t getting enough air.
Why was it not getting enough air? Because the filter wasn’t changed.
Why was the filter not changed? Because there was no preventive maintenance schedule to do so.
That is now a root cause that can be solved. By focusing on the question WHY, we are more likely to avoid using the other W question: WHO.
The purpose is to fix the system, not just remove the symptom. If we aren’t clear about the difference between symptoms and problems, we will not find the root cause effectively. Symptoms are the part we see – the part on the surface. Symptoms are how we know we have a problem. Problems themselves are the cause of that symptom. As an example, if I see oil on my garage floor and I clean up the oil, is the problem fixed? No, you just fixed a symptom of the problem, not the problem. The problem is the engine leaks.
Once the root cause is determined, a countermeasure to the problem must be found. Creativity and lean tools are your most powerful allies in this part of the process. Focus on nothing but the root cause in determining the proper countermeasure. All the other work from problem statement to the Five Whys helps to get you to this point.
A vital final step of the process is verifying that the solution worked. This should be done by first seeing that the countermeasure is sustainable and then making sure that the original condition – the symptom – has been eliminated. There are two purposes. The first is to ensure we met our objective: eliminating the adverse condition. The second is where learning occurs. By verifying each countermeasure, we learn what works and what doesn’t, improving our knowledge both of the process we are trying to manage and improve in addition to problem solving process itself.
Variations on the tool
The Five Whys can be built into many other problem solving processes. Many companies create proprietary problem solving processes that are based on having a common way to communicate or save for learning and history. The Five Whys can be utilized as a formal part of a larger process or by the user to determine the root cause, which then gets input into the formal process. Also, tools, such as Six Sigma, can help find the answer to each successive ‘why’ being asked, but does not replace the process of digging down layer by layer.
How tool relates to rules and principles
The Five Whys most obviously and directly relates to the principle of Systematic Problem Solving. Without the intent of the principle behind you, the Five Whys will likely be a shell of a process and not used effectively.
Key behaviors that must accompany the Five Whys include: 1) surfacing problems quickly; 2) using them as opportunities to move closer to the ideal state; and 3) focus on the process, not on blaming the person. The principle of Create a Learning Organization is also greatly enabled through the practice of the Five Whys. The Five Whys can become the primary driver of daily learning about the management and improvement of the process.
By finding the root cause and then verifying the effectiveness of the countermeasure,
deep knowledge of the process can become institutionalized.
About the author:
The Lean Learning Center was established in 2001 to help companies overcome the barriers to successful lean transformation. In conjunction with its corporate partner Achievement Dynamics, a provider of management consulting, the center provides a full complement of lean transformation services. Partners Jamie Flinchbaugh and Andy Carlino have recently authored a book titled The Hitchhiker’s Guide to Lean, published by the SME. For more information visit www.hitchhikersguidetolean.com.