the 5 whys of problem solving

How it works

For Business

Join Mind Tools

Article • 11 min read

Getting to the Root of a Problem Quickly

By the Mind Tools Content Team

5 Whys Root-Cause Analysis

Have you ever had a problem that refused to go away? No matter what you did, sooner or later it would return, perhaps in another form.

Stubborn or recurrent problems are often symptoms of deeper issues. "Quick fixes" may seem convenient, but they often solve only the surface issues and waste resources that could otherwise be used to tackle the real cause.

In this article and in the video, below, we look at the 5 Whys technique (sometimes known as 5Y). This is a simple but powerful tool for cutting quickly through the outward symptoms of a problem to reveal its underlying causes – so that you can deal with it once and for all.

Origins of the 5 Whys Technique

Sakichi Toyoda, the Japanese industrialist, inventor, and founder of Toyota Industries, developed the 5 Whys technique in the 1930s. It became popular in the 1970s, and Toyota still uses it to solve problems today.

Toyota has a "go and see" philosophy. This means that its decision making is based on an in-depth understanding of what's actually happening on the shop floor , rather than on what someone in a boardroom thinks might be happening.

The 5 Whys technique is true to this tradition, and it is most effective when the answers come from people who have hands-on experience of the process or problem in question.

The method is remarkably simple: when a problem occurs, you drill down to its root cause by asking "Why?" five times. Then, when a counter-measure becomes apparent, you follow it through to prevent the issue from recurring.

The 5 Whys uses "counter-measures," rather than "solutions." A counter-measure is an action or set of actions that seeks to prevent the problem from arising again, while a solution may just seek to deal with the symptom. As such, counter-measures are more robust, and will more likely prevent the problem from recurring.

When to Use a 5 Whys Analysis

You can use 5 Whys for troubleshooting, quality improvement, and problem solving, but it is most effective when used to resolve simple or moderately difficult problems.

It may not be suitable if you need to tackle a complex or critical problem. This is because 5 Whys can lead you to pursue a single track, or a limited number of tracks, of inquiry when, in fact, there could be multiple causes. In cases like these, a wider-ranging method such as Cause and Effect Analysis or Failure Mode and Effects Analysis may b e more effective.

This simple 5 Whys technique, however, can often direct you quickly to the root cause of a problem. So, whenever a system or process isn't working properly, give it a try before you embark on a more in-depth approach – and certainly before you attempt to develop a solution.

The tool's simplicity gives it great flexibility, too, and 5 Whys combines well with other methods and techniques, such as Root Cause Analysis . It is often associated with Lean Manufacturing , where it is used to identify and eliminate wasteful practices. It is also used in the analysis phase of the Six Sigma quality improvement methodology.

How to Use the 5 Whys

The model follows a very simple seven-step process: [1]

1. Assemble a Team

Gather together people who are familiar with the specifics of the problem, and with the process that you're trying to fix. Include someone to act as a facilitator , who can keep the team focused on identifying effective counter-measures.

2. Define the Problem

If you can, observe the problem in action. Discuss it with your team and write a brief, clear problem statement that you all agree on. For example, "Team A isn't meeting its response time targets" or "Software release B resulted in too many rollback failures."

Then, write your statement on a whiteboard or sticky note, leaving enough space around it to add your answers to the repeated question, "Why?"

3. Ask the First "Why?"

Ask your team why the problem is occurring. (For example, "Why isn't Team A meeting its response time targets?")

Asking "Why?" sounds simple, but answering it requires serious thought. Search for answers that are grounded in fact: they must be accounts of things that have actually happened, not guesses at what might have happened.

This prevents 5 Whys from becoming just a process of deductive reasoning, which can generate a large number of possible causes and, sometimes, create more confusion as you chase down hypothetical problems.

Your team members may come up with one obvious reason why, or several plausible ones. Record their answers as succinct phrases, rather than as single words or lengthy statements, and write them below (or beside) your problem statement. For example, saying "volume of calls is too high" is better than a vague "overloaded."

4. Ask "Why?" Four More Times

For each of the answers that you generated in Step 3, ask four further "whys" in succession. Each time, frame the question in response to the answer you've just recorded.

What Is a 5 Whys Template?

The diagram, below, shows an example of 5 Whys in action, following a single lane of inquiry.

Figure 1: 5 Whys Example (Single Lane)

The 5 Whys method also allows you to follow multiple lanes of inquiry. An example of this is shown in Figure 2, below.

In our example, asking "Why was the delivery late?" produces a second answer (Reason 2). Asking "Why?" for that answer reveals a single reason (Reason 1), which you can address with a counter-measure.

Similarly, asking "Why did the job take longer than expected?" has a second answer (Reason 2), and asking "Why?" at this point reveals a single reason (Reason 1). Another "Why?" here identifies two possibilities (Reasons 1 and 2) before a possible counter-measure becomes evident.

There is also a second reason for "Why we ran out of printer ink" (Reason 2), and a single answer for the next "Why?" (Reason 1), which can then be addressed with a counter-measure.

Figure 2: 5 Whys Example (Multiple Lanes)

Step 5. Know When to Stop

You'll know that you've revealed the root cause of the problem when asking "why" produces no more useful responses, and you can go no further. An appropriate counter-measure or process change should then become evident. (As we said earlier, if you're not sure that you've uncovered the real root cause, consider using a more in-depth problem-solving technique like Cause and Effect Analysis , Root-Cause Analysis , or FMEA .)

If you identified more than one reason in Step 3, repeat this process for each of the different branches of your analysis until you reach a root cause for each one.

6. Address the Root Cause(s)

Now that you've identified at least one root cause, you need to discuss and agree on the counter-measures that will prevent the problem from recurring.

7. Monitor Your Measures

Keep a close watch on how effectively your counter-measures eliminate or minimize the initial problem. You may need to amend them, or replace them entirely. If this happens, it's a good idea to repeat the 5 Whys process to ensure that you've identified the correct root cause.

Appreciation

A similar question-based approach known as "appreciation" can help you to uncover factors in a situation that you might otherwise miss.

It was originally developed by the military to assist commanders in gaining a comprehensive understanding of any fact, problem or situation. But you can also apply it in the workplace.

Starting with a fact, you first ask the question, "So what?" – in other words, what are the implications of that fact? Why is this fact important?

You then continue asking that question until you've drawn all possible conclusions from it.

The major difference between this and the 5 Whys technique is that appreciation is often used to get the most information out of a simple fact or statement, while 5 Whys is designed to drill down to the root of a problem.

Tips for Using the 5 Whys Technique

• Try to move quickly from one question to the next. That way, you'll have the full picture before you jump to any conclusions.
• The "5" in 5 Whys is really just a " rule of thumb ." In some cases, you may need to ask "Why?" a few more times before you get to the root of the problem. In other cases, you may reach this point before you ask your fifth "Why?" If you do, make sure that you haven't stopped too soon, and that you're not simply accepting "knee-jerk" responses.
• Know when to stop! The important point is to stop asking "Why?" when you stop producing useful responses.

Frequently Asked Questions About 5 Whys

1. what is the 5 whys technique.

The 5 Whys Technique is a problem-solving method involving repeatedly asking "why?" It's a way of quickly getting to the root cause of a situation.

2. Who Invented 5 Whys?

The 5 Whys technique was invented in the 1930s by Sakichi Toyoda, the Japanese industrialist, inventor, and founder of Toyota Industries.

