5 why problem solving method

• RCA 101 – 5-Why Analysis (Free Training)
• RCA201 – Basic Failure Analysis
• RCA 301 – PROACT® RCA Certification
• RCA401 – 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: April 23, 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

Post-Incident Analysis for Enhanced Reliability

How To Conduct Incident Analysis?

The Role of Artificial Intelligence in Reliability Engineering

Ultimate Guide to Swiss Cheese Model and Its Applications

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:

The 5 Whys Process We Use to Understand the Root of Any Problem

Former Director of People @ Buffer

Sometimes things don’t go according to plan. Tools break, wires get crossed, the best-laid plans fall apart.

And on those occasions, it helps to know exactly what happened—so it doesn’t happen again.

Moments like these are when we at Buffer turn to a simple but remarkably effective process: The 5 Whys.

It’s just as it sounds: A discussion of the unexpected event or challenge that follows one train of thought to its logical conclusion by asking “Why?” five times to get to the root of what happened.

But it’s also a lot deeper than that, too. Let’s take a look at the origin and history of this unique process, and I’ll tell you a bit about how it works for us on our remote team at Buffer—and how it could work for you, too.

The origin of the 5 Whys

The 5 Whys technique was developed and fine-tuned within the Toyota Motor Corporation as a critical component of its problem-solving training.

Taiichi Ohno, the architect of the Toyota Production System in the 1950s, describes the method in his book Toyota Production System: Beyond Large-Scale Production as “the basis of Toyota’s scientific approach . . . by repeating why five times, the nature of the problem as well as its solution becomes clear.”

Ohno encouraged his team to dig into each problem that arose until they found the root cause. “Observe the production floor without preconceptions,” he would advise. “Ask ‘why’ five times about every matter.”

Here’s an example Toyota offers of a potential 5 Whys that might be used at one of their plants.

Today, the method is used far beyond Toyota, and it’s particularly popular in the world of lean development. A lot of what we know at Buffer  in implementing the 5 Whys has come from The Lean Startup ‘s Eric Ries, who does an amazing job describing the 5 Why’s in these two posts.

How the 5 Whys process works

At our startup, we perform a “5 Whys” after something unexpected has occurred—and that means we perform them a lot! We keep a “5 Whys” folder in our team’s Dropbox Paper account, and the folder has 20+ notes files and counting (not to mention the 5 Whys docs that might not be categorized into the folder). ‘Fires’ of various sizes are inevitable—and probably the only constant in the life of a startup.

We’ve held these discussions in every facet of Buffer, from engineering to happiness to marketing and more, and the same process holds true no matter whether the problem is technical or more human-based. Here’s how Eric Ries explains:

“Five Whys involves holding meetings immediately following the resolution of problems the company is facing. These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. Any time something unexpected happens, we could do some root cause analysis.”

It’s important to note that the purpose of the 5 whys isn’t to place blame , but rather to uncover the root cause of why something unexpected occurred. Additionally, it helps a team create small, incremental steps so that the same issue doesn’t happen again (to anyone).

Tweet this ?

At Buffer, the habit of conducting 5 Whys originated from the engineering team. Here’s how our former CTO Sunil Sadasivan describes the changes that have resulted from making these a routine part of how we operate:

“What I really like about this is that it lets us worry about issues when they happen, and it helps us work towards ensuring they won’t happen again. At the same time, it lets us not have to worry about issues that haven’t happened.  I now trust if something comes up that we didn’t foresee, we’ll conduct a 5 whys and learn from it.  We let the 5 whys dictate what documentation we need in place or adjustments to make in our on-boarding process.”

Want to try it for yourself?

The 5 main steps to the the 5 Whys

Step 1: Invite anyone affected by the issue

As soon as the problem or situation is identified (and all immediate concerns are dealt with), invite anyone at all on the team who was affected or noticed the issue to be involved in a 5 Whys meeting. As a remote team , we hold ours via Zoom.

Step 2: Select a 5 Whys master for the meeting

The 5 Whys master will lead the discussion, ask the 5 whys, and assign responsibility for the solutions the group comes up with. The rest of those involved will answer those questions and discuss.

In our experience, anyone can be a 5 Whys master — there are no special qualifications, and it doesn’t have to be the leader of the project or the originator of the issue. We’ve also found that it’s a good idea for the 5 Whys master to take notes for the meeting, unless he or she would like to assign someone else to this.

Step 3: Ask “why” five times

Dig at least five levels deep into the issue with five levels of “whys.” This seems like the simplest part but can in fact get a bit tricky! Getting the right question to start with, the first why, seems to be the key.

When we conduct our 5 Whys, it can feel natural and almost beneficial to go down all potential paths and be really comprehensive. However, this can widen the scope of how much learning and corrective actions need to occur. This is meant to be a ‘lean’ process in which picking one path allows us to perform just the amount of corrective actions needed to solve a problem.

We often have to tell ourselves we just need to pick one and go with it. If the same problem seems to occur again, then we can do another choosing the other route.

Together, we work through each of those five whys and discover actionable steps that have been or will be taken.

Step 4: Assign responsibility for solutions

At the end of the exercise, we go through each why question-and-answer pairing and come up with five related “corrective actions” that we all agree on. The master assigns responsibility for the solutions to various participants in the discussion.

Step 5: Email the whole team the results

After each 5 Whys process, someone involved in the meeting will write down what was discussed in the clearest, plainest language as possible.  Then we add it to a Paper folder and—in one of the most important steps of the whole process—email the whole team with the results.

This makes sense to do, and not just for a company like Buffer that focuses on transparency. It’s super useful for everyone on your team to stay in the loop and understand any steps you’re taking as the result of a 5 Whys.

Eric Ries explains why the email is so important:

The advantage of sharing this information widely is that it gives everyone insight into the kinds of problems the team is facing, but also insight into how those problems are being tackled. And if the analysis is airtight, it makes it pretty easy for everyone to understand why the team is taking some time out to invest in problem prevention instead of new features. If, on the other hand, it ignites a firestorm – that’s good news too. Now you know you have a problem: either the analysis is not airtight, and you need to do it over again, or your company doesn’t understand why what you’re doing is important. Figure out which of these situations you’re in, and fix it.

Put it all together and the process looks like this:

Some real-life 5 Whys examples

To take the 5 Whys from theoretical to actual, here’s a look at a few moments in Buffer’s history that have called for a 5 Whys meeting.

In early 2014, we had a brief systemwide outage. Here’s a look at the 5 Whys the team conducted:

And the corrective actions that resulted:

Here’s an example from the customer happiness world. One of our Happiness Heroes wanted to understand how he might have handled a customer’s problem better, so he performed a modified 5 Whys as a reflection and shared it with the team.

I have learned so much from viewing these examples and being part of 5 Whys processes. It’s been great to develop a habit of reflecting anytime something unexpected happens and taking incremental steps so that we change what happens the next time around.

The 5 Whys in daily life

Although the 5 Whys is most widely used for manufacturing/development use, I’ve found that it is also quite applicable to daily life in any situation where one might seek deeper understanding—of a problem, a challenge or even a motivation behind an action.

This quick graphic from Start of Happiness provides a great example:

Ever since learning about the 5 Whys, I find myself  asking “why?” a lot more often.

Over to you

What sort of process do you use to get to the root of unexpected situations or challenges in your work or life? Have you ever tried the 5 Whys?

I’d love to hear your insights in the comments!

P.S. If you liked this post, you might enjoy our Open blog newsletter . Receive each new post delivered right to your inbox! Sign up here .

Try Buffer for free

140,000+ small businesses like yours use Buffer to build their brand on social media every month

Related Articles

As part of our commitment to transparency and building in public, Buffer engineer Joe Birch shares how we’re doing this for our own GraphQL API via the use of GitHub Actions.

TikTok's parent company must divest the app or face a ban in the U.S. Here's everything we know, plus how to plan ahead.

How the Buffer Customer Advocacy Team set up their book club, plus their key takeaways from their first read: Unreasonable Hospitality by Will Guidara.

140,000+ people like you use Buffer to build their brand on social media every month

Copyright © 2024 Buffer | Privacy | Terms | Security

• Social Media Marketing
• Instagram Marketing
• Social Analytics
• News and Trends
• Best apps and tools
• Inside Buffer
• Remote Work
• Transparency
• Blog & podcasts
• Best Time to Post on Social Media
• Social Media Blog
• Social Media Glossary
• About Buffer
• Our culture

• Join Mind Tools

Getting to the Root of a Problem Quickly

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.

Click here   to view a transcript of this video.

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 be more effective.

This simple 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. 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.

Finding This Article Useful?

You can learn another 44 problem-solving skills, like this, by joining the Mind Tools Club.

Subscribe to Our Newsletter

Receive new career skills every week, plus get our latest offers and a free downloadable Personal Development Plan workbook.

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.

Try to move quickly from one question to the next, so that you have the full picture before you jump to any conclusions.

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.

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.

The important point is to stop asking "Why?" when you stop producing useful responses.

As you work through your chain of questions, you may find that someone has failed to take a necessary action. The great thing about 5 Whys is that it prompts you to go further than just assigning blame , and to ask why that happened. This often points to organizational issues or areas where processes need to be improved.

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.

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.

Infographic

You can see our infographic on the 5 Whys method here:

This site teaches you the skills you need for a happy and successful career; and this is just one of many tools and resources that you'll find here at Mind Tools. Subscribe to our free newsletter , or join the Mind Tools Club and really supercharge your career!

Rate this resource

The Mind Tools Club gives you exclusive tips and tools to boost your career - plus a friendly community and support from our career coaches! 

Comments (77)

