The "3-Legged 5 Why" is a structured approach to root cause analysis that expands on the traditional 5 Whys technique. While the standard 5 Whys focuses on repeatedly asking "Why?" to drill down to a single root cause, the 3-Legged 5 Why method investigates three distinct "legs" or lines of inquiry to ensure a more comprehensive analysis. Here’s how it works:

Describe the Issue:

Defining the problem is a critical first step in effective problem solving. Here’s how you can do it:

1. Be Specific: Clearly state what the problem is, avoiding vague or broad descriptions. Focus on facts, not opinions.
2. Differentiate Fact from Opinion: Gather and analyze supporting data (both qualitative and quantitative) to ensure you’re describing what’s actually happening, not just perceptions.
3. Involve Stakeholders: Engage all workgroups affected by the problem and consult subject matter experts to gain a full understanding of the issue.
4. Go to the Gemba: Observe the process where the problem occurs. Document how the process currently works—who does what, with what tools, in what timeframe, and how information flows.
   1. Gemba Walk – ASQ TV

• Ask Descriptive Questions: Use the following to clarify the problem:
  • What happened? (What is the problem? What product or process is affected?)
  • Where was the problem detected? (Location or process step)
  • When was the problem detected? (Date/time, frequency)
  • How many/much is affected? (Scope, quantity, percentage)
  • Who detected the problem? (Person or role)
  • Why is this a problem? (Impact or consequence at a high level)
• Use Tools: Consider using tools like an Is/Is Not Matrix, process flowcharts, or cause-and-effect diagrams to help clarify the problem’s boundaries and context.
• Fishbone (Ishikawa) Diagram – ASQ TV
• Approaches to Root Cause Analysis – ASQ TV

• https://videos.asq.org/root-cause-analysis-for-beginners-part-1-of-2/

• https://asq.org/quality-resources/seven-basic-quality-tools

Example of a well-defined problem statement: "During final inspection on June 10, 2025, 15% of widgets produced on Line 2 were found to have surface scratches, exceeding the acceptable defect rate of 2%. The issue was first detected by the quality inspector and appears to occur only during the evening shift."

A well-defined problem statement like this sets the stage for effective root cause analysis and solution development.

The Three Legs:

1. Process/Specific Issue Leg: This line of questioning explores the process or system failures that contributed to the problem. It seeks to understand what in the workflow, procedure, or method allowed the issue to occur.
2. Detection Leg: This leg examines why the problem was not detected earlier. It looks at the controls, checks, or monitoring systems that failed to catch the issue before it became significant.
3. Systemic/Management Leg: This leg investigates broader organizational or management factors, such as training, policies, culture, or resource allocation, that may have contributed to the problem or allowed it to persist.

How to Use the 3-Legged 5 Why:

• For each leg, start with the problem statement and ask "Why?" up to five times (or as many as needed) to dig deeper into the root causes.
• Ask "Why?" for the first time. Ask why the problem occurred and write the answer directly below the problem statement.
• Continue asking "Why?" For each answer given, ask "Why did this happen?" again. Write each subsequent answer below the previous one, forming a chain of causes.
• Repeat until you reach the root cause. Typically, you’ll ask "Why?" about five times, but it may take fewer or more repetitions. Stop when the answer reveals a cause that is actionable and within your control, or when no further meaningful answers can be given.
• Document the process. Capture the entire chain of questioning and answers. This helps visualize the progression from the problem to its root cause.
• Verify and act. Once you identify the root cause, discuss and verify it with your team. Then, develop and implement corrective actions to address the root cause.

Example:

Problem: Customers are dissatisfied with website functionality.

• Why? There are frequent errors in layout and text.
• Why? The sites are completed late and under time pressure.
• Why? Too many projects are being undertaken simultaneously.
• Why? There is no system to manage project intake.
• Why? The company lacks a project management process.

In this example, the root cause is the lack of a project management process, not just the immediate symptoms.

Tips:

• It’s important to avoid jumping to conclusions or stopping too early.
• Involve people who are familiar with the process or problem.
• Sometimes, you may need to ask "Why?" more or fewer than five times.
• The 5 Whys can be used alone or in combination with other tools, such as brainstorming or cause-and-effect diagrams.

https://asq.org/quality-resources/five-whys

Repeat this process for the Detection Leg:

This leg examines why the problem was not detected earlier. It looks at the controls, checks, or monitoring systems that failed to catch the issue before it became significant.

Example:

Problem: Customers are dissatisfied with website functionality.

• Why wasn’t this detected? There is no validation process
• Why? Not defined process
• Why? Change management is not defined either
• Why? The company lacks some of the basic quality management system lessons learned.
• Why? The company does not understand what the benefits there are to a quality management system

Repeat this process for the Systemic/ Management Leg:

• This leg investigates broader organizational or management factors, such as training, policies, culture, or resource allocation, that may have contributed to the problem or allowed it to persist.
• Why did the possibility exist for this situation to occur? Start-up company with many procedures / processes not defined
• Why? No quality manager
• Why? No one assigned to take on this task
• Why? Owner does not know operations

Here is how this example looks in the 3-Legged 5 Why template:

Benefits of the 3-Legged 5 Why:

1. Document each answer and continue probing until you reach a cause that is actionable and within the organization’s control.
2. By exploring all three legs, you avoid focusing solely on immediate process errors and uncover deeper, systemic issues that may otherwise be missed
3. Provides a more thorough root cause analysis by ensuring multiple perspectives are considered.
4. Helps prevent recurrence by addressing not just the direct cause, but also failures in detection and underlying systemic issues.
5. Encourages cross-functional collaboration, as different departments may be involved in each leg of the analysis.

Example Application: Suppose a defective product reaches a customer.

1. Process Leg: Why did the defect occur in production? (Ask the 5 Why’s)
2. Detection Leg: Why was the defect not caught during inspection? (Ask the 5 Whys)
3. Systemic/Management Leg: Why did the training or quality system not prevent or detect the issue? (Ask the 5 Whys)

By systematically addressing each leg, you develop a more robust corrective action plan that tackles the problem from multiple angles.

Note: This article was written with the help of https://asq.org/quincy-ai