5 Whys Infographic

See our infographic on the 5 Whys and use it to get to the root of your problems!

Bear in mind that appreciation can restrict you to one line of thinking. For instance, once you've answered your first "So what?" question, you might follow a single line of inquiry to its conclusion. To avoid this, repeat the appreciation process several times over to make sure that you've covered all bases.

The 5 Whys strategy is a simple, effective tool for uncovering the root of a problem. You can use it in troubleshooting, problem-solving, and quality-improvement initiatives.

Start with a problem and ask why it is occurring. Make sure that your answer is grounded in fact, and then ask the question again. Continue the process until you reach the root cause of the problem, and you can identify a counter-measure that will prevent it from recurring.

Bear in mind that this questioning process is best suited to simple or moderately difficult problems. Complex problems may benefit from a more detailed approach, although using 5 Whys will still give you useful insights.

[1] Pojasek, R. (2000). 'Asking "Why?" Five Times,' Environmental Quality Management , Volume 10, Issue 1, 79–84. Available here . [Accessed July 1, 2022.]

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

Using root cause analysis.

Find the Root of Your Problems

Root Cause Analysis

Tracing a Problem to Its Origins

Add comment

Comments (0)

Be the first to comment!

Get 20% off your first year of Mind Tools

Our on-demand e-learning resources let you learn at your own pace, fitting seamlessly into your busy workday. Join today and save with our limited time offer!

Sign-up to our newsletter

Subscribing to the Mind Tools newsletter will keep you up-to-date with our latest updates and newest resources.

Subscribe now

Business Skills

Personal Development

Leadership and Management

Most Popular

Newest Releases

Team Management Skills

5 Phrases That Kill Collaboration

Mind Tools Store

About Mind Tools Content

Discover something new today

How do i manage a hybrid team.

Adjusting your management style to a hybrid world

The Life Career Rainbow

Finding a Work-Life Balance That Suits You

How Emotionally Intelligent Are You?

Boosting Your People Skills

Self-Assessment

What's Your Leadership Style?

Learn About the Strengths and Weaknesses of the Way You Like to Lead

Recommended for you

The burden of responsibility.

Ways to Deal With, and Even Enjoy, Taking Responsibility

How to Guides

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Team Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Pain Points

• RCA 101 – 5-Why Analysis (Free Training)
• RCA 201 – Basic Failure Analysis
• RCA 301 – PROACT® RCA Certification
• RCA 401 – RCA Train The Trainer
• Other Trainings
• 5 Whys Root Cause Analysis Template
• RCA Template
• Chronic Failure Calculator

Root Cause Analysis with 5 Whys Technique (With Examples)

By Sebastian Traeger

Updated: March 21, 2024

Reading Time: 7 minutes

What Is the 5 Whys Technique?

Example of the 5 whys technique, how to conduct a 5 whys analysis in 5 steps, when to use a 5 whys analysis, using 5 whys template, tips for mastering the 5 whys technique, frequently asked questions about 5 whys.

With over two decades in business – spanning strategy consulting, tech startups and executive leadership – I am committed to helping your organization thrive.

At Reliability, we’re on a mission to help enhance strategic decision-making and operational excellence through the power of Root Cause Analysis, and I hope this article will be helpful! 

Our goal is to help you better understand 5 whys techniques by offering insights and practical tips based on years of experience. Whether you’re new to doing RCAs or a seasoned pro, we trust this will be useful in your journey towards working hard and working smart.

The 5 Whys Technique is like peeling an onion – it helps you uncover the underlying reasons behind a problem, layer by layer. By repeatedly asking “why” at least five times, this method digs deep to reveal the root cause of an issue. It’s a simple yet powerful problem-solving approach that aims to get to the heart of the matter rather than just addressing surface-level symptoms.

5 Whys Technique: A method that involves iteratively asking “why” five times to unveil the fundamental cause of a problem.

In essence, the 5 Whys Technique is not just about fixing what’s broken on the surface; it’s about understanding and addressing the deeper issues that lead to problems in the first place.

The 5 Whys Technique is like a detective, uncovering the truth behind recurring problems. Let’s take a look at how this method works in two different scenarios.

Case Study: Manufacturing Defects

Imagine a company that keeps encountering the same manufacturing defects despite various attempts to fix them. By using the 5 Whys Technique, they discovered that the defects were not caused by faulty machinery, as previously assumed, but rather by human error due to unclear operating instructions. This realization led to improved training procedures and clear work guidelines, ultimately eliminating the defects.

Application in Service Industry

Now, consider a service industry struggling with frequent customer complaints and service failures. Through the 5 Whys Technique, it was revealed that these issues stemmed from inadequate staffing levels during peak hours. By addressing this root cause, such as hiring additional staff or adjusting schedules, the service quality can significantly improve, leading to higher customer satisfaction.

These examples illustrate how the 5 Whys Technique can be applied across different sectors to identify and address underlying issues effectively.

Step 1: Identify the Problem

Before diving into a 5 Whys analysis, it’s crucial to clearly identify the problem or issue at hand . This step sets the stage for the entire process and ensures that the focus remains on addressing the right concern. Take the time to gather relevant data, observe patterns, and consult with team members or stakeholders to gain a comprehensive understanding of the problem.

Step 2: Ask ‘Why’ Five Times

Once the problem is clearly defined, it’s time to start peeling back the layers. The process involves asking “why” five times, not necessarily limited to five questions but enough to delve deeper into the underlying causes of the problem . Each “why” serves as a gateway to uncovering additional factors contributing to the issue. This iterative approach helps in identifying not just one cause, but multiple interconnected elements that may be at play.

By consistently probing deeper with each “why,” you can reveal hidden complexities and nuances that may have been overlooked initially. This method allows for a more thorough understanding of the situation, paving the way for effective solutions that address root causes rather than surface-level symptoms.

This structured approach encourages critical thinking and enables teams to move beyond quick fixes towards sustainable improvements.

The 5 Whys Technique is a versatile problem-solving approach that can be applied in various scenarios to uncover root causes and drive continuous improvement. Here are two key situations where the 5 Whys Analysis can be particularly beneficial:

Recurring Issues

• The 5 Whys Technique is especially useful when dealing with recurring issues. Whether it’s a manufacturing defect that keeps resurfacing or a persistent customer complaint in the service industry, this method helps identify the underlying reasons behind these repetitive problems. By repeatedly asking “why,” it becomes possible to trace the issue back to its root cause, allowing for targeted solutions that prevent reoccurrence.

Process Improvement

• Organizations constantly strive to enhance their processes and workflows for increased efficiency and quality. When seeking to improve existing procedures, the 5 Whys Technique serves as a valuable tool. By systematically analyzing the factors contributing to inefficiencies or bottlenecks, teams can gain insights into how processes can be optimized at their core. This method enables organizations to make informed decisions about process improvements based on a deep understanding of the underlying issues.

In both cases, the 5 Whys Analysis offers a structured yet flexible approach to delve into complex problems, making it an indispensable tool for driving meaningful change and progress within organizations.

When it comes to conducting a 5 Whys analysis, utilizing a structured template can greatly facilitate the process and ensure a comprehensive investigation into the root cause identification. Using RCA software such as EasyRCA can benefit the team by streamlining your 5-why process. Here’s how organizations can benefit from using a template:

Benefits of Using a Template

