Skip to content

Free template

Updated

5 Whys template

The 5 Whys is a way to find the cause of a problem by asking why it happened, writing one answer, checking that answer against the facts, and asking why again about it until you reach a cause you can remove. Taiichi Ohno described it in Toyota Production System (1988) with a machine that stopped because a fuse blew, which he traced through an overloaded bearing and a worn lubrication pump to a missing strainer. Five is a rule of thumb, not the rule. This template has a problem statement in four parts, a why chain where each row has its evidence, a verified or disproved mark and a branch letter (a why with two true answers is followed both ways), the root causes, and countermeasures with an owner and a date. The Excel version checks the chain for you: answers built on an unchecked or disproved answer, a why that names a person, a root cause outside your control, and a root cause with no permanent fix. The PDF has the blank worksheet, a filled-in example and a page on how to run it.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Page 1 of the 5 Whys templateFields for area, date, team and facilitator, a four-part problem statement, a why chain table with branch, why number, explains, answer, evidence, verified and root cause columns, and boxes for root causes and countermeasures.
Problem statement in four partsBranching why chainEvidence and verified columnRead-back sentencesChecks for weak linksCountermeasures by typeEffectiveness checkWorked example
Filled-in 5 Whys template: hose assemblies leaking at the pressure test
The same sheet filled in with the worked example (page 2 of the PDF, illustrative numbers). Open full size (opens the picture in a new tab)

When to use it

When to use the 5 Whys

  • A problem with a traceable chain of cause and effect: a machine stoppage, a defect, a missed shipment.
  • Soon after the problem happens, at the line, while the evidence is still there to check.
  • Inside a bigger method: the root cause box of an A3, the root cause step of an 8D, or the analysis in a root cause analysis report.
  • On the most likely branches of a fishbone diagram, once the team has narrowed the possible causes.
  • Not on its own for problems with many interacting causes or no facts yet: start with a fishbone diagram, an is / is not analysis or the data.

How to fill it in

  1. 1

    Write the problem statement in four parts

    What happened, where, when, and how big against normal. No cause and no name in it. The Excel flags a statement with a part missing.

  2. 2

    Ask why, and write one answer per row

    Each answer is a fact about the process or the equipment, not an opinion. Write the row it explains in the "Explains" column (blank for the first why).

  3. 3

    Check each answer before you go on

    Go to the gemba and write what confirms it: a measurement, a record, a photo. Mark it verified, not yet, or disproved. Do not build the next why on an answer that is not verified.

  4. 4

    Branch when there are two true answers

    Give the second answer its own branch letter and follow both chains. The example below has two.

  5. 5

    Read the chain back

    Say each answer with "therefore" and the answer it explains. If the sentence does not hold, the link is wrong. The Excel builds these sentences for you.

  6. 6

    Stop at a verified cause you can act on

    Removing it should stop the problem coming back. If the next why is outside your control, such as a customer's demand, the answer before it is your root cause.

  7. 7

    Act, then check that it worked

    Contain the problem first, give every root cause a permanent fix with an owner and a date, carry the fix to similar lines, and measure the problem again after a set time.

The checks

What the Excel checks on every row

The checks answer the known weak points of a single why chain: one cause where there are several, answers nobody verified, and stopping at a person.

  • Evidence

    Flags
    Verified with no evidence written; built on an answer not yet verified or disproved
    Why it matters
    One unchecked answer sends the rest of the chain the wrong way.
  • Blame words

    Flags
    An answer with "operator", "forgot", "human error" and similar words (the list is editable)
    Why it matters
    People make mistakes the process allows. Ask why it allowed it.
  • Links

    Flags
    An answer that explains a row that does not exist or a later row; a why number out of step
    Why it matters
    The chain must run from the problem to the cause without gaps.
  • Root cause

    Flags
    Not verified, outside your control, or has another why after it
    Why it matters
    You can only remove a cause you have proved and can change.
  • Countermeasures

    Flags
    A root cause with no permanent fix; an action late or done without a date
    Why it matters
    Containment alone lets the problem come back.

A filled-in example

Illustrative, not a benchmark