• Over a month ago BillT wrote Hi hunyakvera, Thanks for your observant feedback. Sakichi Toyoda died in October of 1930, and is the creator of the 5 Whys. Also, he is stated as the founder of Toyota as he challenged his son to start a business that applied the principles of Lean and the 5 Whys. His son Kiichiro first continued with the loom company, and then decided he could do the same for any company, primarily a car company that he called Toyota. BillT Mind Tools Team
• Over a month ago hunyakvera wrote Hi! Great article. However Sakichi Toyoda died in the year 1930, so i don't see how he could have developed this technique in the 1930s. Either 1930 in his last year of life, or the date is wrong. Also, he wasn't the founder of Toyota. His son was. However, he was the founder of Toyoda companies, but not Toyota
• Over a month ago Midgie wrote Hi MGlasscock, Welcome to the Club! Indeed this 5 Whys approach is a great technique to get to the bottom of things! It would be great to meet you so come on over to the Forums and introduce yourself. Also if you have any questions, just let us know and we will be happy to help. Midgie Mind Tools Team

Please wait...

The Simple Yet Powerful 5 Whys Method for Effective Problem-Solving

Updated: May 16, 2023 by Lori Kinney

As a child, you were always asking your parents “Why this?” “Why that?” “Why can’t I do this?” “Why can’t I do that?” Little did you know that you were preparing yourself to be a problem-solver looking for root causes when you would grow up. 

This article will discuss what is the 5 Why method of looking for a problem’s root cause, how to correctly ask the questions, and what benefits and best practices there might be to help you do a better job of improving your processes. 

Overview: What are the 5 Whys? 

The 5 Whys technique was developed in the 1930s by Sakichi Toyoda, the Japanese industrialist, inventor, and founder of Toyota Industries. The 5 Whys technique is an iterative, team-driven process that interrogates the problem by asking Why(?) a number of times, usually 5, thus driving the search to uncover the root cause of a problem.

Rather than using the phrase “solutions” once the root cause is found, the 5 Whys uses the term “countermeasures.” A countermeasure is action-oriented and seeks to prevent the problem from happening again, whereas a solution may just seek to deal with the symptoms.

Here is the 5 Why technique in a nutshell:

First, you must have a defined problem.  Put together a team to address the problem. Then:

• List: Using a white board, flip chart, butcher paper, or other visual display, list five potential reasons for your problem.
• Evaluate: Using data, subject matter experts, or experience, evaluate each of the five potential reasons.
• Select: Select the one reason that seems to be the most likely potential cause.  
• List again: Now list five potential reasons for the potential cause that you selected.
• Evaluate again: Evaluate those five new potential reasons.
• Select again: Again, select the one reason that seems to have the most potential as a root cause.

Repeat the process of list, evaluate, and select as many times as needed until you feel that the root cause has been uncovered. The 

Unfortunately, many organizations don’t do the 5 Whys the correct way. Often, they:

• Look at the problem
• Offer one potential cause
• Ask “Why?” for that one cause
• And continue one at a time 

In the end, you will have only explored five potential causes. Doing it with the list, evaluate, and select approach, you will have assessed 25 potential causes by listing five for each iteration.

3 benefits of the 5 Whys 

This technique has been around since the 1930s. It has been shown to work and can be successfully applied to many situations. 

1. It is a simple yet powerful tool

With just the use of a flip chart and a few markers, a group of people can usually get to the root cause of a problem relatively quickly. 

2. A sking “why” 5 times focuses the team on getting to the root cause

Using this approach in a disciplined fashion will get you to focus on the causes and prevent you from jumping to conclusions as to the solution. 

3. Helps engage the people who deal with the problem   

Getting input from the people who deal with the problem and making them part of the solution can result in better buy-in and engagement. 

Why are the 5 Whys important to understand? 

While the 5 Why technique is simple, you must understand the proper mechanics of the method so that you get the best results possible.

It encourages collaborative problem-solving

Getting the team to collaboratively work together is not only important for the 5 Why problem solving session but for any future activities that would improve the process.

You want to focus on improvement, not blame  

Do not allow such causes as “ human error,” “employee attitude,” “communication,” and other generic and ill-defined reasons to be used as the root cause.  

Understand the importance of having support from leadership  

Hopefully, in the end, the team will come up with a number of countermeasures that will remove the root cause(s) of a problem. It will usually fall upon leadership to provide the resources to make the change. Avoid future frustration by having management on board with this technique from the beginning. 

An example of the 5 Whys in use 

An example is in order.

You are on your way home from work, and your car stops:

• Why did your car stop? Because it ran out of gas.
• Why did it run out of gas? Because I didn’t buy any gas on my way to work.
• Why didn’t you buy any gas this morning? Because I didn’t have any money.
• Why didn’t you have any money? Because I lost it all last night in a poker game.

This example should illustrate the importance of digging down beneath the most proximate cause of the problem. Failure to determine the root cause assures that you will be treating the symptoms of the problem instead of its cause, in which case, the disease will return — that is, you will continue to have the same problems over and over again.

Also note that the actual numbers of whys is not important as long as you get to the root cause. One might also ask, “Why did you lose all your money in the poker game last night?”

Here’s another example. The Washington Monument was disintegrating:

• Why? Use of harsh chemicals
• Why? To clean pigeon poop
• Why so many pigeons? They eat spiders and there are a lot of spiders at monument
• Why so many spiders? They eat gnats and lots of gnats at monument
• Why so many gnats? They are attracted to the light at dusk.

Countermeasure: Turn on the lights at a later time.

3 best practices when thinking about the 5 Whys 

Doing the 5 Whys is simple, but not easy. Keep the team on task and take advantage of the team members’ knowledge, experience, and enthusiasm.

1. Don’t try to do this alone; use a group of people involved in the process  

Five heads are better than one. Select a diverse group of team members to get the widest perspective. 

2. Focus on counter measures rather than solutions  

The solution to a headache is to take two aspirin. The countermeasure to a headache is to find out what is causing it and remove it. 

3. Be open and respectful of everyone’s input and participation  

Everyone’s idea has value. You never know who might hold the hidden gem. Listen and be respectful so people will feel comfortable offering their ideas — you’ll also have better buy-in once you find the root cause. 

Frequently Asked Questions (FAQ) about the 5 Whys

Can i ask more than 5 whys  .

Yes. You can ask more than five or less than five. The key is, how many questions does it take to get to what appears to be the root cause.

Can I use the computer to do the 5 Why exercise?  

It’s recommended that you use something more tactile like flip charts. This way, you can tear them off and hang them on the wall for everyone to see. The more visual you make the work, the better.

Should my manager run the 5 Why session or someone else?

Since the manager often has a stake in the outcome of the process, it might be best to use a neutral facilitator who can help keep the team on task, ask the right questions, and not get defensive when the potential causes are mentioned.

The 5 Whys wrapped up

The 5 Whys is an iterative, team-based approach to asking questions about the potential causes of a problem. Once the problem is defined, the potential causes should be listed, evaluated, and selected, and then repeated as many times as necessary to get to the root cause. 

Once the root cause(s) is identified, the team should recommend specific, action-oriented countermeasures to mitigate or eliminate the root cause of the problem. Remember, don’t just address the symptoms; you must find the underlying cause, otherwise the problem will resurface sometime in the future.

About the Author

Lori Kinney

Problem Solving using the 5 Whys

This post is also available in: German

The 5 Whys template is a simple, yet powerful tool used for root cause analysis. Based on the technique developed by Sakichi Toyoda , it takes an iterative approach to problem-solving. Starting with an initial problem statement, a question beginning with ‘why’ is asked 5 times in order to zero in on the root cause. 

Along with the Fishbone Diagram , the 5 Whys template is a seminal technique for problem-solving through a deeper understanding of causal relationships. Let us understand this method in a little more detail. Or directly use the template . 

What is the 5 Whys root cause analysis?

The 5 Whys problem-solving method was originally developed for Toyota Motor Corporation’s production facility. The technique starts with a single problem and asks a ‘why’ question based on the answer to the previous question. 

The iterative process of asking ‘why’ ensures that each step is logically connected to the previous by a cause and effect relationship. Each ‘why’ takes you one step closer to finding the root cause. 

5 Whys analysis in six sigma

Six sigma is all about waste reduction, process optimization and quality improvements. The simplicity of the 5 Whys method lends itself well to the analysis stage of six sigmas. Since the technique eschews complex statistical methods, individuals from across functions and departments can participate in the process. It’s a great technique for driving process improvements and ensuring past mistakes do not reoccur.  

How to use the 5 Whys template

Since a 5 Whys session is in essence a brainstorming session, it is important to work with a whiteboard and sticky notes. Mapping out the process on an online whiteboard helps people better visualize what happened. Multiple stakeholders can work on Conceptboard’s collaborative template in real time and add their ideas on digital sticky notes . The template is completely editable.

Steps to using the 5 whys template

• Asking the right question – Before you embark on a 5 whys analysis, it is important to start with the right question. Here, a problem statement template can come in handy.
• Gather the right people – All key stakeholders and especially decision makers should be involved in the session.
• Assign a moderator – It is important for the moderator to drive the conversation, ensure each of the steps are followed and assumptions avoided 
• Prepare the board in advance – Load the template by clicking the ‘+’ button and choosing ‘Insert template’. Drag and drop the 5 Whys template and share the board with the team.
• Add sticky notes and write down your comments for each round of the process.
• Once the analysis is complete, identify the action points and export the board as a PDF or print it out.

5 Whys Example

Here’s an example of the 5 Whys process and the solutions that came up from the analysis.

