startthat.work home

TC1-01 Five whys

Asks why repeatedly about one stated problem and records a single chain of causes, leaving a candidate root cause as a result.

Trace cause and test claimsEvidence: PracticePrimary technique, runs in step 5.3Strongest statement: show a link between things

What it does

Asks 'why' repeatedly about a problem to reach a cause treated as the root. Artefact: one chain of causes; read the final cause.

When to use it

Use when you need a quick first account of why a problem happened and one plausible causal path is enough to start an investigation.

When it does not fit

Different teams reach different answers, or the chain ends where the questioning happened to stop. It follows a single causal path.

Result format

The result is one chain of causes, written in order from the stated problem to the final cause, with each link answering why the one before it occurred. It ends by naming the final cause as the root cause.

Requirements on the material

PropertyRequirement typeRequirement
Content typeAlways appliesrequires=text
Unit of analysisAlways appliesrequires=topic
Appraises source credibilityApplies in some casesno

Not restricted on: Structure, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.

Minimum materialOne defined problem statement and at least one person or record able to answer each why.
Additional sources needednone
Not for (rules)stakes_tier=high-stakes & insight_wanted=cause :: a single causal path is not adequate for a high-stakes causal finding
Not for (text)Wrong choice when different teams reach different answers or the chain ends where the questioning happened to stop. Misused when the final answer is called the root cause without checking other causal paths.

Choosing and ordering

Kind of techniquePrimary technique, runs in step 5.3
Phase taganalyse
Other phase tagsnone
Kind of findingcause
Question answeredwhy
Strongest statement it supportsshow a link between things
Needs as input
Makes as output
Must exist firstNone
Loop targetreturn to analyse

Library checks by stakes

Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.

StakesCheckPerson involvedCounts as a different method
exploratoryassumption and limitation statementnoneno
decision-informingassumption and limitation statementnoneno
decision-informingalternative explanations checknoneno
high-stakesassumption and limitation statementnoneno
high-stakesalternative explanations checknoneno
high-stakessecond technique with different assumptionsnoneconditional
high-stakesexpert reviewneededno

Failure modes and limits

Model suitabilityhuman judgement required
Typical model failureProduces a tidy chain of five answers that stops at a plausible but untested cause and presents it as the root cause.
Error sourcesinput data; coder or rater judgement; expert opinion
Certainty limitsCertainty drops when answers rest on opinion and not on records, when the chain follows one of several causal paths, or when different people reach different chains (inconsistency and indirectness).

Evidence and tag basis

Practice. A peer-reviewed commentary finds no evidence of effectiveness, recommends against its use for root cause analysis in patient safety, and reports a worked example with 30 causal pathways of which the technique would address one or two. Figures were read through a summarising tool and need checking. (BMJ Quality and Safety 2017;26:671, on the five whys)

Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.