A Guide To The 5 Whys For Root Cause Analysis

Unplanned downtime is a serious problem for manufacturers. Each downtime hour costs the average consumer goods manufacturer upwards of $36,000. In the rush to get a production line back online, temporary fixes are often the first line of defense.

But those quick fixes rarely solve problems for good, and recurrences are likely. Each repeat outage increases costs, decreases productivity, and intensifies frontline worker frustration.

When an outage happens, smart manufacturers don't just treat the symptoms and move on. They dig deeper to uncover root causes, then develop and implement solutions to fix them for good.

The 5 (or Five) Whys is a simple, effective method that helps teams investigate a problem until they determine its underlying cause.

What Are the 5 Whys of Root Cause Analysis?

A 5 Whys analysis simply means asking "Why" questions five times in a row to peel away the issue's layers until you reach the root cause. 

It was developed by the Toyota Production System in the 1950s to improve quality and efficiency in manufacturing processes by identifying and addressing the underlying causes of problems rather than just treating symptoms.

Thinking beyond surface-level reasons enables teams to trace a problem back to its origins. By uncovering the root cause, your team can develop and implement a solution that prevents the problem from recurring.

A 5 Whys Example

To illustrate how the 5 Whys works, imagine a machine on your factory floor suddenly stops working for the second time this week. The last time, the team noticed it had blown a fuse and replaced it, but it broke again.

They decide to dig deeper by asking 5 Whys:

1. Why did the machine stop? It overloaded and blew a fuse.
2. Why did it overload? The bearing was not sufficiently lubricated.
3. Why was it not lubricated? The lubrication pump was not pumping sufficiently.
4. Why was the pump not pumping sufficiently? The pump shaft was worn out.
5. Why was the pump shaft worn out? There was no filter installed, and metal shavings contaminated the oil.

By using the 5 Whys, the team discovered the root cause and solved it by cleaning and lubricating the system, installing a filter, and updating the operations manual to require biweekly filter checks.

What Is the Purpose of the 5 Whys?

You can't resolve a problem if you don't understand what causes it. By using the 5 Whys, teams can uncover an issue's root cause, then create resilient solutions that prevent recurrences. Consistent use of the 5 Whys can help you build a strong organizational culture. It encourages your teams to move beyond surface-level fixes, prevents recurrence, and promotes sustainable operational improvement.

When Should You Use the 5 Whys?

The 5 Whys works best for simple to medium complexity problems that team members have control over. For more complicated problems, you may need to combine The 5 Whys with more advanced root cause analysis tools, like Pareto charts, fishbone diagrams, or failure mode and effects analysis.

Benefits of the 5 Whys

The advantages of the 5 Whys are more than just about fixing problems. They also include:

• Resiliency: Investigating the chain of events to identify the root cause of disruptions allows teams to formulate solutions that resolve issues and prevent recurrences.
• Simplicity: Selecting a problem-solving method that's easy to understand and use makes it accessible to anyone, regardless of their technical level.
• Collaboration: Bringing people together to discuss a problem in depth promotes teamwork and communication.
• Workplace satisfaction: Inviting people to contribute to solve an issue helps them feel respected and invested in the product.

Limitations of the 5 Whys

The 5 Whys method is powerful, but certain limitations can hinder its usefulness.

• It's not good for complex problems: Because it's a linear method (it assumes a straight line from cause to effect), the 5 Whys may not be useful when multiple factors and interactions cause an issue, like if a machine stopped because of overheating, a power surge, and an inadequately trained operator.
• The team has knowledge gaps: If your participants don't have the right expertise or your data is incomplete or inaccurate, your analysis will fail, and you won't discover the true root cause.
• The culture is toxic: Poor communication or distrust among team members can create misunderstandings or lead them to blame people rather than digging into systemic problems.

How to Apply the 5 Whys to Solve Problems

A 5 Whys analysis is straightforward, but some best practices will help you succeed.

1. Identify one issue to work on. This could be an ongoing problem or something in the recent past that you still need to resolve.
2. Get the right people in the room. Include:
   
   1. A neutral facilitator to guide the discussion.
   2. A frontline worker who has hands-on experience with the process or machine.
   3. A technical expert who understands the problem and can validate proposed solutions.
   4. Someone with the authority to approve the resolution.
   5. A quality or safety expert if there's a compliance or risk angle."
3. Have everyone brainstorm as many potential contributing factors to the problem statement they can think of.  Best practices include:
   
   1. Focus on causes, not symptoms of the problem.
   2. Don't fall back on blaming people. Look for systemic problems (lack of documentation or training, unoptimized equipment, bad processes, factory environment).
4. Evaluate all the responses and choose the best one. The winner becomes Why #2.
5. Repeat the process three more times to come up with Whys #3, 4, and 5. By the fifth Why, you likely have found the root cause.

Five Isn't a Magic Number

Sometimes you can uncover the root cause with just three Whys, and sometimes it takes seven or eight. You must investigate until you identify a cause you can take action on. And for extremely complex issues with multiple causes, the Whys may not be enough. 

What To Do After You Find the Root Cause

After you identify the root cause, test whether it makes sense by running it backwards. Begin with Why #5, then use "therefore" to connect it back to #4, #3, #2, and #1. 

Then start brainstorming solutions, and choose the one you want to implement. Make sure it is feasible, actionable, and fixes the root cause. Assign one or two people to put it into place. 

Finally, schedule a follow-up to evaluate your progress.

What Tools and Frameworks Align With the 5 Whys?

The 5 Whys method is simple and effective in many organizational settings. It can be used along with other root cause analysis tools, including fishbone analysis, Pareto charts, and SWOT (strengths, weaknesses, opportunities, threats) analyses, as well as operational methodologies such as Agile, Kaizen, and Lean.

It's so deeply embedded in the Six Sigma DMAIC (define, measure, analyze, improve, control) methodology that you must demonstrate proficiency with the 5 Whys to achieve Lean Six Sigma certification.

The Bottom Line

The 5 Whys method is a valuable tool for root cause analysis. It can help you understand the actual causes of issues rather than merely address symptoms. It fosters a proactive problem-solving culture focused on long-term improvement and sustainable operational success. 

This makes the 5 Whys an essential tool for any organization committed to continuous improvement and operational excellence. 

Having access to the right data is crucial to a successful 5 Whys evaluation. Learn how Redzone connected workforce software unlocks key information about your frontline operations that informs an effective 5 Whys analysis.