• Why was the hospital’s new health care app delayed by 4 weeks? Answer : Additional complexities were revealed in the testing phase.
• Why did additional difficulties come up? Answer : The creation phase did not include a solution for a major use case.
• Why did the creation phase miss a major use case? Answer : The original brainstorming sessions did not include employees from the department.
• Why were key employees missing from the brainstorming sessions? Answer : The brainstorming session was led by a particular department. In this case, additional departments were brought in later in the development process.
• Why is this process managed by a particular department? Answer : This is how it’s always been done.

Solutions found:

Create a new process that builds on the strengths of all departments and encourages interdepartmental collaboration. Ensure key employees from every department are present in all brainstorming sessions throughout all phases.

If you’ve like this template, we’ve also rounded up 15 of our favourite brainstorming techniques and templates that help you generate new ideas and drive innovation. For additional problem-solving templates, you can use our A3 problem-solving template .  Also check out our list of retrospective ideas and templates you can use today with your team.

Use the free template with your team & customize as you go!

Use Template

More interesting articles for you

OZG 2.0: The future of digital administration in Germany is FIM

Since its introduction in 2017, the Online Access Act (OZG) has aimed to make it easier for citizens and companies to access administrative services and make them available digitally.

Unwrap the Joy: Elevate Your Team’s Holiday Spirit with Our Exclusive Christmas Game Template!

The holiday season is upon us, and at Conceptboard, we’re thrilled to unwrap the gift of festive cheer with our special Christmas Game Template!

Wireframe Template – A structure to build something great | Free Template

By using Wireframe Templates, you can streamline your workflow and ensure a more efficient and effective design process.

2 Comments . Leave new

I disagree with your statement “Six sigma is all about waste reduction, process optimization and quality improvements.”

Six-Sigma is all about “variation reduction” using statistical tools and techniques and pioneered by Motorola.

Lean is all about “Waste reduction” using Lean tools and techniques as part of Lean Manufacturing/the Toyota Production System developed by Toyota.

(1) The example solution is not a solution, it is the recognition that something new needs to happen, followed by requirements on how that is to be achieved.

(2) A single thread down (one answer per question) is insufficient for most difficult problems (i.e. ones that require a 5-why’s!) Each question will generate several answers, each of which is drilled down on. Then answers to different questions that are the same are linked into a lattice. If you are lucky it all comes together into a single item at the bottom of the diagram. One ends up with several dominant threads from top to leaf nodes, each of which has to be dealt with.

(3) The 5-why’s identifies several possibly independent causes. These must be dealt with using a problem solving method — which 5-why’s is not. It is a problem identification method.

Leave a Reply Cancel reply

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

Post Comment

Experience the power of visual collaboration

Experience how Conceptboard boosts your team’s hybrid collaboration and communication.

No credit card

No commitments

Start right now

The 5 Whys Approach for Root-Cause Analysis: Definition, Example, and Template

Fahad Usmani, PMP

February 4, 2024

You often face a problem and conduct a simple brainstorming session to find a solution. You find the solution and implement it, but a little later, the problem resurfaces again with probably more intensity.

Such problems require a more in-depth analysis to find the root causes of the problems and tackle them permanently. The 5 Whys Approach (often referred to as “5Y”) is useful when finding solutions for recurring or difficult problems. 

Today’s article will discuss the 5 Whys Approach and provide examples and templates.

Historical Background of the 5 Whys Approach

The 5 Whys Approach was developed by the Toyota Motor Corporation and popularized in the 1930s by Sakichi Toyoda, a Japanese industrialist and creator of Toyota Industries. Taiichi Ohno was also one of the founders of the technique. In Ohno’s book, Toyota Production System: Beyond Large-Scale Production, he said, “By saying ‘why’ 5 times, the essence of the issue and its solution become evident.”

It evolved and became more popular in the 1970s.

Toyota follows a “go and see” philosophy, where they make decisions based on an in-depth understanding of what is “really” happening on the shop floor rather than someone sitting in the meeting room and assuming what might have happened.

The 5 Why technique follows this philosophy, and it is the most effective when you get answers from people who have experience with the issues or the problem at hand. 

What is the 5 Whys Approach?

The 5 Whys Approach is a problem-solving technique that helps identify the root cause of an issue by asking “why” 5 times to dive deeper into the layers of the problem. 

The 5 Whys Approach is useful in all industries. A study published in the International Journal of Advanced Research in Management and Social Sciences shows how the 5 Whys Approach reduces defects and improves overall quality. The iterative nature of the questioning process helps uncover underlying issues rather than just addressing surface-level symptoms.

By continuously asking “Why?” 5 times, you can get to the source of the problem.

The 5 Hows technique then identifies a solution to the fundamental cause(s). The 5 Whys and 5 Hows are mutually beneficial. You find the root cause using the 5 whys approach, and then you find the solution with the 5 Hows method.

The 5 Whys and 5 Hows technique can help you get to the bottom of a problem and find a solution.

The 5 Whys dig into the issue, and the 5 Hows are used to flesh out the solution. 

When Can You Use the 5 Whys Approach?

You can use the 5 Whys Approach when you have recurring problems. You can also use it to improve product and/or process quality.

This technique is useful for simple to moderate problems or issues as the 5 Why technique leads to a single cause, though a complex problem may have multiple root causes. In such situations, you can use other techniques such as cause and effect analysis , failure mode and effect analysis, etc.

The 5 Whys Approach is a straightforward, adaptable strategy. Even on the first try, you can uncover the root cause swiftly. You should use this method before using more advanced techniques.

As this technique requires time, you should use this method for the problems that affect the project most. You can use Pareto analysis to separate the most recurring issues, then use the 5 Whys Approach to identify a solution to these pressing concerns.

You can use this technique with any framework or methodology. You can use it in project management , lean manufacturing, Six Sigma, etc.

How to Use the 5 Whys Approach

Use the following steps to conduct the 5 Whys Approach :

1. Gather the Experts and Explain the Problem

Bring in people involved with the problem or issue for a brainstorming session. If you are not involved with the problem, get involved before participating in the session. You should also invite some experts who have experience solving similar problems.

Define the problem, write it on a whiteboard or a sheet of paper. Make sure that it is a straightforward problem statement , then write “why” 5 times vertically. Leave enough space between two whys, so you can write questions around them.

2. Ask the First “Why”

Ask the attendees why the problem occurred in the first place. Ensure that the attendees provide factual answers. Don’t allow participants to express their opinions or thoughts.

The attendees should only answer what has happened. This ensures that your assumptions are not included in the problem. This stops collecting a vast number of answers and stops becoming a process of guessing.

Record answers around the first “why.”

3. Ask “Why” Four More Times

You will turn the answer received in the first “why” to a “why” question and ask participants to answer this why again.

You can add why to the answer received from the previous response to make it another “Why.”

4. Stop When the Root Cause is Discovered

When you receive a satisfactory response or the root cause of the problem, there is no need to ask more whys, as it will waste your time.

For example, if you find the root cause of the problem after three whys, don’t go for the fourth why.

If you find more than one cause for the problem, do the same for different branches until you find the root cause for each reason.

The number 5 in 5 Whys is only a rule of thumb . You will often need to stop on the third or fourth why, and sometimes you may need more than 5 whys. As you continue the process, you will know when it is the right time to stop.

5. Determine and Implement Corrective Actions

After identifying the root cause(s), conduct another brainstorming session . You should list approved corrective activities to eradicate the issue’s root cause. You can use the 5 Hows method to figure out the answer. For example, “How can this problem be avoided?” Continue to ask “how” until you find a solution that eliminates the root cause.

6. Monitor the Solution

After implementing the solution, you must monitor it to ensure the solution is effective and the problem is solved entirely. Based on the feedback from the shop floor workers, you can update or modify the solution to make it more robust.

5 Whys Template

Below is an example template for the 5 Whys Approach.

5 Whys Approach Examples

Let’s review the 5 Whys examples to understand this technique better.

Problem Statement 

The client declined to pay the interim payment.

Why does the client refuse to make the advanced payment? 

We didn’t finish the activities on time.

Why didn’t we finish the activity on time? 

Because the action took longer than expected.

What led to the action taking longer than expected? 

First, we didn’t have enough materials for the exercise.

Why didn’t we have enough supplies with us?

We didn’t buy the materials in time.

Why didn’t we buy the materials sooner? 

We didn’t look at the job timetable.

Failure to analyze the job timetable is the root cause of the problem. 

Corrective Actions

To minimize the lack of communication and coordination, the project team should establish strong communication channels and hold regular progress meetings.

Problem Statement

Children don’t go outside to play

Benefits of the 5 Whys Approach

• They encourage each team member to submit suggestions for ongoing improvements.
• They are a highly effective, easy-to-use tool.
• They allow you to find the root cause of the problem instead of its symptoms.
• They avoid acting before you determine whether you’ve found the root cause of the problem.
• They create a culture that values continual improvements.

Limitations of the 5 Whys Approach

The following are a few limitations of the 5 whys approach:

• This technique often oversimplifies complex issues, thus leading to a superficial understanding of the problem.
• This technique depends on the quality of the questions. If the questions are not good enough, the analysis may not provide an effective solution.
• This exercise can become a blame game if it is not approached with a collaborative, non-judgmental mindset.
• The 5 Whys are ineffective when dealing with problems that have multiple, interrelated causes.

Q1: What is the 5 Whys Approach?

The 5 Whys Approach is a problem-solving technique that asks “why” repeatedly to get to the root cause of an issue. It helps find the underlying factors contributing to a problem rather than just addressing the symptoms.

Q2: How does the 5 Whys Approach work?

The technique involves asking “why” 5 times in succession to delve deeper into the causes of a problem. Each successive “why” helps identify the immediate cause and pushes towards understanding the fundamental root cause of the issue.

Q3: When should I use the 5 Whys Approach?