• Streamlined Process: A well-designed 5 Whys template provides a clear framework for conducting the analysis, guiding teams through the iterative questioning process. This streamlines the investigation, making it easier to navigate and ensuring that no crucial aspects are overlooked.
• Thorough Investigation: By following a predefined template, teams are prompted to explore various facets of the problem systematically. This ensures that all relevant factors are considered, leading to a more thorough and insightful investigation into the underlying causes.
• Consistent Approach: Templates offer a standardized approach to conducting 5 Whys analyses within an organization. This consistency promotes uniformity in problem-solving methods across different teams or departments, enhancing overall efficiency and effectiveness.

Customizing the Template

Organizations have the flexibility to customize 5 Whys templates according to their specific needs and industry requirements. This adaptability allows for tailoring the template to address unique challenges and incorporate industry-specific considerations. Customization may include:

• Adding Industry-Specific Prompts: Tailoring the template by incorporating prompts or questions relevant to particular industries or types of issues being analyzed.
• Incorporating Visual Aids: Enhancing the template with visual aids such as flow charts or diagrams can help teams better understand and communicate complex causal relationships.
• Iterative Refinement: Regularly reviewing and refining the template based on feedback and evolving organizational needs ensures that it remains aligned with current processes and challenges.

Customizing the template empowers organizations to harness the full potential of the 5 Whys Technique in addressing diverse problems while aligning with their unique operational contexts.

Encouraging Open Communication

In mastering the 5 Whys Technique as a problem-solving method, creating an environment that fosters open communication is paramount. When team members feel comfortable expressing their perspectives and insights, it leads to a more comprehensive exploration of the underlying causes of a problem. Encouraging open communication allows for diverse viewpoints to be considered, providing a holistic understanding of the issue at hand.

By promoting an atmosphere where individuals are empowered to voice their observations and concerns, the 5 Whys analysis can benefit from a rich tapestry of ideas and experiences. This inclusive approach not only enhances the depth of the analysis but also cultivates a sense of ownership and collective responsibility for addressing root causes within the team or organization.

Continuous Improvement Mindset

A key aspect of mastering the 5 Whys Technique is embracing a continuous improvement mindset. Rather than viewing problems as isolated incidents, this approach encourages teams to see them as opportunities for growth and development. By instilling a culture of continuous improvement, organizations can leverage the insights gained from 5 Whys analyzes to drive positive change across various aspects of their operations.

Fostering a mindset focused on continuous improvement entails actively seeking feedback, evaluating processes, and implementing iterative enhancements based on the findings. It involves an ongoing commitment to learning from past experiences and leveraging that knowledge to proactively address potential issues before they escalate. Embracing this mindset ensures that the 5 Whys Technique becomes ingrained in the organizational ethos, leading to sustained progress and resilience in problem-solving efforts.

As we wrap up our exploration of the 5 Whys Technique, let’s address some common questions that may arise regarding this powerful problem-solving method.

What is the primary goal of the 5 Whys Technique?

The primary goal of the 5 Whys Technique is to uncover the root cause of a problem by iteratively asking “why” at least five times. This approach aims to move beyond surface-level symptoms and address the underlying issues that lead to recurring problems.

Is the 5 Whys Technique limited to specific industries or sectors?

No, the 5 Whys Technique is versatile and can be applied across various industries and sectors. Whether it’s manufacturing, healthcare, service, or technology, this method offers a structured yet flexible approach to identifying root causes and driving continuous improvement.

How does the 5 Whys Technique contribute to continuous improvement?

By delving into the fundamental reasons behind problems, the 5 Whys Technique provides organizations with valuable insights for driving continuous improvement. It not only helps in resolving immediate issues but also fosters a culture of ongoing enhancement and development within an organization.

Can the 5 Whys Technique be used for complex problems with multiple contributing factors?

Yes, while initially designed as a simple and straightforward method, the 5 Whys Technique can certainly be applied to complex problems with multiple interconnected factors. By systematically probing deeper into each layer of causality, this technique enables a comprehensive understanding of intricate issues.

I hope you found this guide to 5 whys technique insightful and actionable! Stay tuned for more thought-provoking articles as we continue to share our knowledge. Success is rooted in a thorough understanding and consistent application, and we hope this article was a step in unlocking the full potential of Root Cause Analysis for your organization.

Reliability runs initiatives such as an online learning center focused on the proprietary PROACT® RCA methodology and EasyRCA.com software. For additional resources, visit Reliability Resources .

• Root Cause Analysis /

Recent Posts

What Is Fault Tree Analysis (FTA)? Definition & Examples

Guide to Failure Mode and Effects Analysis (FMEA)

7 Powerful Root Cause Analysis Tools and Techniques

Root Cause Analysis Software

Our RCA software mobilizes your team to complete standardized RCA’s while giving you the enterprise-wide data you need to increase asset performance and keep your team safe.

Root Cause Analysis Training

[email protected]

Tel: 1 (800) 457-0645

Share article with friends:

• Guide: 5 Whys
• May 9, 2023
• Learn Lean Sigma

5 Whys is a problem-solving technique used to get to the root cause of problems by asking the question of Why multiple times, but often 5 times giving it the name “5 Whys”. This allows people to address the root cause of issues instead of the symptoms of the root causes which is often what is seen as the problem. 

Like a doctor diagnosing an issue such as neck pain, a painkiller will only address the symptoms of the neck pain and not the root cause of the pain. By getting to the root cause you can ensure a long-term fix to the root cause of the neck pain which could be caused by seating positions and not taking painkillers which is a short-term fix.

Table of Contents

What is the 5 whys.

The 5 Whys is a root cause analysis problem-solving technique that aims to identify the root cause of a problem by repeatedly asking the question “Why?” five times or until the core issue is unveiled. Developed within the Toyota Production System , it’s one of fundamental tools in the Lean Six Sigma methodology.

Here’s how it works:

• Begin with a clear and concise problem statement.
• Ask “Why?” the problem occurred. Document the answer.
• If this answer doesn’t identify the root cause, ask “Why?” again and document the subsequent answer.
• Continue this process until you’ve either asked “Why?” five times or the root cause has been identified.

Lets go through an example, let’s say a machine stopped working:

• Why? – The machine’s fuse blew.
• Why? – The machine was overloaded.
• Why? – There wasn’t adequate training on machine capacity.
• Why? – Training materials were outdated.
• Why? – There’s no review process for updating training materials.

In this case, the root cause is the lack of a review process for training materials, and addressing this will prevent similar issues in the future. Only treating the symptom in this situation would have been to change the fuse, for it then to regularly blow and cause additional downtime.

This is a good example where a machine stopping working’s root cause is cause by an issue what would not be obvious is first glace at the symptom of the problem and provides a clear example that root cause analysis is important to ensure that solutions are not jumped to before a through root cause analysis is conducted. 

Why is the 5 Whys Important?

Understanding the 5 Whys is important because identifying symptoms of a problem is not the same as uncovering its root cause. If you only address symptoms this provides only temporary solution to the problem. However, understanding and resolving the root cause can prevent the issue from reoccurring.

The 5 Whys Problem-Solving technique is also useful for:

