Project & Development
5 Whys for Beginners: Ask Why Five Times to Find the Root Cause and Stop It Coming Back
Beginner | 2 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Beginner: No technical terms. Just answer the whiteboard's questions, following the examples, and it takes shape.
This beginner-friendly 5 Whys template is for anyone handling root cause analysis for the first time, to follow the method step by step and land on a root cause and a preventive fix. The whiteboard uses two pages: on the left, a frame for the facts, the four steps of a session, a fishbone diagram covering people, method, machine and materials, and a six-row 5 Whys chain; on the right, good and bad whys, the root cause with its fix, and a four-by-four action plan. The task board has five columns - problem, digging into why, fix decided, in progress and effect checked - and starts with 4 parent tasks and 12 subtasks, all not started. Beginners usually get stuck by blaming carelessness and stopping there, so the board spreads the causes across four angles first and uses them as clues for the five whys. A worked example about a double-booked meeting room fills all six rows, and one review takes about 30 minutes.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
5 Whys Root Cause Board
How to use: (1) Write what happened as facts with numbers (the problem frame) → (2) List cause candidates from four angles - people, method, machine and materials (the fishbone diagram) → (3) Use those clues to ask why five times (the 5 Whys chain) → (4) Pick the root cause, decide the fix and write an owner and a due date (root cause frame and action plan)
1. The Problem That Happened (write facts with numbers)
- When and what happened e.g. on 2 September at 10:00 the visitor meeting room was double booked and the meeting started 20 minutes late
- Who was affected and how much e.g. 2 visitors and 4 colleagues waited 20 minutes, and 3 people had to find another room
- How to write it 1. Make the event the subject, not a person 2. Always include a count, a time or an amount 3. e.g. "someone did not check" becomes "there was no step for entering the booking"
2. How to Run a 5 Whys Session (4 steps)
- 1. Write the facts Put what happened into one sentence, with the date and a number. Make the event the subject instead of a person, so the next why points at the process.
- 2. Ask why five times Start from the clues in the fishbone diagram and dig into the ones you can verify. You may move between angles as you go, for example from people to machine. Answer only one why, based on the sentence just above. Mark answers you have not verified with "maybe" and check them later.
- 3. Read it backwards Read from why 5 back to why 1, joining each line with "and that is why". Where two lines do not connect, a step is missing, so add one in between.
- 4. Decide the fix List three fixes that hit the root cause and pick the one the process itself can enforce. Write the owner, the due date and how you will check the effect. The chosen one goes on the "Main fix" row, the rest on the backup rows. Updating the manual belongs on the "Make it stick" row instead.
3. Fishbone Diagram (cause and effect) / list causes from four angles - people, method, machine, materials / use them as clues for board 4 / the four cards below are examples
- Problem
- People Cause 1 (what people did) e.g. the person who asks for the room and the person who types it into the booking sheet are different, and nobody checks that it was entered
- Method Cause 2 (the rules and the process) e.g. there are two ways to hold a room, by word of mouth and by the booking sheet, and both of them work
- Machine Cause 3 (tools and systems) e.g. the booking sheet accepts two entries for the same slot and shows no warning when a room is double booked
- Materials Cause 4 (information and documents count as materials) e.g. today's bookings are not posted anywhere, so nobody can check availability at the last minute
4. The 5 Whys Chain (dig with the clues from board 3 / problem then why x5 / the six rows below are examples, so clear them and write your own case)
- Problem On 2 September at 10:00 the visitor meeting room was double booked and the meeting started 20 minutes late
- Why 1 Two bookings sat in the same time slot and nobody noticed until the morning of the meeting
- Why 2 One of them was never entered in the booking sheet, because it had only been asked for out loud
- Why 3 The person who was asked was on a call with a visitor and could not type it into the sheet at that moment
- Why 4 The booking sheet opens only on an office PC, so it cannot be filled in during a call or away from the desk
- Why 5 No single way of booking a room was ever agreed, so a spoken request still holds a room and nobody had to make the sheet usable for everyone
5. Good Whys (they question the process)
- e.g. the booking sheet often cannot be opened during a call - that points at the tool, not the person
- Answer only one why, based on the sentence just above
- Write the answer as a fact you can verify
- If five is not enough, six is fine. The chain matters, not the count
6. Bad Whys (they blame a person)
- e.g. they did not check - next time it ends again with 'we will be careful'
- e.g. they were not motivated - no fix can be built on that
- Three reasons under one why - the chain branches and stops going deeper
- Starting to write fixes halfway - the cause stays shallow
7. Root Cause and the Fix That Prevents It
- Root cause (pick one from why 5) e.g. there is no single way to book a room, so a spoken request still holds it
- The fix and its owner e.g. bookings happen only in a sheet that also opens on a phone (Owner: ____ / Due: __/__)
- How you will check the effect e.g. count double bookings one month later. Zero means it worked, one or more means the process needs another look
8. Action Plan for the Fixes
| Fix | Owner | Due | How to check | |
|---|---|---|---|---|
| Main fix | e.g. book only in the mobile-friendly sheet | Owner: ____ | by 10 Sep | zero double bookings after a month |
| Backup 1 | e.g. if asked out loud, enter it yourself on the spot | Owner: ____ | from 8 Sep | count missed entries once a week |
| Backup 2 | e.g. post today's bookings at the room door | Owner: ____ | by 20 Sep | change in the number of questions |
| Make it stick | e.g. add the booking steps to the manual and checklist | Owner: ____ | by 30 Sep | the next person books the same way |
Task board contents
Problem 16 items
State the facts
Line up the starting point. If this stays an opinion, the whys drift towards blaming people.
Sum up in one line
Write what happened, not who is at fault, in one sentence. Done when a reader can picture the same scene.
Add date and number
Put in the time, the count or the minutes lost, so you can compare the effect later.
List those affected
Write down who was inconvenienced. The size of the impact tells you how much effort the fix deserves.
Ask why five times
The heart of the 5 Whys. Using the four angles from board 3 as clues, follow one cause at a time from the sentence just above.
Write why 1 and 2
Trace the two direct causes of the problem. The four angles on board 3 are your clues. Answer with facts, not guesses.
Write why 3 to 5
Keep digging until you reach the process or a decision. If you land on someone's character, step back one row and try again.
Read it backwards
Read from why 5 up to why 1 with "and that is why". If a row does not connect, add one in between and you are done.
Root cause and fix
Turn what you dug up into action. Pick a fix the process itself can enforce, and name an owner and a due date.
Pick one root cause
From around why 5, choose the one that stops the problem coming back. Keep a note of the rows you did not pick.
List three fixes
Write three fixes for the root cause and compare them by whether a step or a tool prevents it, not care or effort.
Set owner and date
Give the chosen fix an owner and a due date. Done when who does what by when is written down.
Do it and check
Run the fix, confirm with numbers that the problem has not returned, and leave a record of it.
Run the fix
Carry out the fix by the due date. If it will be late, rework the owner and the date right then.
Count the results
One month later, count how often the same problem happened. Zero, or a clear drop, counts as effective.
Update the manual
Add the agreed steps to the manual or the checklist so it survives a change of owner. Write the owner and due date on the "Make it stick" row of board 8 first.
