What is 5 Whys? A Practical Guide to Root Cause Analysis

Problems rarely happen for just one reason.

A patient falls despite a completed risk assessment. A discharge is delayed. A medication error occurs. A patient complains about poor communication. On the surface, each incident appears to have an obvious explanation.

But lasting improvement depends on looking beyond the immediate problem.

If improvement teams only address what happened, they risk seeing the same issue happen again. Sustainable improvement requires understanding why it happened in the first place.

The 5 Whys framework is one of the simplest and most widely used techniques for doing exactly that.

By repeatedly asking “Why?” in a structured way, teams move beyond symptoms, uncover the underlying causes of a problem, and identify improvements that reduce the likelihood of recurrence.

What Is 5 Whys?

5 Whys is a root cause analysis technique that helps teams explore the chain of events and contributing factors behind a problem.

Rather than accepting the first explanation, the team repeatedly asks “Why?”, using each answer to inform the next question.

The objective is not simply to ask five questions. The objective is to continue exploring until the team reaches an evidence-based cause that can be addressed through improvement.

The technique originated within the Toyota Production System and has since become one of the most widely used methods in Lean, quality improvement, operational excellence and patient safety.

Its strength lies in its simplicity. 5 Whys requires no specialist statistical knowledge or complex analysis techniques, yet it helps teams uncover process weaknesses that might otherwise remain hidden.

Perhaps most importantly, it encourages teams to remain curious. Instead of accepting the first explanation, it challenges them to keep asking questions until they understand how the system contributed to the problem.

When Should You Use 5 Whys?

5 Whys works best when investigating a clearly defined problem that has already occurred and where the objective is to understand why it happened.

Common healthcare examples include:

• Patient falls
• Medication errors
• Delayed discharges
• Missed appointments
• Documentation errors
• Delays in treatment
• Patient complaints
• Equipment availability issues
• Delays in diagnostic testing

The method is particularly valuable when the team needs to understand the underlying process failures behind an operational or quality issue.

It is equally useful for clinical and non-clinical improvement work because the emphasis is always on understanding how systems, processes and ways of working contributed to the outcome.

Used well, 5 Whys helps teams move beyond reacting to incidents and towards preventing them from happening again.

When Should You Not Use 5 Whys?

Although 5 Whys is a powerful technique, it is not the right tool for every investigation.

Some problems are relatively straightforward and have a single dominant causal pathway. Others are highly complex, involving multiple interacting systems, human factors, environmental conditions and organisational influences.

For example, investigations involving serious patient safety incidents may require a more comprehensive Root Cause Analysis process using multiple investigative techniques.

Similarly, if the team does not yet understand where the problem is occurring or which issue deserves attention first, it may be more appropriate to begin with other improvement tools before asking “Why?”.

For example:

• A Pareto Chart can help identify which problems or causes deserve investigation.
• A Process Map can help understand where failures occur within a workflow.
• A Fishbone Diagram can help generate a broad range of possible contributing factors.

5 Whys is most effective once the team has identified a specific problem or causal pathway that they want to explore in greater depth.

What Is the Difference Between 5 Whys and Root Cause Analysis?

One of the most common misconceptions is that the 5 Whys is Root Cause Analysis. It isn’t.

Root Cause Analysis (RCA) is the overall process of investigating why a problem occurred so that it can be prevented from happening again. 5 Whys is one technique used within that broader process.

Think of Root Cause Analysis as the investigation, and 5 Whys as one of the tools the investigation uses.

Depending on the complexity of the problem, teams may also use process maps, Fishbone Diagrams, Pareto Charts, timelines, interviews, observations and data analysis alongside 5 Whys.

Understanding this distinction helps teams choose the right combination of methods rather than expecting a single tool to answer every question.

How 5 Whys Fits into Root Cause Analysis

Experienced improvement teams rarely rely on a single tool. Instead, they combine complementary methods, with each helping answer a different question about the problem they are trying to solve.

A typical investigation might look like this:

Rather than competing with one another, these tools work together. A Pareto Chart helps teams prioritise where to focus. A Process Map helps them understand how work flows through the system. A Fishbone Diagram encourages broader thinking about all the possible causes of the problem. The 5 Whys then explores one of those causal pathways in greater depth, helping the team understand why it exists. Finally, Driver Diagrams and PDSA cycles help turn that understanding into practical improvements that can be tested, refined and implemented.