• Problem Prevention: By identifying the root cause of the problem, businesses can implement long-term solutions, leading to more robust systems and processes and prevent the problem reoccurring.
• Cost-Efficiency: Addressing root causes is often more cost-effective in the long run as it prevents recurrence and the associated costs of repeated problem-solving which usually involves the same people constantly firefighting the same issues such as repeated machine breakdowns.
• Improved Processes: Regular use of the 5 Whys to identify the root causes of problems can highlight weaknesses in processes, leading to continuous improvement and optimization processes.
• Empowerment: The use of 5 Whys by individuals a positive culture that promotes a deeper understanding of systems and processes, empowering teams to take ownership and responsibility in addressing issues.

How to Conduct a 5 Whys Root Cause Analysis?

Step 1: define the problem.

This is an important step as if the problem is not defined effectively it could result in focusing in the wrong problem. A good method for this could be to use the 5W1H Is/Is Not Problem solving technique to gain a common understanding of that the problem is.

When stating the problem you are going to conduct a 5 Whys on it is important to be specific about the issue and avoid ambiguous descriptions. Additionally, where data and information is available this should be collected and used as evidence that points to the actual problem rather than opinions of the problem. 

Step 2: Ask the First “Why?”

Now you have a clear problem definition you should ask the question “Why did that happen?” This should be done to understand the problem without making assumptions and should be done with supporting facts and data that backs up the initial answer to the question.

Step 3: Continue to Ask Why?

Now you should have an answer to the first why. This should form the next step and ask why did that happen. This ensures you dont settle for the inisital surface-level answer or symptoms of the real problem and pushes you to understand the underlying issues.

When you continue to ask why you should:

• Continuously question the previous answer
• Challenge answer that seem like assumptions and lack evidence to support them to avoid going down the wrong route. 

Step 4: Continue the Process

• Keep the questioning focused on the problem
• If you feel the questioning is going off track revert back to what the initial problem definition.
• Ensure each answer provided logically leads to the next “Why?”
• The 5 Whys process then concludes when further questions leads to no further valuable answers are given or the when the root cause of the issues becomes clear.

Step 5 Implement Solutions

Once you have identified the root cause the you need to address it by implementing a solution to prevent the problem reoccuring.

This should be a case of developing an actionable solution that address the root cause of the issue and not preventing the symptoms as addressing the symptom will likely cause the issue to reappear elsewhere.

Make sure you test the solutions to ensure they are effective in addressing the root cause, you should then continue to monitor the process over time to confirm the problem did not reappear in the same place or elsewhere.

If the problem does not re appear congratulations you have solved the problem!

An Example of 5 Whys Analysis

Below is a good example of a 5 Whys analysis done in a situation where there was a production downtime.

To summarize, the 5 Whys process is an effective problem-solving tool that can assist businesses in identifying the root cause of a problem and developing effective solutions. Teams can delve deep into underlying issues and develop targeted solutions that address the root cause of the problem by asking “why” multiple times.

The five steps of the 5 Whys process – defining the problem, asking “why” once, asking “why” more times, developing a solution, implementing the solution, provide a clear framework for problem-solving and can help ensure that the problem is effectively resolved. The 5 Whys process encourages teams to think critically and systematically, resulting in long-term solutions that are effective, targeted, and sustainable.

• Benjamin, S.J., Marathamuthu, M.S. and Murugaiah, U., 2015. The use of 5-WHYs technique to eliminate OEE’s speed loss in a manufacturing firm.   Journal of Quality in Maintenance Engineering ,  21 (4), pp.419-435.

A: The 5 Whys technique is a problem-solving method that involves asking “why” multiple times to uncover the root cause of a problem or issue.

A: The 5 Whys technique involves repeatedly asking “why” to identify the underlying cause of a problem. After asking “why” five times or until the root cause is revealed, you can develop effective solutions to address the issue.

A: The primary purpose of the 5 Whys technique is to identify and address the root cause of a problem. It helps organizations and individuals go beyond surface-level symptoms and understand the deeper issues affecting their processes or systems.

A: The 5 Whys technique is best used when you encounter a problem or issue that needs to be resolved. It is particularly useful for complex problems, recurring issues, or situations where multiple factors contribute to the problem.

A: Yes, the 5 Whys technique can be applied to any industry or field. It is commonly used in manufacturing, engineering, healthcare, software development, project management, and various other sectors.

A: While the technique is called the “5 Whys,” the number of “whys” you need to ask may vary. The goal is to keep asking “why” until you reach the root cause of the problem, which may require more or fewer than five iterations.

A: Yes, there are a few limitations to consider when using the 5 Whys technique. It relies on the skill and knowledge of the people involved, and it may oversimplify complex problems. Additionally, it assumes a linear cause-and-effect relationship, which may not always be accurate.

A: Yes, the 5 Whys technique can be used in a group setting. In fact, involving multiple perspectives can enhance the effectiveness of the technique and lead to more comprehensive problem-solving.

Daniel Croft

Daniel Croft is a seasoned continuous improvement manager with a Black Belt in Lean Six Sigma. With over 10 years of real-world application experience across diverse sectors, Daniel has a passion for optimizing processes and fostering a culture of efficiency. He's not just a practitioner but also an avid learner, constantly seeking to expand his knowledge. Outside of his professional life, Daniel has a keen Investing, statistics and knowledge-sharing, which led him to create the website learnleansigma.com, a platform dedicated to Lean Six Sigma and process improvement insights.

Download Template

Free lean six sigma templates.

Improve your Lean Six Sigma projects with our free templates. They're designed to make implementation and management easier, helping you achieve better results.

Other Guides

5 Whys: Examples, explanations, and how to find the causes of problems

At some point, we’ve all experienced a problem with a process or strategy at work. But figuring out why the problem exists can be a daunting task. When you sit your teammates down for a discussion, emotions run high and miscommunication is common.

The 5 Whys is a powerful, easy-to-use technique for getting at the root of a problem. It empowers you and your team to understand why a problem persists and to decide on a path forward.

• What is the 5 Whys framework?

The 5 Whys is a popular problem-solving method that individuals and teams use to understand the potential causes of a specific issue. Years ago, Toyota developed the approach to help them get at the heart of complex mechanical issues, so you know it’s legitimate! The technique is easy to use: you ask why a problem happened, and then you ask four more times. By asking “why” on a step-by-step basis, you can get to the root cause of a defect, failure, challenge, or malfunction.

• When and Why the 5 Whys Analysis is Used

The 5 Whys framework is useful in a variety of situations. People love it because it helps you have a focused discussion and avoid getting distracted by other topics. You just start with a problem statement, ask why the problem exists, and keep moving through the exercise until you’ve uncovered the problem.

Here are some scenarios where you might find the 5 Whys approach to be useful.

Working on complex products

Remember, the 5 Whys technique was originally developed by Toyota. The car manufacturer needed a clear-cut way of dealing with a product that has thousands of parts. But that doesn’t mean the technique only works for large physical goods. Many organizations use the 5 Whys approach when software malfunctions, when a key deliverable with many moving parts doesn’t work properly, or when a multi-step process breaks down.

Solving complex problems

When a problem is so complex that engineers, designers, or decision-makers are scratching their heads, the 5 Whys approach may serve you well. Maybe your complicated marketing strategy didn’t hit your targets, or an important API isn’t working. Instead of getting overwhelmed, the 5 Whys framework helps you wrap your head around the problem.

Dealing with consistent problems

Maybe the problem doesn’t seem complex, but it keeps coming up. Or maybe you’ve tried multiple solutions and none seem to work. Rather than burning precious time and money on yet another risky bandaid, try the 5 Whys to finally discover what’s going on.

