The 5 Whys

Choose this exercise

Purpose: Trace cause-and-effect layers beneath a specific operational problem to identify actionable root causes.

Use it when: Use during incident reviews, post-mortems, or retrospective meetings when a team needs to examine systemic issues rather than treating immediate symptoms.

Skip it when: Skip when the issue involves complex multi-factor dilemmas with no linear causality, or when team safety is too low to discuss failures without personal blaming.

Group arrangement: Individual reflection followed by triads or full-group clustering at a shared wall.

Timing: Extended from Gamestorming core format to allow proper individual writing, wall synthesis, and consensus building.

Materials and tools

• Sticky notes (at least 10 pads, different colors optional)
• Dark felt-tip markers (one per participant)
• Roll of painter tape
• Flip-chart paper (2 to 3 large sheets)
• Whiteboard or open wall space (minimum 2 meters wide)

Before participants arrive

1. Write the target problem statement clearly at the top of the whiteboard or wall before the session.
2. Draw vertical columns on the board labeled 1 through 5, with the word Why? written beside each row.
3. Place pads of sticky notes and markers at each seat.

Say this to open

We are examining this specific problem: [read posted statement]. Instead of jumping to immediate fixes, we will trace the causal chain. Take five sticky notes and number them 1 through 5. On note 1, write why this problem happens. Then ask why that answer is true and write it on note 2. Continue until you have five connected answers.

How to run it

1. Frame the target problem 3 minutes

   Read the posted problem statement aloud. Verify that everyone understands the specific occurrence being analyzed. Provide a concrete example of a chain so the rule is clear: for instance, problem: server ran out of disk space; why 1: log files filled the drive; why 2: debug logging was left on after testing; why 3: release checklist lacked a turn-off step; why 4: checklist updates were not assigned; why 5: no clear owner for deployment documentation.

2. Write individual causal chains 7 minutes

   Ask participants to work silently. Each person numbers five sticky notes from 1 to 5. On note 1, they write why the primary problem exists. On note 2, they answer why note 1 happened. They repeat this drill down to note 5. Participants may stop before five if they reach an undeniable root cause, or continue past five if needed.

3. Post and compare columns 5 minutes

   Invite participants to post their notes in columns under the problem statement, matching levels 1 through 5 vertically. Allow three minutes for silent reading of the different paths. Point out recurring themes, branching paths, and differing assumptions across the wall.

4. Consolidate and agree on root causes 10 minutes

   Gather the group around a fresh flip-chart sheet. Write the original problem at the top. Ask the room to select the clearest, most systemic causal chain from the wall. A volunteer writes the selected answers onto clean sticky notes, placing one per level down the chart. Close by asking the debrief questions to check actionability.

Debrief questions

• At which level did the chain shift from an individual technical symptom to a team habit or process policy?
• Which step in this chain is most directly within our power to change this month?
• What assumptions in this sequence should we test against real data before taking action?

Finished output: A documented five-step causal chain posted on a flip-chart sheet identifying agreed root causes behind the target issue.

Remote

Set up an online whiteboard with a sticky note template numbered 1 to 5 for each person. Give 7 minutes for silent writing directly onto individual board zones. Move all columns onto a shared grid by row level 1 through 5. Use digital dot voting to pick the most systemic chain before building the final column.

Hybrid

In-person participants post physical sticky notes while a designated in-room scribe mirrors remote participants' digital notes onto the physical wall. Keep the video camera focused on the physical board while sharing the digital whiteboard on screen. Call alternately on remote and in-room participants during the consolidation step.

Access and participation choices

• Participants may dictate their causal steps to a partner or use digital text instead of handwriting.
• Participants may decline to post their notes publicly and simply observe or contribute verbal input during the synthesis step.

If the session gets stuck

Participants write people's names or blame individuals, such as 'John forgot to run the backup'.

Pause the writing and redirect to processes or systems. Ask: 'What policy, tooling, or training gap allowed that omission to occur?'

Answers keep repeating or hit a dead end like 'because that is how it has always been done'.

Prompt them to examine the immediate predecessor: ask what specific constraint or historical event created that standard practice.

Terms used here

• Root Cause: The fundamental breakdown or condition that, if resolved, prevents the problem from recurring.
• Causal Chain: An ordered sequence where each statement is the direct cause of the statement preceding it.