5 Whys Is Not Enough

The Leadership Layers Hidden Behind Every Root Cause

The Problem with “Finding the Root Cause”

The 5 Whys technique is one of the most widely used tools in Lean and operational excellence. Its appeal is obvious: simple, intuitive, and fast.

A problem occurs. You ask why. Then you ask why again. Within minutes, you arrive at what appears to be a root cause.

And that is exactly where most organizations stop.

But in regulated MedTech environments, where patient safety, compliance, and system reliability are non-negotiable, stopping early is not just insufficient. It is risky.

Because the first “root cause” is rarely the real one.

The Traditional View of 5 Whys

In its classic form, 5 Whys follows a linear logic:

• A defect or failure is identified.

• The team asks “why” repeatedly.

• Each answer leads to the next question.

• After 3 to 5 iterations, a root cause is declared.

This approach typically converges on process-level explanations:

• Operator missed a step.

• Procedure was unclear.

• Inspection was not performed correctly.

These are valid observations. But they are almost always incomplete.

The Structural Limitation: Artificial Root Cause Closure

Most 5 Whys analyses suffer from what can be called Artificial Root Cause Closure.

This occurs when the investigation stops at the first answer that is:

• Plausible.

• Actionable at the local level.

• Socially acceptable within the team.

In practice, this often leads to conclusions like:

• “Operator error.”

• “Training deficiency.”

• “Procedure not followed.”

These answers create the illusion of resolution while leaving the underlying system untouched.

The result?

The same issue returns. Again, and again. Often under a different label.

The Uncomfortable Truth

If you continue asking “why” beyond the accepted stopping point, something interesting happens.

The narrative begins to shift.

• Why did the operator miss the step?
  → Training was insufficient.

• Why was training insufficient?
  → Training content did not reflect actual process risks.

• Why did training not reflect risks?
  → PFMEA assumptions were outdated.

• Why were PFMEA assumptions outdated?
  → No structured feedback loop from production to risk management.

• Why does that feedback loop not exist?
  → Leadership has not prioritized system-level risk integration.

At this point, the analysis has moved far beyond the operator.

It has reached the system.
And then, inevitably, it reaches leadership.

This is the uncomfortable truth:

If you go deep enough, most root causes are not operational. They are structural. And many are leadership-driven.

A Multi-Layer Root Cause Model

To make this explicit, root causes should be understood across multiple layers:

Layer 1: Symptom

• Defect, deviation, complaint, or failure event.

Layer 2: Process Breakdown

• Missed step, incorrect parameter, inspection failure.

Layer 3: System Weakness

• Control plan gaps.

• PFMEA inaccuracies.

• Inadequate training systems.

Layer 4: Leadership Decision or Omission

• Resource allocation decisions.

• Lack of system ownership.

• Misaligned priorities.

Layer 5: Organizational Culture

• Tolerance for shortcuts.

• Focus on output over risk.

• Lack of accountability across layers.

Traditional 5 Whys typically stops at Layer 2 or 3.

True operational excellence requires reaching Layer 4 and often Layer 5.

MedTech Example: Disposable Infusion Set Assembly

Consider a high-volume disposable infusion set assembly line.

Initial Problem:
Increased field complaints due to leakage.

Traditional 5 Whys Outcome:

• Leak detected.

• Why? Seal not properly formed.

• Why? Operator missed inspection step.

• Root cause: Operator error.

Corrective action: Retrain operator.

Extended Why Analysis:

• Why was the inspection missed?
  → Operator overwhelmed by cycle time pressure.

• Why was there cycle time pressure?
  → Line balancing prioritized output over inspection robustness.

• Why was inspection not robust?
  → Control plan assumed low variability in sealing process.

• Why was that assumption incorrect?
  → PFMEA did not reflect real process drift observed in production.

• Why was PFMEA not updated?
  → No ownership or structured review cadence defined by leadership.

Now the picture changes.

The issue is no longer an operator problem.

It is a system design failure reinforced by leadership decisions.

And the risk is no longer theoretical.

It directly impacts patient safety, regulatory compliance, and brand trust.

Leadership Is the Missing Link

Manufacturing organizations often believe they have strong leadership because strategy exists at the top.

But operational excellence depends on leadership at every level.

As highlighted in prior analysis of manufacturing leadership gaps:

• Front-line supervisors must translate standards into daily execution.

• Mid-level managers must ensure systems are functioning and aligned.

• Plant leadership must create structures that sustain performance.

When these layers are misaligned:

• Processes drift.

• Risk signals are ignored.

• Problems repeat.

5 Whys does not fail because the method is flawed.

It fails because organizations are unwilling to follow the logic to where it leads.

From 5 Whys to Systemic Why Analysis

To operate at a higher level, 5 Whys must evolve.

Systemic Why Analysis extends beyond process-level thinking and enforces a structured escalation:

• Continue questioning until system-level contributors are identified.

• Explicitly link findings to:

  • PFMEA assumptions.

  • Control plan effectiveness.

  • Training system design.

  • KPI structures and incentives.

Most importantly:

• Require identification of leadership-level contributors.

If the analysis does not surface a system or leadership dimension, it is not complete.

Key Metrics That Reveal True Root Causes

Organizations that operate at this level track indicators that go beyond defects:

• Recurrence rate of similar issues.

• CAPA effectiveness over time.

• Inspection escape rates.

• Training coverage vs process complexity.

• Control plan compliance and drift.

These metrics expose whether root causes were truly addressed or merely reassigned.

Strategic Leadership Insight

There is a simple test for any root cause analysis:

If your root cause stops at the operator or the process, you have stopped too early.

Real root causes are embedded in:

• System design.

• Decision-making structures.

• Leadership priorities.

And until those layers are addressed, problems will not disappear. They will only relocate.

Closing Perspective

5 Whys remains a powerful tool.

But only if used with the discipline to follow the logic all the way through.

In MedTech manufacturing, where the stakes include patient safety and regulatory compliance, partial answers are not acceptable.

Intelligent Operational Excellence requires:

• System-level thinking.

• Cross-layer accountability.

• Leadership ownership of outcomes.

Because in the end:

Operational failures are rarely created on the shop floor.
They are enabled by the systems above it.