• How to conduct a 5 Whys analysis in 6 steps

One of the great things about the 5 Whys framework is that it’s easy to understand. Unlike many other problem-solving techniques, which can be difficult to grasp, you can explain the 5 Whys to your team in minutes. Follow these guidelines any time you need to use the approach.

Step 1 – Form your problem statement.

Start by asking your team what problem you’re about to analyze. Everyone should get a chance to articulate the problem so you’re all on the same page. Sometimes, you might find yourself using the 5 Whys approach to uncover the root of a difficult or charged obstacle. If that’s the case, give your team the time and space to be honest with each other and to have difficult conversations. Write down the problem statement for everyone to reference.

Step 2 – Ask “why has this happened?” 5 times.

Don’t be too literal with it. Feel free to amend the “why” statement to something like “Why does this keep happening?” or “Why are we having this problem?” Keep going until you’ve asked “why” five or more times. It might feel unnatural, but eventually, you’ll push through any awkwardness to uncover the root of the problem.

Step 3 – Jot down logical causes.

Okay, now you have a pretty good handle on your problem. Write down any logical causes that have followed from your 5 Whys analysis. Regardless of whether those causes came from your first “why” or your fifth, make a detailed note of them. Discuss the causes with your team and make sure you’re all agreed.

Step 4 – Hypothesize an answer.

Now that you have your logical cause, it’s time to come up with some potential solutions. At this stage, you’re just having a conversation. You don’t need to come up with the perfect solution in this meeting. Have everyone go around the room and say (or write down) a possible solution. Ask everyone to vote on the most actionable one.

Step 5 – Test your hypothesis.

Put your solution to the test with some experiments. If you’ve decided that a marketing campaign failed because you didn’t choose the correct target audience, then maybe you can come up with some A/B tests to vet possible solutions. Aim for low-stakes tests that you can use to draw meaningful conclusions.

Step 6 – Repeat until solved.

Iterate until you’ve solved the problem! Don’t be discouraged if it doesn’t happen right away. Sometimes, it might take multiple rounds of “whys” followed by many rounds of testing to uncover a solution. Keep an open line of communication among your teammates and don’t give up.

Try Miro today

• A simple 5 Whys example

The 5 Whys is an adaptable, easy-to-use framework for uncovering the root of a problem. Organizations and teams of all sizes use the framework to overcome complex, high-stakes challenges. Here’s a quick example to help you bring this method of analysis to your own team.

Let’s say your team has been working on an app for many months. You rolled out a beta version late last quarter. You were supposed to ship the app to the rest of your users at the beginning of this quarter, but a problem arose: a bunch of your early users complained of a fatal error that caused the app to crash. As a result, you couldn’t ship it, and your customers were disappointed.

Step 1 — Write down your problem statement. 

As we mentioned above, the first step in following the 5 Whys framework is to clearly and succinctly define what problem you’re trying to solve. The entire group should be clear about this issue. In this case, the problem statement is: your app wasn’t ready to ship to your customers.

Step 2 — Start with the broadest possible question.

Start with the broadest possible question. Then aim to answer it. Why wasn’t the app ready for your customers? It wasn’t ready because there was a bug in the code that caused it to crash.

Drill down into that question. Why was there a bug in the code that caused it to crash? There was a bug in the code because the engineers didn’t get user feedback in time to fix it.

Keep drilling down. Why didn’t the engineers get that user feedback? They didn’t get the feedback because the development team didn’t provide an easy way for users to submit their feedback.

Continue drilling down, asking more and more precise questions as you get closer to the answer. Why didn’t the development team provide an easy way for users to leave feedback? They didn’t provide an easy way for users to leave feedback because they weren’t clear on deadlines for the project.

Ask “why” at least one more time. Why wasn’t the development team clear on deadlines for the project? They weren’t clear on deadlines because they weren’t meeting with stakeholders often enough to know when the timeline changed.

Step 3 – Write down logical issues.

Now you have enough information to write down logical causes. It seems that this problem stemmed from a lack of communication between stakeholders. That caused the development team and engineering team to become misaligned.

Step 4 – Once you’re ready, you can come up with a possible solution to this problem.

Once you’re ready, you can come up with a possible solution to this problem. In the future, internal stakeholders will hold weekly check-ins to make sure they’re aligned on where the project is headed.

Step 5 – Put that hypothesis into action.

Here’s where you get to test out your hypothesis and see what effects it has. Moving forward, start holding weekly check-ins and see what happens. If miscommunication and confusion goes down, you’ll know you’re on the right track.Step 6 – Adjust your strategy, if needed

Resist the urge to consider a problem “solved” and move on immediately. It’s important to revisit how the solution is functioning in the weeks ahead, continually checking in with everyone on the team to see how they’re feeling about it. You may need to tweak your strategy over time.

• How 5 Whys helped solve the problem

This example clearly showcases the power of the 5 Whys. What looked like a problem with code turned out to be a symptom of miscommunication.

Although this is just a hypothetical, we all know stuff like this happens every day. But it’s often difficult to uncover the root causes of a problem without months and months of exploration. With the 5 Whys, you can overcome costly challenges in a much shorter amount of time.

• Try the 5 Whys template for free

Clearly, asking “why?” isn’t just a technique used by persistent 4-year-olds – it’s actually a quick and easy way to identify a root cause. Countless teams across different industries have had great results using this framework. Save time, collaborate with your team, and solve hard problems with Miro’s free 5 Whys template .

• How Miro helps distributed teams collaborate

Working with a remote team can be challenging — but it also offers unparalleled opportunities for creativity and collaboration. Miro’s online whiteboard helps teams overcome cultural divides, communication silos, geographic barriers, and micro-cultures to empower you to stay connected and do great things.

Miro has a variety of templates and tools for teams to help you and your team:

• Create a mind map
• Manage a scrum board
• Create user story maps and customer journey maps
• Work with sticky notes, even if you aren’t in the same room
• Generate flow charts and diagrams
• Run brainstorming sessions

And lots more… try Miro for remote collaboration today!

Miro is your team's visual platform to connect, collaborate, and create — together.

Join millions of users that collaborate from all over the planet using Miro.

Keep reading

How to streamline processes to make your org more efficient.

From chaos to clarity: How project workflows lead to success

Your guide to understanding (and improving) organizational efficiency

The Lean Post / Articles / Clarifying the ‘5 Whys’ Problem-Solving Method

Problem Solving

Clarifying the ‘5 Whys’ Problem-Solving Method

By Lean Enterprise Institute

July 19, 2018

This brief animation offers a detailed explanation of one way to discover a problem's root cause.

To help lean thinkers apply this powerful approach to overcoming  work  obstacles, LEI Senior Advisor John Shook guides lean thinkers through a detailed example from Taiichi Ohno’s  Toyota Production System : Beyond Large-Scale Production . Find a transcript below.

Let’s take a look at the problem-solving method known as the “ five whys ” or also “causal chains.” Let’s take a look first of all at how that relates to the problem-solving funnel as a frame where we began with a high-level problem—it might be something vague that we don’t fully understand, but it’s the problem coming at us on a day-to-day, moment-to-moment basis. 