Viewed this way, 5 Whys is not an isolated exercise. It is one important step within a structured improvement journey that moves from understanding a problem to delivering sustainable change.

How to Perform a 5 Whys Analysis

The method is deliberately simple, but effective investigations depend on asking thoughtful questions, involving the right people and basing conclusions on evidence rather than assumptions.

Step 1: Clearly Define the Problem

Begin with a concise problem statement that everyone agrees accurately describes the issue being investigated.

For example: Patients are waiting longer than expected for discharge because discharge medication is not ready.

A clearly defined problem keeps the investigation focused and helps prevent the discussion drifting towards unrelated issues.

Step 2: Ask the First “Why?”

Ask why the problem occurred.

The first answer often describes an immediate cause rather than the underlying issue.

Support answers with evidence wherever possible rather than relying on memory or opinion.

Step 3: Continue Exploring

Use each answer to ask the next “Why?”.

Each question should build logically on the previous answer, gradually revealing how processes, systems or ways of working contributed to the problem.

The conversation should remain focused on understanding the system rather than identifying individuals to blame.

Step 4: Continue Until You Reach an Actionable Cause

Despite its name, the investigation does not always require exactly five questions. Sometimes the underlying cause becomes clear after three questions. Sometimes it takes seven or eight.

The investigation should continue until the team identifies a cause that it can realistically address through improvement work. At this point, asking another “Why?” is unlikely to produce additional insight.

Step 5: Turn Insight into Improvement

Understanding the root cause is not the end of the investigation. The learning should now inform change ideas, improvement planning and testing.

Whether the team develops a Driver Diagram, tests changes through PDSA cycles or redesigns a process, the purpose of the 5 Whys is to ensure those improvements address the underlying causes rather than the visible symptoms.

Example of a 5 Whys Analysis in Healthcare

To see how the 5 Whys works in practice, consider a hospital team investigating delays in patient discharge.

Problem

Patients are waiting longer than expected for discharge medication, delaying their discharge from hospital.

Why 1

Why was the discharge medication not ready?

Because the prescription was sent to pharmacy late.

Why 2

Why was the prescription sent late?

Because it was completed after the consultant ward round.

Why 3

Why wasn’t it prepared earlier?

Because discharge planning often begins on the day of discharge.

Why 4

Why does discharge planning begin so late?

Because expected discharge dates are not consistently identified during daily ward reviews.

Why 5

Why are expected discharge dates not discussed consistently?

Because there is no standard process for recording and reviewing anticipated discharge dates during multidisciplinary ward rounds.

At first glance, the problem appeared to be that pharmacy was too slow. However, the investigation revealed that the underlying issue sits much earlier in the discharge process. This changes the nature of the improvement work.

Instead of focusing solely on pharmacy performance, the team can explore improvements such as standardising discharge planning, introducing earlier identification of likely discharge dates, or embedding discharge planning into routine ward reviews.

The investigation has moved the team from treating a symptom to improving the system.

How to Run an Effective 5 Whys Analysis

The quality of a 5 Whys investigation depends less on asking five questions and more on asking good ones.

Experienced improvement teams use the technique thoughtfully, combining curiosity, evidence and collaboration to develop a shared understanding of the problem.

Focus on Processes Rather Than People

One of the most important principles of improvement is that most problems arise from the way work is designed rather than the intentions of the people doing the work.

If an answer identifies an individual, it is often worth asking another “Why?”

For example: Why was the prescription completed late?

Instead of stopping at: “Because the doctor forgot.”

Continue exploring: Why was it easy to forget?

What in the process allowed this to happen?

This shifts the conversation from blame towards learning.

Base the Investigation on Evidence

The first explanation offered during a discussion is not always the correct one.

Where possible, support each answer using evidence such as:

• Incident reports
• Audit findings
• Process observations
• Electronic health record data
• Staff experience
• Patient feedback

Evidence strengthens the investigation and helps avoid conclusions based solely on opinion or anecdote.

Involve the People Closest to the Work

Frontline staff understand how processes work in practice. They often recognise workarounds, delays and practical constraints that are invisible in policies or procedures.