The 5 Whys Approach is most effective for addressing recurring problems, complex issues, or situations in which the root cause is not immediately apparent. It’s also valuable for continuous improvement and preventing problems from reoccurring.

The 5 Whys are a problem-solving method to find the root causes of issues. They ask “why” 5 times to dig deeper into problems. They help uncover hidden reasons that allow you to find effective solutions. They are easy to use and can solve various problems, which will prevent them from recurring.

I am Mohammad Fahad Usmani, B.E. PMP, PMI-RMP. I have been blogging on project management topics since 2011. To date, thousands of professionals have passed the PMP exam using my resources.

PMP Question Bank

This is the most popular Question Bank for the PMP Exam. To date, it has helped over 10,000 PMP aspirants prepare for the exam. 

PMP Training Program

This is a PMI-approved 35 contact hours training program and it is based on the latest exam content outline applicable in 2024.

Similar Posts

Project Status Reports: Templates & Examples

A project status report is a project management document that details the status of a project. It’s a project reporting tool that outlines the project’s health and provides vital data to project stakeholders such as clients, sponsors, and team members. Project managers communicate the project status to management and key stakeholders through a project status…

How to the Write Scope of Work (Examples & Template Included)

The scope of work (SOW) defines the work that must be carried out to complete the project; hence, creating the SOW document is vital for project success. In today’s article, we will discuss the meaning of the scope of work, its importance, and the step-by-step process of writing SOW. Finally, I will provide a template…

PMP Certification Training in Dallas

In this post, I will provide a few PMP training programs you can join in Dallas. To apply for the PMP exam, you must attend PMP training. This training improves your project management skills and fills knowledge gaps. You can get trained through many methods, such as classroom training, live online training, or an online…

How to Manage Scope Changes in Project Management

The scope can be related to the product features or the project work. Mostly, in traditional project management, the scope is fixed. However, scope changes are common occurrences in project management, and these changes in scope affect other project objectives and baselines. In today’s blog post, we will discuss what qualifies as scope change, its…

PMI-ACP Training: Online PMI-ACP Certification Exam Training Program

If you are preparing for the PMI-ACP certification exam, you must attend the PMI-ACP training program.  You must attend a PMI-ACP training and earn 21 contact hours to apply for the PMI-ACP exam. PMI-ACP stands for PMI-Agile Certified Practitioner, and PMI awards this certification to professionals working with Agile methodologies. Many professionals have asked me…

What is a Key Performance Area (KPA)?

Performance measurement is an integral part of project management that ensures the employees know their responsibilities and roles in completing the project. Key Performance Area (KPA) is the key aspect that affects the project, and the project managers must know Key Performance Areas to emphasize them and complete the project successfully. What Are Key Performance…

Leave a Reply Cancel reply

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

What is the 5 Whys framework?

Table of Contents

Use the 5 whys to transform your problem-solving approach.

The 5 Whys framework is a problem-solving technique used to identify the root cause of a problem . It’s a simple but powerful way to uncover the underlying reasons behind a problem by asking the question “why” repeatedly. By doing so, you can delve beyond the symptoms and surface-level causes of a problem and reach the fundamental cause that is contributing to the issue. And by addressing the root cause, you have a better chance of implementing effective solutions and preventing the problem from recurring.

Dive into the 5 Whys: Origins, basics, and benefits

Let's demystify the 5 Whys and discover:

What is it?

How does it help identify the root cause of problems?

How does it lead to more effective resolutions?

We'll highlight the benefits that it brings to the table after we provide you with the origins.

Origins of the 5 Whys: From Toyota to today

The 5 Whys technique, a cornerstone in the Toyota Production System, was initially employed to zero in on the root cause of manufacturing issues. The ultimate aim of the approach was to eliminate waste, increase efficiency, and improve quality in manufacturing processes.

With applications beyond the realm of manufacturing, many different industries have adopted the 5 Whys technique over time, demonstrating its powerful ability to drill down to the heart of problems.

Potential of the 5 Whys: Benefits and impact

Incorporating the 5 Whys technique into your problem-solving arsenal brings many benefits, including enhanced efficiency and amplified productivity. It also fosters a proactive problem-solving attitude within your team.

Using the 5 Whys approach is especially beneficial as it hones in on the root cause of issue, which helps prevent its recurrence in the future. By taking corrective actions at the source, businesses can avoid repeatedly dealing with the same issue.

Mastering the 5 Whys: Step-by-step guide

Embarking on a 5 Whys journey is akin to mining for gold — digging through layers to unearth the precious nugget — the root cause of your problem.

Here's your step-by-step guide to ensure a successful excavation with the 5 Whys template .

Step 1: State your problem

Your journey with the 5 Whys begins by clearly stating your problem. This crucial first step lays the groundwork for the entire analysis.

Step 2: Ask your first Why?

Now it's time to get to work. With your problem defined, pose your first "Why" question. The question should address the problem you've just stated.

Step 3: Probe deeper with more Whys

Don't stop there! Keep probing with more "Why" questions. Each question should be a response to the previous answer. Per the classic technique, you'll typically ask five times. Remember, the goal is to dig deeper into the root cause.

Step 4: Unearth the root cause

You'll know you've hit the root cause when your "Why" questions no longer produce meaningful responses. More than likely, you’ve found the core issue that, if addressed, will prevent the problem from recurring.

Step 5: Develop and implement your solution

It's time to take action with the root cause in your sights. Develop a solution that tackles the root cause directly rather than just dealing with surface-level symptoms. And remember, the proof is in the pudding. Implement your solution and observe the effects.

5 Whys in action: Real-world applications and examples

To truly appreciate the 5 Whys, you have to see it in action. We'll explore how the 5 Whys technique is used for root cause analysis in UX Design by delving into a detailed example, demonstrating how to navigate user experience challenges.

UX Design case study: Navigating user experience challenges

Let's take a hypothetical scenario where we encounter a UX Design problem that'll benefit from using the 5 Whys method.

Initial problem : Our latest app design needs to improve user navigation.

Application of the 5 Whys method:

Why is navigation difficult? Users need help finding the search function.

Why are users having trouble finding the search function? The search function needs to be more easily visible.

Why isn't the search function easily visual? Because it's located within a menu, not on the main screen.

Why is it placed on a menu? We wanted to keep the main screen uncluttered.

Why'd we want to keep the main screen uncluttered? It'd enhance the user experience.

Solution implemented: We added a prominent search bar on the app's main screen.

Outcome: user complaints about navigational difficulties were reduced by 50%, leading to an increase in app usage and user satisfaction

Software development: Debugging with precision

For developers, the 5 Whys is a powerful tool for debugging. Let's walk through a hypothetical situation where code goes rogue.

Problem statement:

A recently launched app crashes whenever users try to sign up.

Question: Why does the app crash when users try to sign up?

Answer: Because there's an unhandled exception in the sign-up module

Second Why?

Q: Why is there an unhandled exception in the sign-up module?

A: Because it doesn't handle a case where a new user's email is already in the database.

Q: Why doesn't it handle the case where a new user's email is already in the database?

A: Because there's a missing condition, check for duplicate emails in the code.

By identifying and fixing these common missteps and pitfalls, you'll enhance your usage of the 5 Whys technique. This'll lead to precise root cause detection and practical solutions that address the issues.

Amplifying the 5 Whys with Fishbone Diagrams

You can amplify the 5 Whys by pairing it with a fishbone diagram , also known as the Ishikawa Diagram. This combination enhances problem-solving by mapping cause-and-effect relationships, aiding understanding and decision-making in complex projects.

To combine these methodologies, start by creating a fishbone diagram and map the different categories related to the main problem and their potential causes. For each potential cause, use the 5 Whys technique to explore the underlying reasons and identify the root cause for each branch on the diagram. The 5 Whys analysis will help you to challenge assumptions and discover the fundamental reasons driving each cause in a structured manner.

Miro has easy-to-customize fishbone diagram templates that can help you get started.

Perfecting your 5 Whys approach

To fully harness the power of the 5 Whys, it's crucial to adopt best practices and dodge common pitfalls.

Follow these best practices to perfect your use of the 5 Whys:

Be consistent

Consistency in the 5 Whys lies in persistent probing. Don't stop at initial reasons — repeatedly maintain your Why inquiries. This diligent uncovering of layers helps reveal the root cause.

Beware of assumptions

Assumptions can compromise the 5 Whys effectiveness. Stay on path and validate each Why with data. This grounding ensures your conclusions are fact-based, not assumption-driven.

Keep the big picture in mind

It's crucial to zero in on the problem, but don't let this tunnel vision distract you from the broader perspective. Effective solutions shouldn't only tackle the immediate problem, but they should also seamlessly blend with your overarching objectives and strategies.

Discover more

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

What is root cause analysis?

What is a cause and analysis diagram?

Get on board in seconds

Join thousands of teams using Miro to do their best work yet.

• Consultancy
• Online Courses
• 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.

As a parent, I know the feeling in the car when your child in the back seat asks a question. The response I give just does not satisfy their curiosity. They are trying to order a particular bit of information in their brains, and my answer never worked. So they ask “Why?” again.

It does not take long within this cycle of asking “why?” before we all begin to have difficulty to answer. We twist our logic as we try to justify why we said what we said in the first place … “but why?” just keeps on coming and before you know it we end up tongue-tied and just putting our foot down with  “STOP! That’s just how it is! Alright”

• Visit our Consultancy page

Ready to test your business knowledge?

Take our business quiz (5 mins), gb masterclass course, get access to our free gb mastercourse classes, free course previews, 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

“5 Why” remains one of the most straightforward tools to remember, and it’s easy to put into practice. However, the simplicity hides a level of complexity.

Like many of the best and simple tools, they need to be tested and practised to get the best from them.

