5 Whys for Beginners: Ask Why Five Times to Find the Root Cause and Stop It Coming Back

Project & Development

5 Whys for Beginners: Ask Why Five Times to Find the Root Cause and Stop It Coming Back

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.

0 Likes 0 Copies Author: WeProcess
5 Whys root cause analysis problem solving preventing recurrence fishbone diagram
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode 5 Whys for Beginners: Ask Why Five Times to Find the Root Cause and Stop It Coming Back
Sign up free and use this template

Whiteboard preview

1. The Problem That Happened (write f... 2. How to Run a 5 Whys Session (4 steps) 5. Good Whys (they question the process) 6. Bad Whys (they blame a person) 7. Root Cause and the Fix That Preven... 8. Action Plan for the Fixes 5 Whys Root Cause... How to use: (1) W... Root cause and fix Decisions, owner ... The problem and b... Good whys and ins... When and what happenede.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 muche.g. 2 visitors and 4 colleagues waited 20 minutes, and 3 people had to find another room How to write it1. Make the event the subject, not a person2. Always include a count, a time or an amount3. e.g. "someone did not check" becomes "there was no step for entering the booking" 1. Write the factsPut 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 timesStart 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 backwardsRead 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 fixList 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 Diagr... Problem People Cause 1 (what people did)e.g. the person who asks for the room and the person who types it into the booki… Method Cause 2 (the rules and the process)e.g. there are two ways to hold a room, by word of mo… Machine Cause 3 (tools and systems)e.g. the booking sheet accepts two entries for the same slot and shows no warnin Materials Cause 4 (information and documents count as materials)e.g. today's bookings are not posted anywhere, so nob 4. The 5 Whys Cha... 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 f… 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 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 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 ownere.g. bookings happen only in a sheet that also opens on a phone(Owner: ____ / Due: __/__) How you will check the effecte.g. count double bookings one month later. Zero means it worked, one or more means the process needs another look 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
100%

Drag to move, scroll to zoom

Task board contents

Problem 16 items

State the facts
Ask why five times
Root cause and fix
Do it and check
Sum up in one line
Add date and number
List those affected
Write why 1 and 2
Write why 3 to 5
Read it backwards
Pick one root cause
List three fixes
Set owner and date
Run the fix
Count the results
Update the manual

Digging into why 0 items

Fix decided 0 items

In progress 0 items

Effect checked 0 items