The 5 Whys Method in Project Management

How to Find the Real Causes of Problems

A milestone isn’t met, a work package takes significantly longer than planned, or the same errors keep cropping up. In many projects, people react quickly in such situations. Additional meetings are scheduled, tasks are reprioritized, or more resources are allocated. The problem seems to be solved at first, but resurfaces shortly thereafter.
To break this vicious cycle, it makes sense not only to address the symptoms but also to identify the root cause of the problems. The 5-Why method can be used for this purpose. It is easy to apply, requires no special software, and is suitable for both experienced project managers and teams looking to improve their problem-solving skills.

What is the 5 Whys method?

The 5 Whys method is a technique for root cause analysis. It was originally developed by Taiichi Ohno, the founder of the Toyota Production System. Today, it is an integral part of many lean and quality management approaches, as it enables the systematic identification of structural weaknesses and their sustainable improvement.
The principle is very simple: Starting with a specific problem, you repeatedly ask “Why?” Each answer forms the basis for the next question. In this way, you work your way step by step toward the actual root cause of a problem.
The number five is not set in stone. Some problems can be resolved after just three questions, while others require seven or more “Why” questions to truly get to the heart of the matter. What matters, then, is not the number of questions, but that you ultimately identify a root cause that you can resolve in a sustainable way.

Why is the 5 Whys method so helpful in project management?

Project problems often have complex causes that aren’t apparent at first glance. A delay is rarely due solely to a team member working too slowly. Often, the reasons run deeper—such as unclear requirements, a lack of decisions, or inadequate coordination processes.
The 5 Whys method helps project managers and their teams uncover these underlying connections so they can address them effectively.

Typical benefits include:

• Sustainable problem-solving instead of treating the symptoms.
• Recurring problems are permanently resolved.
• Decisions are based on facts rather than assumptions.
• Teams develop a shared understanding of the causes.
• Managers identify structural weaknesses.
• Resources are used in a more targeted manner.
• Greater transparency regarding project processes.
• Continuous improvement of processes.

This method is particularly valuable for managers because it prevents them from rushing to address symptoms. Only those who know the root cause can take effective countermeasures.

How the 5 Whys Method Works

Step 1: Clearly define the problem

Describe the problem as specifically as possible. It is important to be precise so that everyone involved is working from the same understanding of the facts.
Instead of: “The project isn’t going well.”
Better: “The milestone for approving the specifications was missed by two weeks.”

Step 2: Ask the first “Why?”

Ask why the problem occurred.
Example: Why was the milestone missed?
Answer: Because the requirements were not agreed upon in a timely manner.

Step 3: Derive additional “Why?” questions

Reexamine each answer to get to the root cause of the problem.
Example: Why weren't the requirements coordinated in a timely manner?
Answer: Because key stakeholders were brought on board too late.

Step 4: Identify the root cause

Continue using this questioning technique until you identify a cause that can be meaningfully addressed. What matters is not the number of questions, but whether the actual cause has been identified. A good rule of thumb is to keep asking questions until additional questions no longer yield new insights.

Step 5: Define Measures

Define specific steps to permanently eliminate the identified cause.

Example of the 5 Whys Method

Problem: The planned milestone was not met on time.
1. Why was the milestone not met?
Because the requirements were not approved in time.
2. Why were the requirements not approved in time?
Because the business unit submitted change requests late.
3. Why were the change requests submitted so late?
Because no binding review deadlines were scheduled.
4. Why were there no binding review deadlines?
Because no clear approval process was defined in the project plan.
5. Why wasn’t an approval process defined?
Because the importance of formal coordination at the start of the project was underestimated.
Root cause: Lack of a defined approval process.
Action: In the future, binding review and approval deadlines will be included in project planning.

When is the 5 Whys method appropriate?

This method is particularly helpful when you want to analyze recurring or unexpected problems, such as:

• Delays
• Budget overruns
• Quality defects
• Communication Problems
• Resource constraints
• Recurring errors

For highly complex problems with many influencing factors, it may be helpful to combine this method with other tools, such as the Ishikawa diagram.

Tips for Successful Use

• Look for causes, not culprits: This approach works well only when discussions are open and objective. The goal is not to assign blame, but to improve processes.
• Verify Answers with Facts: Not every plausible answer is automatically correct. Therefore, verify statements using data, documents, or empirical evidence.
• Incorporate multiple perspectives: Include different roles and departments in the analysis. This will help you avoid blind spots.
• Consistently implement measures: Even the best root-cause analysis is of little use if it does not lead to concrete improvements.

Advantages of the 5 Whys Method

• Quick and easy to use
• No special training required
• Promotes analytical thinking
• Supports continuous improvement
• Helps resolve recurring problems in a sustainable way

Limits of the method

Despite its simplicity, the 5 Whys method is not a panacea, particularly because the quality of the results depends heavily on the answers, and different people may arrive at completely different causes. It is also important to corroborate the results with facts, project data, or documentation to avoid misinterpretations. The main criticism, however, is that while the method is well-suited for clearly defined problems, operational errors, or isolated process disruptions, a linear questioning technique is sometimes simply insufficient for complex issues or situations involving many interdependencies.
This is because the method’s linear structure suggests that there is exactly one cause for every problem. In practice, however, this is rarely the case. In project management in particular, problems often arise from multiple factors that influence one another.
Let’s take a schedule delay as an example: Why wasn’t the milestone reached?
Possible answers:

• Requirements were released late.
• A key resource was sick.
• There were technical problems at a supplier.

There are already three lines of causation here. If one were to pursue only one of them, important insights might be overlooked.
That is why, in practice, the method is often applied with a degree of flexibility, and multiple "why" chains are pursued in parallel.

Example:
Cause 1: Requirements were approved late.
→ Why?
→ Why?
→ Why?
Cause 2: A key resource was sick.
→ Why was that a problem?
→ Why wasn’t there a substitute?
→ Why wasn’t a substitute scheduled?
Cause 3: Technical problems at the supplier.
→ Why?
→ Why?
→ Why?
In the end, you end up with several root causes instead of just one. Experienced project managers often compile these chains of causes into a cause tree, thereby approaching the principle of the Ishikawa diagram. Therefore, in complex situations, it can be useful to combine both methods

Conclusion

The 5 Whys method is a simple yet highly effective technique for systematically getting to the root of problems in project management. Instead of treating symptoms, it helps identify the actual causes, thereby laying the foundation for sustainable improvements. For managers in particular, the method is a pragmatic and valuable tool for making well-informed decisions and permanently eliminating recurring problems.

Find out more about the myPARM project and portfolio management software:

FAQ