What we want to do is break the problem down to understand it, get some data, get some facts, and look for patterns. And from there, that means understanding the work, which is certainly a primary characteristic of lean problem-solving, which is to go and deeply observe and understand the work. From there, we can identify a point of occurrence, sometimes called the direct cause and also can be thought of as a problem on its own.

Now we can do the fun part, which is to start asking the five whys. We can put on our investigative hats and ask why, why, why is this occurring? That will lead us to a root cause regarding which we can attach a countermeasure. 

To look at this part of the problem-solving process , the five whys or a causal chain, let’s look at the famous example from Taiichi Ohno of Toyota and the one he used starting in the 1950s of a machine breaking down. 

The problem that he saw as the machine shop manager is that machines would often break down, and his people would often just attach a Band-Aid. They would only stop it at the first level of cause, meaning that the problems would recur; they would come back. So, he trained himself and his people then always to ask the five whys, sometimes three, sometimes eight, the point being to follow the causal chain all the way down to a root cause.

In this example, he looked at a machine that had stopped working and identified with the first why that it had blown a fuse in the control box because it was overloaded. The overload caused the fuse to blow. But, he didn’t stop there and asked why again, and recognized that insufficient lubrication was getting to the bearing. So, the bearing, therefore, was causing the overload on the machine. 

Not stopping there, he went to the next cause and, asking why, found that the pump was not drawing lubricant. So, the lubricant, then, would not be sent to the bearing.

Still not stopping there. Why, again, was the pump not drawing lubricant? Because the shaft was worn, causing it to rattle and not function properly. 

Now, another why there led him to a root cause, which was that there was no strainer, which allowed metal chips to enter and damage the pump. So, with the damaged shaft, that would mean the pump wasn’t drawing lubricant, so that there wasn’t enough lubrication going to the bearing, which overloaded the machine and blew a fuse, which stopped the machine from working.

So, he’s got a five-why causal chain going down to the root, and you can check that with the “therefore chain” going up as well. 

Now he knows if he applies a countermeasure here, which is to make sure there’s a strainer, then the problem will be solved so that it doesn’t come back.

So, this is what you can accomplish with a fairly simple way of thinking so that we’re not just putting Band-Aids on symptoms—that we’re solving problems at the root cause. 

Good luck with your problem-solving attempts.

Learn How to Identify and Solve Business Problems

• Gain a solid understanding of lean problem-solving by taking the on-demand, online course Intro to Problem-Solving. Learn more and register.
• Get an in-depth instruction and intensive coaching that will improve your—and your team’s—problem-solving capabilities. Join the next Managing to Learn Remotely workshop. Learn more and register.

Managing to Learn

An Introduction to A3 Leadership and Problem-Solving.

Written by:

About Lean Enterprise Institute

Excellent, deep troubleshooting explained in detail and easy to understand. A concept well with the example.

Leave a Comment Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

Revolutionizing Logistics: DHL eCommerce’s Journey Applying Lean Thinking to Automation  

Podcast by Matthew Savas

Transforming Corporate Culture: Bestbath’s Approach to Scaling Problem-Solving Capability

Building a Problem-Solving Culture: Insights from Barton Malow’s Lean University

Related books

The Power of Process – A Story of Innovative Lean Process Development

by Eric Ethington and Matt Zayko

Welcome Problems, Find Success – Creating Toyota Cultures Around the World

by Nate Furuta

Related events

April 08, 2024 | Coach-Led Online Course

April 16, 2024 | Coach-Led Online Course

Improvement Kata/Coaching Kata

Explore topics.

Privacy Overview

• Consultancy
• Online Courses

SIGN UP TODAY

• All , Lean , Lean Management , Lean Wiki

The 5 Why Problem-Solving Technique | Root Cause Analysis

• 7 mins to read
• July 13, 2018
• By Reagan Pannell

By using the 5-why analysis, you can get to the root cause of a problem, rather than just treating its symptoms.n help.

One of the most famous and straightforward problem-solving methodologies introduced by Toyota has become known as the “Five Why’s”. It’s a tool where you simply keep asking “Why” 5 times to identify the root cause of the problem and potentially a simple solution. It’s at the heart of lean thinking and our Lean training courses .

Did you know that kids ask around 90 questions a day and many of them are just “Why”!

We all naturally ask, “Why” all the time? The last figure I heard is that kids ask around 90 questions a day, and many of them are “Why?” style questions.

And the best way to imagine how the ‘Five Whys’ work is to imagine children asking “why”… again and again. As adults, we ask “Why?” once or maybe twice. If you are at a dinner party, asking your friends “Why?” more than twice, may make us look like petulant children. To ask your boss “Why?” once may not even be possible in case it comes across threatening or disrespectful, or perhaps you will feel that its a sign of your lack of knowledge.

But asking “why” without the threatening and undermining tone is an essential way we all began to learn. Asking “why” almost gets kicked out of us at school and with it the questioning mind that we all need if we want to do something different.

VISIT OUR FREE COURSE

Ready to level up your career, lean six sigma courses.

LEAN SIX SIGMA TRAINING

Ready to level up your career, get free access to our certified lean six sigma courses.

The ‘Five Whys’ is this simple in theory.

It asks us to take an open mind to a problem and to not be afraid to keep asking why five times (plus or minus a couple depending on the situation). And what is the goal? Well, our goal is to keep drilling down until we feel that “A-HA!” moment when things suddenly make more sense, and we have uncovered a root cause.

So let’s bring this to life with a real-life example regarding the Washington Monument.

The Washington Monument and others for that matter were deteriorating quite severely in the early ’90s. The specialists were sure why. However, on the desk of Don Messersmith, an esteemed Entomologist (the scientific study of insects) was what has become one of the most famous examples of the five whys approach to problem-solving .

Just for the curious:  Messersmith, Donald H. 1993.  Lincoln Memorial Lighting and Midge Study . Unpublished report prepared for the National Park Service. CX-2000-1-0014. N.p

Idea Summary: The problem was simple: The Washington Monument in Washington D.C. is deteriorating.

Why #1 – Why is the monument deteriorating? Because harsh chemicals are being frequently used to clean the monument

Why #2 – Why are harsh chemicals needed? To clean off the large number of bird droppings being left on the monument

Why #3 – Why are there a large number of bird droppings on the monument? Because of the large number of spiders and other insects which are a food source of the birds

Why #4 – Why are there large numbers of spiders and other insects around the monument? Because the insects get drawn to the monument at dusk

Why #5 – Why are the insects attracted to the monument at dusk? Because the lighting in the evening attracts the local insects

This classic five why example shows how the goal of the “five why problem-solving” approach is to move past the first level inquiry. It would have been quite easy to change the chemical, which was causing the apparent issue or investigate different cleaning methods which may slow the deterioration but nothing more.

The solution implemented was simply to delay turning on the lights at night. The result was a dramatic 85% reduction in the midges and consequently, a massive drop in bird droppings and the level of cleaning required. The bonus was also a reduction in energy costs.*

Five Why application to Customer / User Experience

The five why problem-solving technique can be used in almost all scenarios where you are trying to resolve an identified problem. So in the example below, let’s look at customer behaviour.

In the book “Hooked (How to Build Habit-Forming Products)”, the author Nir Eyal ( www.nirandfar.com ), uses the five whys approach to dig into users behaviour and tries to identify the underlying root cause of the behaviour. He points out that “one method is to try asking the question “Why?” as many times as it takes to get to anemotion.” The emotion behind the behaviour is often the driving force and the trigger which forms habits.

