MetodicMETODIC | learn
problem-solving

5 Whys Analysis

The 5 Whys Analysis is a root cause analysis technique that helps teams drill down to the fundamental cause of a problem by repeatedly asking "Why?" five times. This iterative questioning process uncovers layers of symptoms to reveal the core issue.

30-45 min3-8 peopleMedium
When to Use

Use this method when a project underperforms or when you need to understand the underlying reasons for a recurring problem. It's particularly useful for preventing similar issues in the future.

How It Works

Solves: Superficial problem-solving that only addresses symptoms, leading to recurring issues.

Step-by-Step Instructions
Follow these steps to facilitate this method
  1. 1

    Step 1: Identify the Problem (5 min). Clearly state the problem you want to address.

  2. 2

    Step 2: Set the Stage (5 min). Explain the purpose of the exercise: to investigate, not to blame.

  3. 3

    Step 3: Ask 'Why?' (5 min per 'Why'). For the initial problem, ask 'Why did this happen?' and record the answers. Vote on the most relevant answer.

  4. 4

    Step 4: Repeat 'Why?' (5 min per 'Why'). Turn the chosen answer into the next problem statement and repeat the 'Why?' question. Continue this process for a total of five times (or until the root cause is identified).

  5. 5

    Step 5: Identify the Underlying Cause (5 min). After asking 'Why?' five times, document the team's consensus on the root cause. Verify that addressing this cause would prevent the initial problem from recurring.

  6. 6

    Step 6: Propose Solutions (10 min). Brainstorm solutions to address the root cause. Choose one or two solutions, assign owners, and set a follow-up date.

Facilitator Tips
  • Encourage diverse perspectives to get a richer understanding of the problem.
  • Remind the team to focus on facts and avoid assumptions.
Variations
  • Breakout groups: After identifying the initial problem, divide the team into smaller groups, each exploring a different potential cause. Compare findings afterward.
Source: Atlassian Team PlaybookLearn more