How to do a 5 Why exercise as a team

One of the key disadvantages of the tool is that teams only follow one avenue of investigation rather than focusing on all the potential causes to identify the real root cause. This is not really an issue with the tool, but the way people implement the tool and rush through things.

Another potential disadvantage is that all too often the teams never get anywhere near 5 Why’s. Once again, an issue with the implementation rather than the tool. Teams quickly get overexcited and stop at 2 or 3 Whys as they have jumped to a solution that looks great.

So always try to get to 5 and be brave and follow every avenue of investigation. And remember, this is processed focused, so try to avoid the trap of seeing people’s capability and training as the single root cause.  If you end up with lots of “more training is required” as a solution, then go back up and try again and see if anything has been missed from a process point of view. Why is the process so hard to follow?

In our experience, any issue or problem can be quickly improved by asking why within a small group. It has helped teams better understand their customers’ needs, and it has helped organizations save thousands of dollars on fixing the wrong thing.

This is a team exercise and asking the why needs to be explorative and not in any form understood as a criticism. So keep the ideas and conversation open with strong ground rules and group facilitation.

For each Why there may be multiple reasons and each of these need to go through a separate set of 5 why discussion. 

You will then need to prioritize the potential root causes either through a Pareto or through a simple voting system initially to understand which ones the team believes need to be investigated first.

Keep in mind that we are focused on processes and not always people. Remember the 94/6 rule – that 94% of the issues come from your process and 6% of the issues from the people. So if you end up with more training as the root cause, take it from me, you have missed something major.

When conducting five why’s, they are never quite as neat as the examples above. Each time you ask why there will rarely be only one reason. You are much more likely to end up with 10 to 15 different potential root causes. As a team, you can then work through the possible root causes and with testing, piloting or perhaps through a simple team vote, begin to prioritize solutions.

The below slide from our  Lean Six Sigma training  deck visually captures how five why’s work in reality.

* A quick footnote on the Washington Monument

Like many real improvement opportunities, the hardest part is change management. And the Washington Monument is not the exception. With the delay in turning on the lights, the side effect was the iconic tourist photographs of the monument at dusk vanished. The complaints started to arrive. Even from the cities inhabitants complaints. 

While a solution had was found to stop the use of heavy cleaning chemicals, this monument was a landmark and symbol of the city. And it was not too long before the lights were back on and the government was looking for a new solution.

Stay current with our latest insights

• Lean Six Sigma Yellow Belt Course

Our Training Courses

Fundamentals of lean.

• Lean Six Sigma White Belt Course
• Lean Thinking Business Course
• Lean Six Sigma Green Belt Course
• Lean Six Sigma Black Belt Course

Yellow Belt Course

View all courses, recent articles, leanscape announces leadership coaching services, unlock business innovation with the lean business model canvas, 2024 recommended reads for transformative thinking, 10 best books on agile, scrum and design thinking, the ultimate guide to lean and manufacturing: boosting efficiency and productivity, 10 best management books for leaders and change makers, view all articles, green belt course, other articles, measles charts: how they’re used and what they mean, dmaic model | the 5 phase dmaic process to problem-solving, why the fmea is a great tool for all project managers, what are the benefits of cpd for lean certifications, the top benefits of lean six sigma training & certification, what is kanban explained in 10 minutes, the vital role of successfully adopting lean in driving operational improvement, delegate decision making to the lowest level possible, time thieves: how time slips away, the benefits of continuous improvement, an overview of the pugh matrix: what is it and how does it work, an introduction to correlation and regression analysis, related articles, maximising efficiency and profitability: exploring the benefits of lean consultancy, is problem solving a skill how to improve your problem-solving skills, customer value – are you creating enough | principles of lean, kaizen vs kaikaku – understanding the difference, principle 1: use long term goals to drive short term decisions, lean six sigma online courses.

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

Lean Accelerator Progam

A Lean Six Sigma Green Belt Masterclass

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

FREE COURSE

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.

Lean Accelerator Program

Discover the power of problem-solving, 15 min per day | 3-months | only €999 | learn from experts.

Guide: 5 Whys

Author: Daniel Croft

Daniel Croft is an experienced continuous improvement manager with a Lean Six Sigma Black Belt and a Bachelor's degree in Business Management. With more than ten years of experience applying his skills across various industries, Daniel specializes in optimizing processes and improving efficiency. His approach combines practical experience with a deep understanding of business fundamentals to drive meaningful change.

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.

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

Hi im Daniel continuous improvement manager with a Black Belt in Lean Six Sigma and over 10 years of real-world experience across a range sectors, I have a passion for optimizing processes and creating a culture of efficiency. I wanted to create Learn Lean Siigma to be a platform dedicated to Lean Six Sigma and process improvement insights and provide all the guides, tools, techniques and templates I looked for in one place as someone new to the world of Lean Six Sigma and Continuous improvement.

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.

Was this helpful?

The Power of the Five Whys: Drilling Down to Effectively Problem-Solve

It’s a fact of life that things don’t always go according to plan. When facing mistakes or challenges, asking “why”—especially if you do it repeatedly—can help uncover deeper layers of understanding so you can identify potential solutions.

The “Five Whys” method (also called “5 Whys Root Cause Analysis”) can specifically help in examining beliefs, behaviors, and patterns to shine a light on areas for improvement. The Five Whys have other benefits too, including encouraging collaboration and communication since this strategy promotes open dialogue among team members or partners. It also helps generate effective and lasting solutions that can prevent similar issues from resurfacing in the future.

What Is the “5 Whys” Method?

The power of asking “why”.

“Effective problem solving can help organizations improve in every area of their business, including product quality, client satisfaction, and finances.” Jamie Birt , Career Coach

When the 5 Whys Should Be Used

“Curiosity has been identified as a characteristic of high-performing salespeople, and having a tool and system that fosters curiosity in your team is extremely helpful.” Alexander Young, Forbes

Any time a problem needs to be clarified and solved, the Five Whys can help. This flexible technique can be adapted to different situations, including personal and professional ones. For example, it’s useful when there are complications within businesses that are causing a loss of profits or when arguments occur among family members or partners. Eric Ries from Harvard Business Review points out that start-ups can especially benefit from the Five Whys to test and refine procedures, ideas, products, and processes.

Here are examples of situations in which the Five Whys can be utilized:

How to Utilize the 5 Whys Technique

“The beauty of the [Five Whys] tool is in its simplicity. Not only is it universally applicable, it also ensures that you don’t move to action straight away without fully considering whether the reason you’ve identified really is the cause of the problem.” Think Design

Follow these steps to implement the Five Whys:

2. Ask “Why?”: Start by asking why the problem occurred. Answer your own question. The answer becomes the basis for the next “why” question.

4. Analyze and Take Action: Once you have identified the root cause, analyze potential solutions and take appropriate action.

To test if the root cause is correct, ask yourself the following: “If you removed this root cause, would this problem be resolved?”

Potential Solutions:

Five Whys Examples

Example 1: machine breakdown, example 2: orders not being fulfilled on time, other ways of improving problem-solving.

“Great leaders are, at their core, great problem-solvers. They take proactive measures to avoid conflicts and address issues when they arise.” Alison Griswold , Business and Economics Writer

Problem-solving is a skill that can be developed and improved over time. The Five Whys method is most effective when used in conjunction with other problem-solving tools and when utilized in a collaborative environment that encourages open communication and a willingness to honestly explore underlying causes. For the method to work well, “radical candor” needs to be utilized, and constructive feedback needs to be accepted.

Want to learn more about problem-solving using critical thinking? Check out this article:

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

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

Teaching Lean Thinking to Kids: A Conversation with Alan Goodman 

Podcast by Alan Goodman and Matthew Savas

Related books

A3 Getting Started Guide

by Lean Enterprise Institute

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

by Eric Ethington and Matt Zayko

Related events

September 26, 2024 | Morgantown, PA or Remond, WA

Building a Lean Operating and Management System 

October 02, 2024 | Coach-Led Online OR In-Person (Oakland University in Rochester, MI)

Explore topics

Subscribe to get the very best of lean thinking delivered right to your inbox

Privacy overview.

• Sign up for free
• SafetyCulture

The 5 Whys: A Powerful Problem-Solving Tool

The 5 Whys can be used for everything from fixing a broken appliance to solving a complex business issue. This article discusses how you actually use it.

What is the 5 Whys Technique?

The 5 Whys is a problem-solving technique used to explore the cause-and-effect relationship that leads to a particular problem. The name derives from the method’s frequent utilization of the question “Why?” This repeating question is used to determine the root cause of a problem by repeating why the problem occurs five times. Each answer forms the basis for the next question.

It’s a simple but powerful technique that can help you get to the bottom of things in a thorough manner. It can be used for anything from figuring out why your car keeps breaking down to understanding why a project is behind schedule. It’s a great way to get clarity and find solutions fast. 

When it comes to problem-solving, the 5 Whys is one of the simplest techniques around. But don’t let its simplicity fool you—it’s a powerful tool that can help you get to the root of any issue. The beauty of the 5 Whys is that it helps you get to the heart of the issue quickly and easily. And it’s a great tool for troubleshooting problems in your business. Here are some of its benefits:

• Identifies the root cause of the problem
• Helps you analyze and understand how one action can cause a chain of problems
• Gets you to the root cause quickly
• Does not use any complicated techniques for problem-solving
• Figures out the relationship between the various root causes
• Is very effective as a solution for simple problems

The 5 Whys technique was developed in the 1930s by Sakichi Toyoda, a mechanic who was always looking for ways to improve the efficiency of his work. He found that the best way to do this was to ask why his processes were failing. He would ask why five times until he got to the root of the problem. Simple as that!