An example (illustrative): hydraulic hose assemblies leaking at the end-of-line pressure test on line 2. 38 of 1,200 assemblies failed from Monday to Wednesday (3.2%), against 0.3% the month before. The Excel Example sheets and PDF page 2 hold the same rows.

The example chain: one problem, two branches

  • A: crimped above the upper limit: 31 leaking assemblies
  • B: within limits, hose short of full insertion: 7 leaking assemblies
  1. ProblemBranch A: 38 of 1,200 assemblies leaked at the pressure test (3.2%)
  2. Why? (1)31 of the 38 leaking fittings had a crimp diameter above the upper limit.
  3. Why? (2)The die set was worn.
  4. Why? (3)Nobody checks die wear: 61,000 crimps since it was fitted.
  5. Why? (4)The crimper is not on the PM schedule.
  6. Why? (5)Root cause A, after five whysTools bought under the capital threshold are never registered as assets.
  1. ProblemBranch B: the same 38 leaks
  2. Why? (1)The other 7, crimped within limits, had the hose short of full insertion.
  3. Why? (2)There is no insertion-depth mark on the hose.
  4. Why? (3)The marking gauge was not put back after the line move in May.
  5. Why? (4)Root cause B, after four whysThe line-move checklist has no item for station gauges.

38 of 1,200 hose assemblies leaked at the end-of-line pressure test, 3.2 percent against 0.3 percent the month before. Why 1 has two true answers: 31 fittings were crimped above the upper limit and 7 had the hose short of full insertion. Branch A ends after five whys: tools bought under the capital threshold are never registered as assets. Branch B ends after four: the line-move checklist has no item for station gauges.

Every answer was checked before the next why; the operator setting was checked against the log and disproved. Two root causes, two permanent fixes, and the check is a leak rate of 0.5% or less for 4 weeks.
  • Why 1 has two true answers, so the chain branches. A: 31 of the 38 leaking fittings had a crimp diameter above the upper limit. B: the other 7, crimped within limits, had the hose short of full insertion when cut open (31 + 7 = 38).
  • Branch A: the operator setting was checked against the log and disproved. The die set was worn; nobody checks die wear (61,000 crimps since it was fitted); the crimper is not on the PM schedule; tools bought under the capital threshold are never registered as assets. Root cause after five whys.
  • Branch B: there is no insertion-depth mark on the hose; the marking gauge was not put back after the line move in May; the line-move checklist has no item for station gauges. Root cause after four whys.
  • Six countermeasures: contain (re-test all 1,200), two fixes now (new die set, gauge back), a permanent fix for each root cause, and a check of lines 1 and 3 for other unregistered tools.

10 answers, 9 verified and 1 disproved, 2 branches, 2 root causes, each with a permanent fix. One permanent fix is 1 day late and the Excel flags it. The effectiveness check is a leak rate of 0.5% or less, down from 3.2%, measured for 4 weeks after the permanent fixes.

Common mistakes

  • Stopping at a person

    "Operator error" ends the search too early. In the example the operator's setting was checked and disproved; the real causes were a missing PM routine and a missing checklist item.

  • Guessing answers in a meeting room

    Every answer needs evidence next to it. An unchecked answer sends the whole chain the wrong way.

  • Following one path when there are several causes

    If a why has two true answers, follow each one. It is the main point of A J Card's 2017 critique of the method.

  • Counting to five

    Stopping at five because the form has five rows is as wrong as stopping at three. Stop at a verified cause you can remove.

  • Jumping to a favorite fix

    The countermeasure should remove the root cause on the sheet, not the first idea someone had.

  • Containment with no permanent fix

    Sorting parts protects the customer this week. Without a fix for the root cause, the problem comes back.

In LeanSuite

Use this as a Lean Studio board

The same method is one of the 30 ready-made board templates in Lean Studio, LeanSuite's whiteboard: 5 Whys, drill from a symptom to its root cause in five steps.

  • Start from the 5 Whys template: the problem sits at the top and five stickies hang below it, joined by arrows.
  • Type each answer on its sticky; add a branch with a second column of stickies when one why has two causes.
  • Put the countermeasure on a coloured sticky at the bottom and save the board to My templates for the next problem.