Bringing together clinical staff, operational teams and improvement specialists usually leads to a richer understanding of why problems occur. It also helps build shared ownership of any improvements that follow.

Stay Curious

The purpose of the 5 Whys is exploration, not confirmation.

Avoid asking questions that steer the conversation towards a conclusion that has already been assumed. Instead, encourage genuine curiosity.

Sometimes the investigation confirms what the team expected. Often it reveals something entirely different.

Recognise When You Have Reached a Root Cause

One of the most common questions about the 5 Whys is: “How do we know when we’ve reached the root cause?”

The answer is not simply: “After asking Why five times.”

A useful root cause usually has three characteristics. It explains why the previous event occurred. It is supported by evidence rather than assumption. Most importantly, it identifies something that the team can realistically improve.

If asking another “Why?” simply moves into factors outside the team’s influence or no longer leads to useful improvement ideas, it is often a good indication that the investigation has gone far enough.

The goal is not to reach the deepest possible philosophical explanation. The goal is to reach an actionable understanding that helps improve the system.

Common Mistakes When Using 5 Whys

Although 5 Whys is straightforward, several common mistakes can limit its effectiveness.

Stopping Too Early

The first explanation often describes a symptom rather than an underlying cause.

Continuing the investigation usually reveals weaknesses in processes, communication or system design that would otherwise remain hidden.

Looking for Someone to Blame

Answers that identify individuals rarely lead to sustainable improvement.

A more useful question is: “What allowed this to happen?”

rather than: “Who caused this?”

Improvement becomes far more effective when the focus shifts from people to systems.

Accepting Opinions as Facts

The quality of the investigation depends on the quality of the evidence.

Where possible, validate each answer using observations, data or discussion with the people involved in the work.

Assuming There Is Only One Root Cause

Many healthcare problems have multiple interacting causes.

5 Whys explores one chain of causation at a time. If several different causal pathways appear likely, additional investigations may be needed.

Treating 5 Whys as the Entire Investigation

5 Whys is one tool within a wider improvement methodology.

High-performing teams often use it alongside:

• Pareto Charts to prioritise investigation
• Process Maps to understand workflow
• Fishbone Diagrams to explore possible causes
• Driver Diagrams to develop improvement ideas
• PDSA cycles to test whether changes deliver better outcomes

The strength of the method lies not only in asking “Why?”, but in connecting that understanding to meaningful improvement.

Frequently Asked Questions

Why is it called 5 Whys?

The method traditionally involves asking “Why?” around five times, although there is no fixed rule. Five questions are often enough to move beyond symptoms and uncover an actionable underlying cause.

Is it always exactly five questions?

No. Some investigations reach a meaningful root cause after three questions. Others may require seven or more.

The number is less important than reaching an evidence-based understanding that can guide improvement.

When shouldn’t I use 5 Whys?

5 Whys is less suitable for highly complex incidents involving multiple interacting causal pathways or where a formal Root Cause Analysis process is required.

In these situations, 5 Whys can still be useful, but it should be used alongside other investigation techniques rather than in isolation.

What’s the difference between 5 Whys and a Fishbone Diagram?

A Fishbone Diagram helps teams identify all the possible causes of a problem.

5 Whys then explores one of those possible causes in greater depth to understand why it exists.

Many improvement teams use the two methods together.

Is 5 Whys only used in Lean?

No. Although the technique originated within Lean manufacturing, it is now widely used across healthcare quality improvement, patient safety, operational excellence and service redesign.

Can 5 Whys be used for non-clinical problems?

Absolutely. The method is equally valuable for operational, administrative and organisational challenges, including appointment scheduling, workforce processes, procurement, information governance and service delivery.

Summary

5 Whys is one of the simplest and most effective techniques for understanding why problems occur.

By repeatedly asking thoughtful, evidence-based questions, improvement teams move beyond symptoms and uncover the underlying process issues that contribute to recurring problems.

Used alongside complementary improvement methods such as Pareto Charts, Process Mapping, Fishbone Diagrams, Driver Diagrams and PDSA cycles, the 5 Whys becomes an important part of a structured approach to Root Cause Analysis and continuous improvement.

Ultimately, the goal is not to ask five questions. The goal is to understand the system well enough to improve it.