The 5 whys is now a popular problem-solving technique that’s used in businesses all over the world. It’s simple yet amazingly effective at getting to the root of a problem.

How It Works

Let’s say you’ve got a problem. You know what it is, but you’re not sure how to fix it. This is where the 5 Whys come in.

Here’s how it works: you ask yourself why the problem happened, and then you ask yourself that question again and again until you get to the root of the issue.

The key is to ask why five times. Why did the problem happen? Why did the previous solution fail? And so on. This helps you get down to the root cause of the issue and find a solution that will actually work.

This is a great technique when you’re stuck and don’t know how to move forward. It can help you get clarity and come up with a solution that works for you.

Here’s a perfect example:

Digitize the way you Work

Empower your team with SafetyCulture to perform checks, train staff, report issues, and automate tasks with our digital platform.

What are the 5 Whys in Six Sigma?

The 5 whys tools can be used in a variety of situations. It’s used in root cause analysis and Six Sigma to get to the root of a problem.

As we all know, Six Sigma is a process improvement methodology used in various industries to achieve near-perfection in their processes. Within that metholodogy, the 5 whys tool is used specifically for the DMAIC (Define, Measure, Analyze, Improve, and Control) framework.

As a result, it helps Six Sigma practitioners find the root cause of a problem by asking successive “why” questions. 

When to Use this Method

This technique can be used when you’re trying to solve a specific problem understand why something went wrong. It can also be used to come up with new ideas or solutions.

The great thing about the 5 Whys is that it helps you get to the root of the problem, and it also encourages creativity and brainstorming. So if you’re facing a challenging problem, this is a technique you should try.

Limitations

The 5 Whys is a great tool for problem-solving, but it has some limitations. For example, it can be difficult to apply this technique to more complex problems. Aside from this, here are some of the constraints when using this method:

• This method is not recommended for complex problems as it may not lead to the main cause. This is because the 5 whys will lead to a single source, which may be a problem if there is a need for multiple solutions.
• It is reliant on the skills of the team facilitator. One wrong question or answer can lead to completely throwing off the questions, thus leading to a wrong root cause.
• The 5 whys method may not show all possible issues caused by the main problem. 

How to Use the 5 Whys Method

Now that you know all about the 5 Whys method, let’s talk about how to use it. So how do you implement the 5 Whys tool? Here’s a quick and easy guide to get you started:

#1. Gather and Assemble a Team.

The first step is to create a team that is familiar with the problem or issue at hand. Familiarity with the issue is essential because this will determine the right questions to ask thus solving the problem correctly.

#2. Identify the Problem.

Next is to identify the problem at hand. Once you’ve done that, it’s time to discuss it with your team by writing down a brief statement or question of what the agreed issue needs to be solved. A team member can right down the statement while leaving enough space for why questions.

#3. Ask the 5 Whys.

Now is the time to ask the first why. The first question must pertain to why the problem occurred. The question must be based on facts and related to the issue. Keep going until you reach the root cause of the problem.

#4. Brainstorm Solutions to the Root Cause.

Once you’ve identified the root cause, you can start brainstorming solutions. It’s important to remember that not every solution will work, but the goal is to find a solution that will prevent the problem from happening again.

#5. Test the Solution.

So how do you know if the solution is effective? You need to test it. Modify the solution as needed and repeat the test until you’re satisfied that it’s working.

How Can SafetyCulture Help with Using 5 Whys?

The 5 Whys is a great tool for solving problems quickly and easily, and it can be used in situations wherein you need to find the cause of the problem. But how SafetyCulture (formerly iAuditor) can help you with using 5 Whys? 

SafetyCulture is a powerful analytical tool and 5 whys software that can help you quickly and easily identify the root cause of any problem. Plus, the platform’s reporting and dashboard capabilities make it easy to share your findings with your team. Here are some other features that you can utilize when doing 5 whys analysis with SafetyCulture:

• Capture and report issues to gain better visibility and traceability, and get to the root cause using relevant insights and data for continuous improvement .
• Use the Heads Up feature to keep everyone in the loop during 5 Whys meetings. With this feature, you’ll never miss team meetings, ensure all agenda are addressed, and easily collect the additional necessary data to streamline the process.
• Assign actions to team members that are in charge of making sure that the 5 whys analysis progresses and that tasks are properly assigned through building workflows .
• Use various smart checklists and templates that you can customize based on your team’s needs.
• Integrate your tools to assess all kinds of data and monitor analytics in one place.

Featured Templates:

The 5 Whys Template

Can I use 5 Whys in any situation or problem that occur?

Yes and no. The great thing about 5 whys is that it can be used by anyone facing simple problems. However, for complex problems that require detailed solutions, using 5 whys may not be ideal.

Why are there only five "whys"?

The 5 Whys technique is based on the premise that the root cause of a problem can be found by asking why five times. With this method, you can get to the root of the issue and find appropriate solutions.

How do I know when I've reached the root cause?

There is no hard and fast rule for how many times you should ask why before you reach the root cause. However, if you find yourself going in circles or asking the same question multiple times, it’s likely that you haven’t yet reached the root cause.

How do you document 5 Whys?

There are various ways to document 5 whys. One way is to use a cause and effect diagram, also known as an Ishikawa diagram or fishbone diagram. This type of diagram can be used to brainstorm the possible causes of a problem. Another way to document 5 whys is to simply write down the question and answer for each step.

SafetyCulture Content Team

Related articles

• SOP Examples

Learn how SOPs are used in various industries and examples of how to write them comprehensively

• Find out more

• Construction Site Management

Learn about construction site management and its importance in project success.

• Disaster Recovery Planning

Safeguard all aspects of your business by developing and implementing an effective disaster recovery plan.

Related pages

• Induction Software
• Construction Collaboration Software
• Workforce Optimization Software
• Care Management Software
• Visitor Management Software
• Construction Project Management
• Product Launch
• NDIS Audit Checklist
• Change Impact Assessment Template
• Environmental Aspects and Impacts Register
• 5 Whys Template
• Agile Transformation Checklist

• Your Project
• 5 Whys Method

What is the Five Whys method?

The “ 5 Whys ” is a Problem-Solving method that identifies Root Causes of Problems by asking five consecutive times:

• “Why this happened?”.

It Starts with the most obvious “Symptom” (or Issue) and Forces the analyst to wonder Why it happened .

• Once the Analyst has a first Explanation, he/she has to repeat this cycle 4 more times.

5 Whys method Flowchart

Let’s see it with one example:

Five Whys example

Imagine that one day, your front-right tire suddenly bursts .

As we all would do, you call your car assistance company, that comes exactly where you are and replace it with a new tire.

Few weeks later, again, this same tire (the new one) bursts again .

And you start thinking that this is not normal (or shouldn’t be).

Then, you decide to apply the 5 Why methodology :

1. Why this happened?

• Why your tire burst in the first place?

You bring your car to the car shop.

There, they tell you that your rims are not aligned and that is causing your tires to burst.

Many people would settle for this explanation but you then, ask yourself again:

2. Why this happened?

• Why weren’t they aligned?

Your car is only 2 years old so, it shouldn’t be usual.

Your car assistant tells you this can happen if case you park on irregular terrain frequently .

You do it, but just once a month. It shouldn’t be enough.

3. Why this happens?

• Why parking once a month on irregular terrain misalign your wheels?

You decide to investigate about it, and you find out that you have a loose master screw that is causing this problem .

4. But how is this possible?

• Why is this screw loose? Is it a car problem?

You ask different same-car owners and you find out that this is only happening to you , so you start to suspect that in your last car revision somebody caused this problem.

You then ask in your car shop about what they did in your last revision and they confirm that they “manipulated” that piece .

5. Then, how is it possible that they forgot a loose screw?

• Should you take your car to another shop? Why this happened?

In the workshop, they confess that the last revision of your car, was developed by an external worker since the main mechanic was sick .

They assure you they won’t hire that external worker again since he didn’t know what he was doing.

• Moreover, they will give your money back (what you had to pay for your tires and the alignment).

Summarizing:

Imagine now, what would have happened if you had settled for the first explanation they gave you .

• You would have stopped parking on uneven terrains, but you would still have the problem.

We are not car-mechanic experts, so forgive us if we said something stupid.

We just wanted you to understand how the “five Whys” tool works.

Why is the 5 Whys method important?

By nature, we all tend to settle for the first explanation we have.

The 5 Whys method pushes you to see beyond and find the “root cause” of your problem.

But, can you always apply this method?

When can be used the 5 Whys method?

Whenever you need to find the root cause of a certain problem .

• Which Plugins may cause it and why?
• Which employee could do better and why?
• You can even use to improve your diet and find out why you are gaining weight!

Although it was originally designed for Industrial quality processes (where it is extremely useful) it can be used in practically all situations .

How should you develop a Five Whys analysis?

According to our experience, the simpler the better .

There are dozens of Flowcharts with crossed explanations, difficult algorithms…

We propose you to use the simplest approach possible.

It is better to use a simple yet useful approach instead of a difficult one that you would only use once.

What do you need for applying the 5 Whys method?

Some people recommend assembling a Team, but we don’t think that is necessary.

• If you develop this method at your Job you can do it without any problem.

You only need to feel like finding the Root Cause of your Problem .

Should you always find 5 Whys?

Sometimes, with just 3 “Whys” is enoug h .

• You should try to dig as deep as you can, but sometimes you get to “bedrock” with less than 5 Whys.

5 Whys Method Examples

Now, we’ll propose you two examples of different situations in which this method can be very useful.

Let’s begin:

YouTube Channel - 5 Whys Method Example

Let’s imagine you own a YouTube channel :

