Protocol

Follow the why-chain until the cause becomes changeable

Do not stop at a label that merely renames the event.

About 1 min read

Before you use it

Use when
  • The immediate explanation is a label such as human error, missed step, bad data or process deviation.

Keep this limit in mind

  • Five Whys is a prompt for inquiry, not a guarantee of one root cause. Complex failures commonly have interacting causes.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Ask why the observed event was possible, then ask why about the answer while the chain remains evidence-based. Stop when you reach a factor the system can change, when the chain branches, or when evidence runs out. Record branches instead of forcing one linear root cause.

Steps

  1. Is this answer more than a label?
  2. What evidence supports the next link?
  3. Did the chain split into multiple contributors?
  4. Is the current factor changeable?
  5. Are we now guessing?

An example

Wrong field mapped → template used an old label → template had no version check → add a version gate at upload.

Check your result

The final factor suggests a concrete control and each causal link has evidence or is marked as a hypothesis.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingFollow the why-chain until the cause becomes changeable

Evidence and sources
Supports

Modern RCA guidance emphasizes system-level contributing factors and sustainable corrective actions rather than stopping at individual blame or documentation.

AHRQ discusses healthcare safety. The corpus transfers the system-design logic cautiously to ordinary work.

The Evolution of Root Cause Analysis · Introduction; RCA2; action hierarchy discussion

Supports

Five Whys is used in RCA2 to extend a causal chain beyond an immediate event description.

Repeated 'why' questions can oversimplify branching causes; answers still need evidence.

The Evolution of Root Cause Analysis · Discussion of event mapping and Five Whys

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details