Five whys analysis — the full causal chain captured before the team forgets the middle steps.
A well-facilitated five whys analysis on a whiteboard traces the root cause chain in a way that's impossible to reconstruct afterward. BoardSnap captures every step — symptom through root cause — before the chain fades.
Why agile coaches love this workflow
The five whys technique is powerful because of the intermediate steps — the second and third whys that connect the visible symptom to the systemic root cause. Those intermediate steps are where the real insight is. But they're also the most likely to be forgotten or compressed when someone writes up the analysis later.
BoardSnap preserves the full chain. Snap the five whys whiteboard and get a summary that shows each why as a step in the causal chain — not just the symptom and the root cause, but the logic that connects them. That logic is what the team needs to design an effective corrective action.
The exact flow
- Write the problem statement at the top of the board
Be specific: 'The sprint demo failed because Feature X wasn't ready.' Not 'we had a bad sprint.' Specific problem statements produce better why chains.
- Facilitate each 'why' step on the board
For each answer to 'why,' write it on the board and draw a connecting arrow. Label the arrow 'because.' The visual chain on the board is what BoardSnap reads as the causal sequence.
- Challenge superficial answers
As coach, your job is to push past organizational blame to systemic causes. When the team says 'because John was too busy,' ask why John was too busy. Write each push and response.
- Identify the root cause and mark it
Circle the root cause when you've reached it — the point where the answer is a systemic issue, not a person or a one-off event. Label it 'Root Cause.'
- Snap the complete chain
The full causal chain from symptom to root cause is on the board. Snap it. The BoardSnap summary is the five whys analysis document, complete and shareable.
What you'll get out of it
- Full causal chain captured — not just symptom and root cause
- Intermediate steps preserved with the 'because' logic intact
- Root cause labeled explicitly in the summary
- Five whys analysis shareable with stakeholders who weren't in the session
- Analysis history per team for pattern recognition across incidents
Frequently asked
Can BoardSnap read a five whys chain with branches — where multiple whys follow from one answer?
Yes. Branching five whys chains are read with their branch structure. If 'Why 2' has two possible answers leading to different branches, BoardSnap describes both branches in the summary.
Should I always do exactly five whys?
The 'five' is a heuristic, not a rule. Stop at the root cause — sometimes it's three whys, sometimes it's seven. The goal is to reach a systemic cause, not to hit a count.
Can the five whys BoardSnap summary serve as input to a corrective action plan?
Yes. The root cause identified in the summary is the starting point for the corrective action. The intermediate causal steps explain why the corrective action addresses the right level of the system.
Agile Coaches: try this on your next five whys.
Three taps. Action items in your hand before the room clears.