Purpose

The Five Whys Retrospective applies the classic root-cause analysis technique to the team's most pressing problem. By asking why five times in succession, the team drills past symptoms to find the underlying cause. It is the go-to format when one specific issue keeps recurring and surface-level fixes have not worked.

At a glance

• Group size: 3–10 people
• Duration: 20 minutes
• Difficulty: Intermediate
• Facilitation style: Structured
• Setting: Both / Remote-friendly

How to run

1. Select the one problem to analyze (from a previous retro or by team vote) (3 minutes).
2. State the problem clearly. Ask: Why does this happen? Record the answer (2 minutes).
3. Take the answer and ask Why again. Repeat five times total, recording each level (10 minutes).
4. At the root cause, brainstorm countermeasures (3 minutes).
5. Agree on one countermeasure to implement with an owner and timeline (2 minutes).

Materials needed

• Whiteboard with a vertical chain diagram
• Markers
• Timer

Pitfalls & common mistakes

• Stopping at the second or third why because it feels like enough — push to five.
• Branching into multiple causes at each level and losing focus — pick one path, note others for later.
• Blaming individuals rather than systems at deeper levels.
• The root cause being something the team cannot influence — still identify it, then find the deepest controllable cause.

Inclusion & accessibility

• Frame the exercise as a blame-free investigation.
• Allow written contributions so quieter members can suggest answers.
• The linear format is easy to follow regardless of language proficiency.

Variations

• Fishbone + Five Whys: use a fishbone diagram to categorize potential causes, then Five Whys on the top one.
• Group Five Whys: split into small groups that each analyze a different problem, then share.
• Five Whys + Countermeasure Matrix: map each root cause to a specific, testable countermeasure.

When NOT to use this

• When the team has many small issues rather than one dominant problem — use a broader format like Four Ls.
• When the problem is interpersonal rather than systemic.

Source & further reading

• Taiichi Ohno, Toyota Production System.
• Eric Ries, The Lean Startup (Five Whys for startups).