Idea Summary: Problem: What drives people to use email?

Why #1 – Why would Julie want to use email? So she can send and receive messages.

Why #2 – Why does she want to do that? Because she wants to share and receive information quickly?

Why #3 – Why does she want to do that? To know what’s going on in the lives of her coworkers, friends, and family.

Why #4 – Why does she need to know that? To know if someone needs her.

Why #5 – Why would she care about that? She fears to be out of the loop

While the final “why” appears to point to something very different than the Washington Monument example they both uncover a root cause. 

The first example is that the lighting is attracting the midges.

In the second example – its finding the root emotion that drives people to use a particular product and knowing that this emotion can help business connect with their customers at a deeper level to build successful products that a customer wants to engage with.

Here is Edward Bear, coming downstairs now, bump, bump, bump on the back of his head, behind Christopher Robin. It is, as far as he knows the only way of coming downstairs, but sometimes he feels that there really is another way, if only he could stop bumping for a moment and think of it. Winnie the Pooh Tweet

Reagan Pannell

Reagan Pannell is a highly accomplished professional with 15 years of experience in building lean management programs for corporate companies. With his expertise in strategy execution, he has established himself as a trusted advisor for numerous organisations seeking to improve their operational efficiency.

Our Training Courses

Fundamentals of lean.

• Lean Six Sigma White Belt Course

Lean Thinking Business Course

• Lean Six Sigma Yellow Belt Course
• Lean Six Sigma Green Belt Course
• Lean Six Sigma Black Belt Course

Yellow Belt Course

View all courses

Download | learn more, recent articles.

The Difference Between Strategy and Strategic Execution

Small Steps, Big Gains: The Case for Incremental Improvement

Maximising Efficiency and Profitability: Exploring the Benefits of Lean Consultancy

Empowering Leaders: The Imperative for Problem-Solving Training

Importance of Free Online Courses in Business Management

Marrying Online Courses with Real-World Projects

View all articles, green belt course.

Lean Six Sigma Courses

Lean Six Sigma Black Belt Certification Online

Free Lean Six Sigma Certification | Fundamentals of Lean

Lean Six Sigma Yellow Belt Online Certification

Lean Six Sigma Green Belt Online Certification

Lean Six Sigma White Belt Online Certification

Other articles.

5 Benefits and Power of A3 Problem Solving. Designed by Toyota

01 – Don’t Kill Momentum | Change Management | Principles of Lean

Harnessing the Power of the Leadership Circle Profile | Leadership

Principles of Persuasion to Manage Change in Organizations

05 – Work to Establish Standardised Processes

The Quality Assurance Society: A Professional Overview

What is a Matrix Plot? An Introduction from Leanscape

5 Bullet Friday Lean Thinking Newsletter | 8th Sept 2023

The Kano Model: A Step-By-Step Guide for Doing a Kano Analysis

DPMO: Defects per million opportunities explained

Lean Lifestyle Design

Related articles.

2 Proportion Test: The Basics

Get Your Company to Fund Your Lean Six Sigma Training

LeanScape launches the Online Lean Academy

Process Mapping – An Essential Business Tool

Poka Yoke: The Lean Concept of Mistake Proofing

Lean six sigma online courses.

FREE COURSE | YELLOW BELT | GREEN BELT | BLACK BELT | MASTERCLASS | WORKSHOPS

Ready to start your journey into the world of Lean with this free course?

FREE COURSE

LSS White Belt

Looking to get your first recognised Lean Six Sigma Certificate

Lean Thinking

A Lean focused continious improvement certification course

LSS Yellow Belt

Propel your career forward, tackle complex problems and drive change

LSS Green Belt

The ultimate fast-track for future leadership

LSS Black Belt

Become an expert in change management and complex problem-solving.

Subscribe to Newsletter

Keep up to date to the latest insights, courses, training, webinars and more. Join our newsletter today.

Take Our Business Quiz

Ready to test your business improvement knowledge and level up?

Root Cause Analysis – The 5 Whys Technique

This elementary and often effective approach to problem-solving promotes deep thinking through questioning, and can be adapted quickly and applied to most problems. For example, asking “Why?” may be a favorite technique of your three-year-old child in driving you crazy, but it could teach you a valuable problem-solving technique.

“If you don’t ask the right questions, you don’t get the right answers. A question asked in the right way often points to its answer. Asking questions is the ABC of diagnosis. Only the inquiring mind solves problems.” – Edward Hodnett

The “5 Whys” is a simple problem-solving technique that helps you to get to the root of a problem quickly, which was originally developed by Sakichi Toyota. It was used within the Toyota Motor Corporation during the evolution of its manufacturing methodologies. It is a critical component of problem-solving training, delivered as part of the induction into the Toyota Production System.

How to Conduct 5 Whys Analysis?

When you’re looking to solve a problem, start at the result and work backward (toward the root cause), continually asking: “Why?” You’ll need to repeat this over and over until the root cause of the problem becomes apparent.

The 5 Whys strategy involves looking at any problem and asking: “Why?” and “What caused this problem?” Very often, the answer to the first “why” will prompt another “why” and the answer to the second “why” will prompt another and so on; hence the name the 5 Whys strategy.

The 5 Whys exercise is vastly improved when applied by a team and there are five basic steps to conducting it:

• 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.
• Ask “Why” the problem happens and write the answer down below the problem.
• 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.
• Loopback 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.
• After settling on the most probable root cause of the problem and obtaining confirmation of the logic behind the analysis, develop appropriate corrective actions to remove the root cause from the system.

Edit this Diagram

5 Whys Example

The vehicle will not start. (The problem)

• Why? – The battery is dead. (First why)
• Why? – The alternator is not functioning. (Second why)
• Why? – The alternator belt has broken. (Third why)
• Why? – The alternator belt was well beyond its useful service life and not replaced. (Fourth why)
• Why? – The vehicle was not maintained according to the recommended service schedule. (Fifth why, a root cause)

Note: A 5 Whys analysis sometime could be taken further to a sixth, seventh, or higher level, but five iterations of asking why are generally sufficient to get to a root cause.

5-Whys Criticisms

Here are each of the criticisms as listed on the Wikipedia:

• Stopping at symptoms, not the root cause
• Limited by the investigator’s knowledge.
• Not asking the right Why questions.
• Not repeatable – Different people build different 5 Whys.
• The tendency to isolate a single root cause

©2024 by Visual Paradigm. All rights reserved.

• Terms of Service
• Privacy Policy
• Security Overview

[email protected] / 248.906.8605

The 5 Whys for Problem Solving

The problem with problems.

The late inventor, Charles Kettering, once said, “A problem well-stated is a problem half-solved.” And while this might seem a bit far-fetched, the research suggests that this notion isn’t far from the truth. If you look at just about any problem-solving study, they all come to the same conclusion: the best way to solve a problem is to be sure that your problem is well-defined.

The issue with this thinking is that problems are almost always more complex than our initial belief. For example, if productivity dips at your company, you might first define the problem as a lag in motivation. However, if you start digging underneath the surface and asking the right questions, you might learn that the dip in productivity is due to a company-wide communication error. This is a tad more complex than your original assumption. Had you began implementing change at the surface-level definition, productivity would likely have remained low.

What is the 5 Whys Technique?