• You have been publishing new videos for a whole year on regular basis.
• Your videos have a higher than average quality (regarding image, sound, etc).
• All the people you’ve asked tell you that your videos are funny.

However, you just have half the audience of other similar channels .

1. Why do you have half the audience of your competitors?

Assuming you have approximately the same videos published; the obvious answer is this:

• YouTube is not showing your content as often as that of your competitors.

This statement is not as obvious as it may seem.

If your content is good, and you have “plenty” of it…

2. Why is YouTube not showing your content as often as that of your competitors?

If YouTube is not showing your content as much as you would like, must be because some of your metrics are not as good as you expected:

You then discover that:

• Your “Engagement” is not very high.
• Your “Audience retention” is limited.
• The “Average percentage viewed” is reduced.
• On the other hand, your “Click-Through rate” is elevated.

Some users devour your videos, but others just move on .

So far, you have concluded that:

• Your YouTube Title descriptions are better than average.
• Some of your users love your videos.
• Others don’t.

And this last fact is preventing your content from being better positioned.

3. Why some of your users don’t like your content?

You decide to investigate the average profile of your users:

• Where they come from.
• What they are interested about.

After a deep research, you conclude that users of your same country are much more engaged than those from other countries .

4. Why the users from your same country are much more engaged?

You start to look at your YouTube comments in order to figure out what is going on.

You find 3 different kinds of comments:

• Stupid meaningless comments.
• You suspect they are from your same country.
• Comments requesting for some explanations; they didn’t understand your video at all.

The people from your same country understood perfectly your content:

• Your Jokes.
• The references you made.
• The people you referred to.

While people from other countries, didn’t understood everything you said .

5. Why people from other countries don’t fully understand your videos?

So far, we have that:

• Your videos don’t have as good metrics as you thought and that is why YouTube is not showing your content as much as that of your competitors.
• Some of your users are very engaged while others are not.
• Those Engaged users are from your same country.
• They like your videos because it seems that they are the only ones that understand perfectly everything you say; your jokes, your references, etc…

And the reason some users don’t understand your videos is:

• You are publishing videos with local references for a global audience.

People from other countries don’t understand your jokes because what you think is very popular all over the world, is popular only in your country .

• That is why your publications don’t have as good metrics as they could.

Now, you’ll start introducing new and more international references in your videos.

We are not YouTube experts so please, forgive us if we said something wrong.

Since lots of our users are very interested in SEO, we’ll show a similar example, but focused on a Website:

Improving SEO - 5 Whys Method Example

Let’s imagine that you own a WordPress Site .

You have been writing interesting and high-quality content for a whole year.

• You have already published 60 interesting articles.

However, you barely have 1,000 pageviews per month . What is going on?

Let’s develop a “condensed” 5 Whys method:

1. Why you only have 1,000 pageviews per month?

Because your content isn’t Rankings very good .

2. Why is your content Ranking so poorly?

Because your metrics are terrible:

• You have a 0.3% CTR.

People do not Click on your content .

3. Why people don’t Click through your content?

You decide to look for some of your pages on Google and you find out that your Publications’ titles are not attractive at all .

While your competitors have nice Titles and Descriptions, your Posts have short boring titles.

4. Why do your Posts have boring Titles?

Because you didn’t know that you could edit them .

With this “5 Whys analysis” you found out that it is very important to edit your publications’ titles, so they are more attractive to your potential users .

Your content may be the best, but if it has a generic boring Title, nobody will Click through it.

* Believe or not, this is based on a true story.

Summarizing

The 5 Whys method is a simple iterative analysis that pushes you to find the root cause of your problems by asking yourself 5 consecutive times: Why this happens?

• Sometimes you’ll need less than 5 Whys, and other times 5 won’t be enough.

Although there are different approaches for developing a “5 Whys analysis”, the simpler the better .

Never underestimate this method : You have surely settled for the first explanation you’ve encountered several times without discovering the true root cause of your problem .

• Economies of Scale
• Business Plan for Beginners
• Business Plan Basics
• How to write a Business Plan
• Cash Flow Calculation
• Raising Funds for a Business
• 4 C’s of Credit
• Business Plan Templates
• Customer Insight
• Customer Experience
• Customer Pain Points
• 4C Marketing Model
• RATER Model
• Augmented Product
• Product Mix
• Unique Selling Proposition
• DAGMAR Model
• Marketing Storytelling
• Content Marketing
• Psychographics
• Barnum Effect
• Market Segmentation
• Market Research & Big Data
• Marketing to Generation Z
• 4P Marketing Mix
• 7P Marketing Mix
• Sales Funnel
• Loyalty Ladder
• RACE Planning
• Push and Pull Marketing
• Marketing Strategy
• Marketing Templates
• Starting your own business
• From Startup to a Business
• Entrepreneur FAQs
• Start your Business Idea
• Entrepreneur Golden Rules
• Innovate or Imitate?
• Design Thinking
• SCAMPER Model
• AAR Process
• Work From Home
• Growth strategies for Startups
• VMOST Analysis
• 3P Framework
• SOAR Analysis
• TELOS Analysis
• 5 C’s of Entrepreneurship
• Crowdfunding
• BATNA & ZOPA Negotiation
• Entrepreneur with no Money
• Entrepreneurship Templates
• Strategy vs Tactics
• Mission and Vision
• Business Values
• Value Chain
• Scenario Planning
• Porter 6 Forces
• Bowman’s Strategy Clock
• GE-McKinsey Matrix
• Delta Model
• PEST Analysis
• PESTEL Analysis
• SWOT Analysis
• VRIO Framework
• Strategy Canvas
• Competitive Advantages
• Porter’s Four Corners
• 5 Ps of Strategy
• Porter’s Generic Strategies
• Porter’s Diamond Model
• Wardley Map
• Core Competencies
• Resource Based View
• Bridges Transition Model
• CAGE Distance Framework
• McKinsey’s 3 Horizons
• Vertical Integration
• Horizontal Integration
• Blue Ocean Strategy
• Red Ocean Strategy
• Porter 5 Forces
• Ansoff Matrix
• McKinsey 7S Framework
• CATWOE Analysis
• Strategy Pyramid
• Bain’s RAPID Framework
• Balanced Scorecard
• Resources and Capabilities
• Strategy of Apple
• Strategy of Amazon
• Strategy of Starbucks
• Strategy Templates
• Communicate Effectively
• COIN Conversation Model
• SCARF Model
• SBI Feedback Model
• CEDAR Feedback Model
• How to behave at a meeting
• Gibbs’ Reflective Cycle
• Bloom’s Taxonomy
• 5E Learning Model
• 9-Box Performance Grid
• SEEDS Bias Model
• Halo Effect
• Pygmalion Rosenthal Effect
• Dunning-Kruger Effect
• How to be an Entrepreneur
• How to be a Leader
• Mintzberg Managerial Roles
• Cog’s Ladder
• The Peter Principle
• How to Negotiate
• Teamwork Skills and Profiles
• Gantt Chart
• RACI Matrix
• Eisenhower Matrix
• MoSCoW Method
• FMEA Process
• Problem Solving
• Ishikawa Fishbone diagram
• 8 Disciplines Method
• ADDIE Model
• ORAPAPA Method
• Cynefin Framework
• Just In Time
• SMART Goals
• KISS Principle
• Birkinshaw’s 4 Dimensions
• Parkinson’s Law
• OGSM Framework
• OKR Methodology
• APQP Framework
• Theory of Constraints
• Success through Organization
• ADKAR Model
• Lewin’s Change Model
• Kotter’s 8-Step Model
• The Greiner Curve
• GAP Analysis
• Planning Templates
• Mean, Median and Mode
• Define your Data
• Pareto Principle 80/20 Rule
• Decision Matrix
• Decision Tree
• TARA Framework
• Root Cause Analysis
• Simplex Process
• Forecasting Methods
• Product Life Cycle
• How to use Google Trends
• Correlation vs Causation

© 2024 - Consuunt .

We're not around right now. But you can send us an email and we'll get back to you, asap.

Log in with your credentials

Forgot your details.

• Creative & Design
• See all teams

For industries

• Manufacturing
• Professional Services
• Consumer Goods
• Financial Services
• See all industries
• Resource Management
• Project Management
• Workflow Management
• Task Management
• See all use cases

Explore Wrike

• Book a Demo
• Take a Product Tour
• ROI Calculator
• Customer Stories
• Start with Templates
• Gantt Charts
• Custom Item Types
• Project Resource Planning
• Project Views
• Kanban Boards
• Dynamic Request Forms
• Cross-Tagging
• See all features
• Integrations
• Mobile & Desktop Apps
• Resource Hub
• Educational Guides

Upskill and Connect

• Training & Certifications
• Help Center
• Wrike's Community
• Premium Support Packages
• Wrike Professional Services

Explore Wrike for Enterprise

• Enterprise Overview
• Enterprise Customers
• Enterprise Features

Introducing the 5 Whys Technique of Problem Solving

February 3, 2021 - 7 min read

What do you do when you and your team run into a problem?

Do you try to find the quickest fix to keep things moving? Get through and assume it was a fluke that won’t happen again? Shift blame to circumstances that were beyond your control?

There’s a better way to diagnose and even solve your problems. It’s called the five whys. 

What is the five whys method?

The five whys method is a problem-solving technique that helps you get to the root cause of a problem. Using this technique, you’ll uncover cause and effect relationships and ultimately uncover how processes and projects can be improved in the future.

The premise of the five whys is fairly straightforward: You’ll ask “why?” five times in a row. 

Maybe your team didn’t complete a major project by the deadline. Why? Because a team member was late submitting their piece of the project. Why? Because the end client was delayed in getting her the feedback she needed. Why? ...and so on. 

