MetodicMETODIC | learn
problem-solving

5 Whys

The 5 Whys method helps teams dig beneath surface-level symptoms to uncover the root cause of a problem by repeatedly asking 'Why?' This iterative questioning process reveals deeper insights and facilitates more sustainable solutions.

30-60 min5-10 peopleMedium
When to Use

Use this method when a team is facing a persistent problem and needs to identify the underlying cause before developing effective solutions. It's particularly useful when the initial problem statement feels vague or symptomatic.

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: (5 min) Define the problem. As a group, clearly articulate the problem statement and write it visibly for all participants.

  2. 2

    Step 2: (2 min) Distribute sticky notes. Give each participant five sticky notes, numbered 1 through 5.

  3. 3

    Step 3: (10 min) Individual 'Why' generation. Instruct participants to individually write down their answer to 'Why is this a problem?' on sticky note #1. Then, for each subsequent sticky note, they should answer 'Why is the previous answer true?'

  4. 4

    Step 4: (10 min) Share and synthesize. Have each participant post their sticky notes in columns under the 'Why?' headings. Facilitate a discussion to identify common themes and differences.

  5. 5

    Step 5: (10 min) Refine the problem statement. As a group, use the insights gained to rewrite the problem statement, focusing on the root cause.

Facilitator Tips
  • Encourage honesty and open communication. Remind participants that the goal is to uncover the truth, not to assign blame.
  • Prompt participants to consider different perspectives and avoid jumping to conclusions.
Variations
  • Use a fishbone diagram to visually represent the 'Whys' and their relationships.
  • Continue asking 'Why?' beyond five iterations if necessary to reach a meaningful root cause.
Source: GamestormingLearn more