Lack of well-defined problems often stems from over-worked teams and limited time. That’s where the 5 Whys tool comes in handy. The founder of Toyota invented the 5 Whys technique in the 1930s as a clean and simple way to identify the root cause of a problem or issue. Its title gives away its process: Ask ‘why’ five times or until you’ve drilled down to the core cause of the problem.

Four Easy Steps

1. Problem Definers . While asking ‘why’ five times sounds relatively simple, it’s useless if the right people aren’t in the room to provide the answers. To get to the root of the problem quickly, gather the people on the front lines who deal directly with the problem every day.

2. Problem Statement. Start with the surface level problem and define it in one, clean, fact-based statement, free from bias or emotion.

3. Ask Why . The idea here isn’t to gather guesses or hypotheses but answers grounded in fact and reliably observed. This critical step prevents thought spiraling and helps keep your team focused on real solutions.

4. Repeat Four Additional Times . The next step is to ask four additional whys for each of the responses in step 3. If the answer to the first why isn’t apparent, it’s possible for folks to come up with several plausible ‘whys.’ This will ensure that you’ve followed every possible lead to the core problem. See below for a simple example.

5. Don’t Overdo It. The number five is more of a guideline. While there may be times it takes longer than five rounds, you might also reach a root cause in less. You’ll know you’ve gotten to the root cause when the responses are no longer useful.

This is only the beginning. Once you’ve gotten to the root cause, it’s time to discuss the strategies to properly address the issue so it doesn’t continue. In the case of our example, perhaps you decide to assess software updates on a regular schedule, preventing the need for last-minute decisions. Regardless of the final solution, monitoring the solution’s effectiveness will be essential to ensure the problem is solved long-term.

Related Posts

Maximizing Talent Retention: Leveraging Lean Practices and Six Sigma for Business Success

How A Perspective Shift Enhances Creativity And Problem Solving Skills

Mistake Proofing

Lean Works for More than Manufacturing

[email protected] 248.906.8605

Subscribe To Our Newsletter

Receive our email newsletter for useful articles, tips, and tricks for boosting your business’ efficiency and success.

© Copyright 2001 - 2024 | Lean Learning Center | All Rights Reserved

Privacy Statement | Legal Statement

Partners Zone

• April, 2023
• What Are The 5 Whys?

Problem-solving is the bread and butter of most factories today, but not all organisations solve their problems the same way.

Today, we dissect the operating principles behind the 5 Whys method, exploring its advantages, use cases, and relevance.

What do the 5 Whys mean?

By definition, 5 Whys is a problem-solving technique that uses Root Cause Analysis (RCA) to understand the problem in detail and solve it permanently. It’s considered one of the most effective problem-solving techniques in lean management , and it works best to solve simple problems.

This method was developed by Sakichi Toyoda, founder of Toyota, and incorporated into the Toyota Production System (TPS).

The 5 Whys work best to solve relatively simple issues, as anything too complex will need more robust problem-solving tools such as 8D, Cause Effect Analysis, or QRQC .

How do the 5 Whys work?

This method is relatively straightforward. All you have to do is identify the problem and then ask why five times .

Sometimes, you might find the root cause before you reach your fourth line of inquiry.

Sometimes, you might have to ask why a few more times to reach the root cause.

To make the 5 Whys method really successful, there is a process you need to follow, and it goes like this:

Step 1 — Create a team

The more relevant people you include to find a solution to the problem, the faster and more effective the resolution will be.

When you’ve decided who will be part of your team, you should appoint a leader to guide the process and keep everyone on track.

This person is known as the 5 Whys Master .

Step 2— Identify the problem

The problem needs to be identified and clarified beyond any reasonable doubt . Your team should define the problem and explain it in a specific statement. 

This keeps everyone focused on the problem, giving them a concise account of the situation.

Step 3 — Ask Why? five times

The first Why? is on your team.

The other four, on your 5 Whys Master .

Essentially, the team starts asking the first question, and then the 5 Whys Master leads the process through the rest of the questions.

Sometimes, you might need more than five whys to solve the issue.

Sometimes, you might need less.

However long it takes, you need to reach the root cause of the issue , which will always be linked to a management issue or a design flaw.

STEP 4 — Correct the problem

When the problem is identified, your team discusses actions or countermeasures to solve the issue.

The 5 Whys Master will then decide who does what, delegating responsibility among the team members.

STEP 5 — Keep track of your results & share them

Monitoring helps you see if the countermeasures you take to solve the issue are working.

It also gives you great insight into what you’re doing right, and what could be done better.

You also need to share your findings so that everybody can access them and learn from the process.

To make sure you’re using the 5 Whys method to its fullest extent, you need to make sure that you/your team:

• Know when to stop asking Why → when the answers you’re getting are no longer useful or don’t bring anything else to the process, you need to stop asking further whys and take another approach instead.
• Address the root cause(s)   → finding the root cause it’s great, but not enough. Once you find it, you need to make sure you’re taking the appropriate measures to fix the issue and prevent it from happening again.
• Monitor your measures → once you take measures to address the issue, it’s fundamental that you monitor how the measures impact the issue. Are they effective? Could they be even more effective? When you monitor how your measures are performing, you’ll be able to solve the root cause faster and more efficiently.
• Share your results → keeping your results a secret helps nobody. When you find the root cause, you address it, and you fix it, you need to share your results with everybody, so they can learn from it. Even when the root cause isn’t fixed, you need to share your results to keep everybody on track regarding the issue and its current status.

5 Whys in real life

Here’s what a 5 Whys method looks like in real life:

In this particular instance, after finding the root cause, we then come up with a solution. In this case, it could be to make sure we train the workers on the standards regarding changing the pipes.

This example shows how easy and cost-effective it is to set up this problem-solving method to find the root cause of a problem in your factory.

Advantages of the 5 Whys methodology

This method brings with it a good number of advantages, and it might be exactly what you need to implement in your factory, some of which are: 

• It helps your teams find, understand, and correct the root cause of the problem
• It fosters teamwork
• It’s very easy and flexible to implement
• You can use it alongside other problem-solving methods, such as Root Cause Analysis or Six Sigma
• It can be templated — just create a set structure and prompts that can be used whenever this method needs to come into play

mlean ® and the 5 Whys method

The 5 Whys method is a great problem-solving technique that helps you find the root cause of an issue and take measures to correct it quickly and efficiently.

But sometimes, this method alone isn’t enough to solve your problem.

Our mlean® Production System includes a wide range of problem-solving methods to ensure your issues are always dealt with using the right tools .

Our software is the most complete toolkit for digital industrial operations, integrating a variety of lean philosophies and processes like Kaizen or Hoshin Kanri .

mPS digitalises your factory processes, increases your workers’ safety and motivation, and increases revenue.

Book a demo and see for yourself!

Request a Demo Today

Alba Rodriguez

• Industry Trends (27)
• mlean news (21)
• Product (2)
• Standardization (4)
• Strategy (5)

Recent Post

The link between continuous improvement and worker satisfaction

Factory performance: how to level up your game

How delivery impacts your factory’s ability to be competitive

Connect with us

on social media

with any questions

Book a demo

Duis aute irure dolor in reprehenderit in voluptate.

• Privacy Overview
• Strictly Necessary Cookies
• 3rd Party Cookies
• Cookie Policy

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.

This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.

Keeping this cookie enabled helps us to improve our website.

Please enable Strictly Necessary Cookies first so that we can save your preferences!

More information about our Cookie Policy