Sound like overkill? Or maybe something a curious toddler would do? We get it. However, this technique is surprisingly beneficial. 

When you and your team are brainstorming or problem-solving, it’s tempting to jump right into identifying solutions — without realizing you don’t quite understand the extent of the problem yet. The five whys technique keeps you and your team zoned in on the challenge so you can identify the most impactful solution. 

A five whys analysis is helpful for understanding the inner workings of problems, but it’s not without its flaws. Let’s cover a few pros and cons of this approach. 

Benefits of the five whys method

• It’s simple to use : As far as problem-solving tools and analyses go, the five whys technique is one of the most straightforward and intuitive.
• It uncovers the root cause : It pushes teams to go beyond their gut feeling or their first answer to think critically about the real source of their issues.
• It encourages conversation : “Why?” is an open-ended question , which can encourage candid and valuable discussions between your team members. It can also expose them to roadblocks or areas of confusion they didn’t realize others were experiencing. 

Challenges of the five whys method 

• It’s subjective : One team member might think your project was delayed because a colleague dropped the ball, while another thinks it’s because the original deadline was unrealistic. Conflicting opinions are common, which can present some roadblocks for the effectiveness of this technique. 
• It’s limiting : Despite the name, you might need to ask “why?” more than five times to get to the heart of a problem. Additionally, there may be more than one root cause for an issue, which this technique doesn’t easily address or accommodate. 
• It requires visibility : Your team is smart, but they don’t know everything. When asking “why?” you might run into some instances where the only answer you can come up with is, “I don’t know.” That means this technique is at a standstill. 

Why does the five whys technique benefit project management?

Ask yourself this: When’s the last time you had a project go off without a hitch? Everything went exactly according to plan, and you didn’t experience a single hiccup along the way.

Has it been a while? That’s normal. Collaboration is complicated, and even the most successful project managers will admit that even the most carefully-planned projects sometimes run off course. In one report from the Project Management Institute ( PMI ), respondents said that only 69% of their project s met their original goals—implying that 31% of projects fell short. 

When that happens, it’s tempting to grit your teeth, get through the muck, and then move on. However, the best thing to do is to reflect on those project problems , drill down to their root causes, and identify how you can fix those for future projects. 

That’s why the five whys technique is important for project management: It will help you and your project team identify how you can collaborate more effectively, proactively navigate risks and problems, and deliver more winning projects. 

The five whys example: How it applies to project management 

Want to see a five whys analysis in action? Let’s continue with the example that we set up at the beginning: 

The Problem: Our team was two weeks late in finalizing a client’s keyword research report.

• Why? Maggie was late in delivering the section on keyword opportunities.
• Why? The end client took too long to get the audience personas she requested.
• Why? We didn’t get the information we needed at the start of the project.
• Why? We don’t have a streamlined process for collecting the client information we need.
• Why? We haven’t created a work intake form. 

Now you know what you need to do to ensure you don’t hit the same snag on your next projects: You need to create an intake form so that your team is equipped with the must-have information they need from your clients — before they even start any work. 

See how it works? By doing nothing more than asking, “Why?” five times in a row, you identified a relatively simple fix (particularly if you’re using a project management platform like Wrike that has dynamic request forms ) that will yield huge results for your team and your projects. 

And you owe all of that to the five whys technique—proof that problem-solving methods don’t need to be complicated to be effective. 

Wrike gives you and your team visibility into your work processes so that you have an easier time leveraging the five whys method. Start your two-week free trial now .

Kat Boogaard

Kat is a Midwest-based contributing writer. She covers topics related to careers, self-development, and the freelance life. She is also a columnist for Inc., writes for The Muse, is Career Editor for The Everygirl, and a contributor all over the web.

Related articles

The Ultimate Guide to Sprint Retrospectives

Plan your next sprint retrospective with these tips and best practices. Use this guide to enable your Scrum team to look back and optimize processes.

The Ultimate Guide to Implementation Plans

Achieve better outcomes and stronger results by creating implementation plans that help you turn concepts into real world action. Learn more with Wrike.

What Is a Bottleneck in Project Management?

What is a bottleneck in project management? Here’s how to perform a bottleneck analysis to identify project roadblocks before they spiral out of control.

Get weekly updates in your inbox!

You are now subscribed to wrike news and updates.

Let us know what marketing emails you are interested in by updating your email preferences here .

Sorry, this content is unavailable due to your privacy settings. To view this content, click the “Cookie Preferences” button and accept Advertising Cookies there.

Module 5: Thinking and Analysis

Problem-solving with critical thinking, learning outcomes.

• Describe how critical thinking skills can be used in problem-solving

Most of us face problems that we must solve every day. While some problems are more complex than others, we can apply critical thinking skills to every problem by asking questions like, what information am I missing? Why and how is it important? What are the contributing factors that lead to the problem? What resources are available to solve the problem? These questions are just the start of being able to think of innovative and effective solutions. Read through the following critical thinking, problem-solving process to identify steps you are already familiar with as well as opportunities to build a more critical approach to solving problems.

Problem-Solving Process

Step 1: define the problem.

Albert Einstein once said, “If I had an hour to solve a problem, I’d spend 55 minutes thinking about the problem and five minutes thinking about solutions.”

Often, when we first hear of or learn about a problem, we do not have all the information. If we immediately try to find a solution without having a thorough understanding of the problem, then we may only be solving a part of the problem.  This is called a “band-aid fix,” or when a symptom is addressed, but not the actual problem. While these band-aid fixes may provide temporary relief, if the actual problem is not addressed soon, then the problem will continue and likely get worse. Therefore, the first step when using critical thinking to solve problems is to identify the problem. The goal during this step is to gather enough research to determine how widespread the problem is, its nature, and its importance.

Step 2: Analyze the Causes

This step is used to uncover assumptions and underlying problems that are at the root of the problem. This step is important since you will need to ensure that whatever solution is chosen addresses the actual cause, or causes, of the problem.

Asking “why” questions to uncover root causes

A common way to uncover root causes is by asking why questions. When we are given an answer to a why question, we will often need to question that answer itself. Thus the process of asking “why” is an  iterative process —meaning that it is a process that we can repeatedly apply. When we stop asking why questions depends on what information we need and that can differ depending on what the goals are. For a better understanding, see the example below:

Problem: The lamp does not turn on.

• Why doesn’t the lamp turn on? The fuse is blown.
• Why is the fuse blown? There was overloaded circuit.
• Why was the circuit overloaded? The hair dryer was on.

If one is simply a homeowner or tenant, then it might be enough to simply know that if the hair dryer is on, the circuit will overload and turn off.  However, one can always ask further why questions, depending on what the goal is. For example, suppose someone wants to know if all hair dryers overload circuits or just this one. We might continue thus:

• Why did this hair dryer overload the circuit? Because hair dryers in general require a lot of electricity.

But now suppose we are an electrical engineer and are interested in designing a more environmentally friendly hair dryer. In that case, we might ask further:

• Why do hair dryers require so much energy?

As you can see from this example, what counts as a root cause depends on context and interests. The homeowner will not necessarily be interested in asking the further why questions whereas others might be.

Step 3: Generate Solutions

The goal of this step is to generate as many solutions as possible. In order to do so, brainstorm as many ideas as possible, no matter how outrageous or ineffective the idea might seem at the time. During your brainstorming session, it is important to generate solutions freely without editing or evaluating any of the ideas. The more solutions that you can generate, the more innovative and effective your ultimate solution might become upon later review.

You might find that setting a timer for fifteen to thirty minutes will help you to creatively push past the point when you think you are done. Another method might be to set a target for how many ideas you will generate. You might also consider using categories to trigger ideas. If you are brainstorming with a group, consider brainstorming individually for a while and then also brainstorming together as ideas can build from one idea to the next.

Step 4: Select a Solution

Once the brainstorming session is complete, then it is time to evaluate the solutions and select the more effective one.  Here you will consider how each solution will address the causes determined in step 2. It is also helpful to develop the criteria you will use when evaluating each solution, for instance, cost, time, difficulty level, resources needed, etc. Once your criteria for evaluation is established, then consider ranking each criterion by importance since some solutions might meet all criteria, but not to equally effective degrees.

In addition to evaluating by criteria, ensure that you consider possibilities and consequences of all serious contenders to address any drawbacks to a solution. Lastly, ensure that the solutions are actually feasible.

Step 6: Put Solution into Action

While many problem-solving models stop at simply selecting a solution, in order to actually solve a problem, the solution must be put into action. Here, you take responsibility to create, communicate, and execute the plan with detailed organizational logistics by addressing who will be responsible for what, when, and how.

Step 7: Evaluate progress

The final step when employing critical thinking to problem-solving is to evaluate the progress of the solution. Since critical thinking demands open-mindedness, analysis, and a willingness to change one’s mind, it is important to monitor how well the solution has actually solved the problem in order to determine if any course correction is needed.

While we solve problems every day, following the process to apply more critical thinking approaches in each step by considering what information might be missing; analyzing the problem and causes; remaining open-minded while brainstorming solutions; and providing criteria for, evaluating, and monitoring solutions can help you to become a better problem-solver and strengthen your critical thinking skills.

iterative process: one that can be repeatedly applied

• Problem solving. Authored by : Anne Fleischer. Provided by : Lumen Learning. License : CC BY: Attribution
• College Success. Authored by : Matthew Van Cleave. Provided by : Lumen Learning. License : CC BY: Attribution
• wocintech stock - 178. Authored by : WOCinTech Chat. Located at : https://flic.kr/p/FiGVWt . License : CC BY-SA: Attribution-ShareAlike
• Five whys. Provided by : Wikipedia. Located at : https://en.wikipedia.org/wiki/Five_whys . License : CC BY-SA: Attribution-ShareAlike