BoardSnap is an iOS app that reads a Five Whys whiteboard — problem statement and five levels of why — and produces a structured causal analysis with the root cause and corrective action clearly identified.
The Five Whys is the most accessible root cause analysis tool: ask why five times in succession, and you move from observable symptom to fundamental cause. It works on a whiteboard in five minutes for a team of any size. The process is simple enough that it gets used — which is more than can be said for more elaborate analysis frameworks.
The problem is that a Five Whys session on a whiteboard leaves behind a vertical ladder of five or six boxes and arrows. That ladder is the analysis — but it only exists on the whiteboard. The root cause is box five. The corrective action is what you decided to do about box five. Neither survives the room without deliberate capture.
Teams that run Five Whys without documentation repeat the same root causes over and over. An engineering team that fixes the symptom three times before finally looking at the root cause has run three Five Whys sessions in their heads without writing any of them down. The written Five Whys, captured and filed against the specific problem, is what prevents the fourth incident.
At the top of the board, write the observable problem. Be specific: 'The nightly data export failed on April 25 at 02:14 UTC.' Not 'the export broke.' Specificity prevents the analysis from wandering. This is Why 0 — the starting point.
Write 'Why?' with an arrow pointing down to the first cause: 'Why did the export fail?' Answer: 'The API request timed out.' Write the answer in a box connected by the arrow. The answer must be a fact, not an assumption — note any assumptions separately.
Continue: 'Why did the API request time out?' → 'The external service response time increased.' 'Why did response time increase?' → 'The external service had no rate limit configured on our tenant.' 'Why was there no rate limit?' → 'Rate limit configuration is manual and there's no checklist for new tenant setup.' Each why gets its own box connected downward.
The fifth why should land at a cause that is systemic and actionable. 'Why is there no checklist for new tenant setup?' → 'Our onboarding process has never been formally documented.' That's the root cause — box it with a double line or a different color.
Next to the root cause box, write: 'Corrective action: [what will be done], by [owner], by [date].' The corrective action must address the root cause, not just the observable symptom. If the corrective action is 'restart the service,' you haven't done a Five Whys.
Sometimes a Why question has two answers — two parallel causes that both contributed. Write both, connected by 'AND' or 'OR,' and trace both chains if they go in different directions. Don't force a single-path analysis if the reality is parallel causes.
Open BoardSnap. The vertical or horizontal causal ladder — Why 0 through Why 5 — with boxes, arrows, and a double-boxed root cause. BoardSnap AI reads the numbered levels and the root cause marker.
A structured Five Whys report: Problem statement → Why 1 cause → Why 2 cause → Why 3 cause → Why 4 cause → Why 5 root cause, each as a numbered section with the fact or evidence noted. The root cause is labeled prominently. The corrective action is listed as an open action item with owner and date. The report is ready for an incident post-mortem system or a process improvement log.
After a bug reached production, the team ran a Five Whys in 20 minutes. Why 5 was 'Our automated tests don't cover user-specific rate limit logic.' The corrective action: add rate limit test cases by end of sprint, owner: lead engineer. BoardSnap captured the chain. The PM filed it against the incident in the issue tracker that day.
A customer escalated the same issue for the third time. The CS lead ran a Five Whys. Why 5: 'Customer success doesn't receive product changelog updates — they find out about changes when customers call.' Corrective action: CS gets a pre-release changelog summary every sprint. BoardSnap documented it. The process change was implemented in a week.
No. The goal is to reach the root cause — sometimes that's three levels deep, sometimes it's six or seven. Five is a heuristic for 'keep going until you find a systemic cause, not just an immediate one.' Use the number that the analysis actually requires. Label your board 'Why 1' through 'Why N' and BoardSnap will read whatever depth you go to.
Yes. Draw each chain separately — parallel vertical ladders on the same board. Label each chain at the top with the branch problem it's addressing. BoardSnap reads each chain as a separate analysis and produces separate sections in the output.
Write both answers and mark one as 'Hypothesis A' and the other as 'Hypothesis B.' Add a note about what evidence would confirm or deny each. Board Snap will include both hypotheses in the output. This is often the most valuable part of a disputed Five Whys — making the assumptions visible.
Snap the board, ship the action items in ten seconds.