5 Whys Root Cause Analysis

Choose this exercise

Purpose: Identify an underlying operational or procedural cause behind a recurring team problem.

Use it when: Use when a team faces recurring breakdowns, recurring bugs, or handoff errors where human workflows and technical systems intersect.

Skip it when: Skip for large, multi-variable crises with dozens of independent contributing factors that require formal systems mapping or statistical failure analysis.

Group arrangement: Subgroups of 3 to 5 people

Timing: UWT standard 25-minute design, adapted from the untimed EasyRetro 5-step guide.

Materials and tools

• One printed 5 Whys Worksheet per subgroup or digital whiteboard equivalent
• One black marker per subgroup
• Timer visible to the room

Before participants arrive

1. Identify a concrete, agreed-upon problem symptom in advance or invite subgroups to select an operational friction point.
2. Arrange seating into tables of 3 to 5 participants.
3. Distribute one worksheet and one marker to each group.

Say this to open

We often treat symptoms rather than root causes. Today we will use the 5 Whys to drill down beneath the surface of an operational issue. We state the problem clearly in one sentence, ask why it happened, take that answer, and ask why again. We repeat this until we hit an underlying process or communication breakdown we can actually repair.

How to run it

1. Frame the problem statement 4 minutes

   Each subgroup selects an operational issue and summarizes it into a single factual sentence. For example: 'The weekly analytics report was delivered three days late.' Groups write this sentence in the top box of their worksheet. The facilitator visits groups to ensure statements describe observable events rather than assumed blame.

2. Drill through five causal layers 10 minutes

   Subgroups ask 'Why did this happen?' and agree on the direct cause. They write that answer on Line 1. They turn Line 1 into the next question: 'Why did [Line 1] happen?' and write the explanation on Line 2. Continue this chain through Line 5 or until hitting an actionable process, training, or structural root cause. Anyone can choose to pause the group to confirm evidence.

3. Identify countermeasure 5 minutes

   Groups examine their final cause (typically layer 4 or 5). Together, they draft one concrete countermeasure designed to prevent that specific breakdown from recurring. Record this countermeasure at the bottom of the worksheet.

4. Debrief and compare chains 6 minutes

   Reconvene the full room. Invite two or three subgroups to read their original problem statement and their final root cause. Facilitate the structured debrief questions.

Debrief questions

• At which layer did your focus shift from a technical or surface symptom to a human or process problem?
• How did testing each statement for factual evidence prevent blaming individuals?
• What is one immediate test your team can run to verify your chosen countermeasure?

Finished output: A completed causal chain worksheet linking a specific operational failure to an actionable process root cause and prevention step.

Remote

Run in breakout rooms of 3 to 5 people. Replicate the worksheet on a shared digital whiteboard with 5 stacked sticky notes and one countermeasure card per breakout frame. One nominated scribe writes while participants offer answers verbally or via chat.

Hybrid

Keep in-person participants grouped at physical tables and remote participants grouped together in virtual breakout rooms. All groups log their chains into a shared digital document so in-person and remote participants view and compare completed chains simultaneously during the debrief.

Access and participation choices

• Provide large-print digital and physical worksheets.
• Offer non-verbal participation options by allowing participants to contribute potential causes via chat or sticky notes without reading aloud.
• Participants may pass on speaking during the whole-group report-out.

If the session gets stuck

The group branches off into multiple competing causes at step two.

Ask the group to pick the single most frequent or impactful cause to trace down first. Note other branches on scratch paper to pursue later if needed.

Answers stop at individual human blame (for example, 'Alex forgot to click send').

Ask the follow-up: 'Why did the system or workflow allow a single forgotten click to cause a failure without a reminder or fallback?' Shift the focus from individual blame to process safety.

Terms used here

• Root Cause: The fundamental, underlying reason a problem occurs, which, if resolved, prevents recurring failure.
• Countermeasure: An operational action or process update designed to neutralize a specific root cause and prevent recurrence, distinct from a temporary patch.