Marcus Andrey Study
Ler em português Library

Framework · Facilitation techniques · 2 min read

5 Whys

Ask "why?" repeatedly about a single problem to get from the symptom to a root cause you can act on.

  1. 1Missing states

    Problem: developers build screens without error states.

    "Why? They are not in the file."
  2. 2No time

    The designer ran out of time before handoff.

    "Why? Review came too late."
  3. 3Late review

    Design review happens the day before the sprint starts.

    "Why? There is no fixed slot."
  4. 4No slot

    Nobody planned review time into the sprint rhythm.

    "Why? Handoff timing has no owner."
  5. 5Root cause

    Handoff timing is not part of sprint planning. You can act on this.

    Action: book a review slot.
5 Whys follows one problem down from the symptom until you reach a cause you can change.

Use it when

  • The same problem keeps coming back, for example designs that reach developers without error states.
  • A stakeholder proposes a quick fix, and you suspect it only treats the symptom.
  • A retro or incident review needs a quick root cause in about 15 minutes, on one specific issue.

How to use it

  1. Write one specific problem. Describe what happened, not who did it: "Developers built three screens without error states this sprint." Stay on one problem. Output: a one-line problem statement on the board.
  2. Ask "Why did this happen?" Write the answer under the problem. Base it on facts the group knows, not on guesses. Output: the first cause.
  3. Ask "why?" again about that answer. Repeat, each time about the last answer. If there are two real causes, accept the branch and follow each one separately. Output: a chain (or small tree) of causes. About 10 minutes.
  4. Stop at something actionable. Stop when the answer is a cause the group can change, usually a process, a habit or a missing agreement. If you reach "people are careless", go back one step. Output: one root cause per branch.
  5. Agree an action and an owner. Turn the root cause into one change with an owner and a date. Check it with the reverse question: "If we fix this, would the problem stop?" Output: an action, an owner and a check date. About 5 minutes.

Worked example

A UX lead uses 5 Whys in a 15-minute slot of a team retro on an internal operations platform. The problem: developers built screens without error states.

Step Question Answer
Problem Developers built three screens without error states this sprint.
Why 1 Why were they missing? The error states were not in the handoff file.
Why 2 Why were they not in the file? The designer ran out of time before handoff.
Why 3 Why did time run out? Design review happened the day before the sprint started.
Why 4 Why so late? There is no fixed review slot in the sprint rhythm.
Why 5 Why is there no slot? Handoff timing is not part of sprint planning.

Action: the lead and the product managers add a fixed review slot to the middle of each sprint. Owner: the UX lead. Check: at the next retro, count screens shipped without error states.

Watch out for

  • Blaming a person. "Because the designer forgot" stops learning. Ask why the process allowed it to happen.
  • Guessing instead of knowing. Each answer should be something the group can confirm. Mark guesses and check them later.
  • Forcing one chain. Real problems often have two causes. Follow each branch, or use a problem tree for complex issues.
  • Using it for big, fuzzy problems. "Why is UX not valued?" is too broad for 5 Whys. Use it on one specific event.

Template

Copy this into your retro notes or board.

5 WHYS                                            About 15 min

Problem (what happened, not who):
_________________________________________________

Why 1: ___________________________________________
Why 2: ___________________________________________
Why 3: ___________________________________________
Why 4: ___________________________________________
Why 5: ___________________________________________
(stop earlier if you reach a cause you can change)

Root cause:
Reverse check: "If we fix this, would the problem stop?"  yes / no
Action:                     Owner:            Check date:
Source
Toyota Production System
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close