Worked example · sample data

The sample board starts with a 40-minute stoppage on press 2 on Tuesday. Why? The clamp lost pressure. Why? A hydraulic hose split. Why? The hose had been rubbing on the guard. Why? The guard was refitted without its clip. Why? The refit instruction does not mention the clip. Each answer is something the maintenance technician could see or check, and read backwards with 'therefore' the chain holds. Stopping at the hose would have meant a new hose and the same failure in a few months; the fifth why reaches a document the team can change. The countermeasure at the bottom is to update the refit instruction and add the clip to the CILR check, so the next operator inspecting the press looks for it.

A press stoppage at the top, five linked why stickies down to a missing clip in the refit instruction, and the countermeasure at the bottom. Sample data.

Open this board in LeanSuite

5 Whys is one of the 30 ready-made boards in Lean Studio, LeanSuite's whiteboard. Try LeanSuite in your browser, or run it on your own lines for 90 days.

What Lean Studio is

How to run a 5 Whys session

  1. 1Start from one problem, one occurrence: 'Press 2 stopped for 40 minutes on Tuesday', not 'press 2 keeps stopping'.
  2. 2Go to where it happened with the people who were there, and answer each why with something they saw or can check, not with an opinion.
  3. 3Write each answer on its own sticky and read the chain backwards: 'therefore' should link every step. If it does not, the chain has a gap.
  4. 4Stop when the answer is a process, standard or system the team can change. Five is a guide; some chains need three, some seven.
  5. 5Write the countermeasure against the last why and give it an owner and a date. Then check, weeks later, that the problem has not returned.

Common mistakes

  • Stopping at the first cause that suggests a fix: a new hose is a repair, not a countermeasure.
  • Answering a why with a person's name. 'The operator forgot' asks for a next why: why was it possible to forget?
  • Branching into three causes at each level, which is a fishbone, not a 5 Whys. Pick the likeliest branch and follow it.
  • Doing it at a desk from memory. Each answer should be checkable on the floor.
  • Not verifying. A chain that reads well is a hypothesis until the countermeasure holds.

Where it goes next in LeanSuite

  • Add a 5 Whys section to any phase of a Kaizen project and push its countermeasure into the action plan with an owner and a due date. Kaizen & Projects
  • A tag raised on the floor that keeps coming back can be escalated into a Kaizen or A3 project in one click, keeping the tag's history. Daily Issue Management
  • The RCA Agent drafts the 5 Whys from a problem description and attached manuals, for the team to edit. AI Root Cause Analysis

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

In LeanSuite you describe the problem in plain words and attach what you know, the RCA Agent drafts the 5 Whys, 5W1H and fishbone from it, and you edit the result and send the countermeasures to the action plan.

See it in a 45-minute demo

FAQ

5 Whys template: common questions

  1. No. Five is a rule of thumb from Ohno's example. In the worked example one branch takes five whys and the other four. Stop when you reach a verified cause you can remove, or when the next why is outside your control.

  2. Follow each true answer as its own branch. In the Excel, give the second answer a new branch letter and write which row it explains; the sheet counts the branches and checks each chain separately.

  3. Check it with evidence at the gemba before asking the next why, then read the chain back with "therefore": the die set was worn, therefore the crimp diameter was above the limit. If an answer cannot be confirmed, mark it not yet and do not build on it.

  4. On problems with many interacting causes, or when nobody has the facts. A 2017 paper in BMJ Quality and Safety by A J Card criticises the single chain for exactly this. Start with a fishbone diagram, an is / is not analysis or the data, and use the 5 Whys on the likely branches.

  5. A fishbone diagram lays out many possible causes in categories; the 5 Whys follows a few of them in depth. The root cause analysis report is the full record around the analysis, with containment, timeline and sign-off. Use them together.

More free templates

All templates
Browse all 199 templates

Can't find the template you need?

Tell us what you're looking for. We'll make it and send it to your inbox, free.

A shift handover sheet, a red tag log, a changeover checklist for one machine: if your team uses it on the floor, ask.

By sending this form you agree to our Terms of Service and Privacy Policy.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.