Gumshoe · Method reference

Five whys

Ask "why" repeatedly to move from a surface symptom to a root cause.

Conceptual illustration of five whys.
Effort
Low
Participants
Not required
Remote friendly
Yes
Evidence / output
Inference

What it is

A root-cause technique: starting from a problem statement, ask “why” and answer, then ask “why” of that answer, repeating (roughly five times) until you reach an underlying cause rather than a symptom.

When to use it

During Synthesize, when a problem’s true cause is unclear and you risk treating symptoms.

Why (value)

Cheaply pushes thinking past the first, obvious explanation toward causes you can actually address.

How to run it

  1. State the problem clearly.
  2. Ask why it happens; record the answer.
  3. Ask why of that answer; repeat about five times.
  4. Stop when you reach a root cause you can act on.
  5. Validate the causal chain before acting.

Inputs and outputs

  • Inputs: A clearly stated problem and people who understand it.
  • Outputs: A causal chain leading to a probable root cause.

Time and effort

Low. Minutes within a discussion.

Evidence and limitations

Produces a plausible causal hypothesis, not proof. The chain reflects the group’s reasoning and should be validated with evidence before large investments. See Evidence and limitations.

Tips and pitfalls

  • Follow one causal chain at a time.
  • Beware stopping at a convenient answer.
  • Validate the root cause; do not treat the chain as fact.

Variations

Fishbone (Ishikawa) diagrams, why-because analysis.

Need help choosing and applying a method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

Explore related methods

  • Affinity diagramming — Cluster many observations into themes to make sense of qualitative data as a group.
  • Problem statements — A crisp, shared articulation of the problem worth solving, before anyone jumps to solutions.
  • Assumption mapping — Surface the beliefs a plan depends on and sort them by risk so you test the scariest ones first.

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.