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.
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
| Property | Requirement type | Requirement |
|---|---|---|
| Content type | Always applies | requires=text |
| Unit of analysis | Always applies | requires=topic |
| Appraises source credibility | Applies in some cases | no |
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 material | One defined problem statement and at least one person or record able to answer each why. |
|---|---|
| Additional sources needed | none |
| 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 technique | Primary technique, runs in step 5.3 |
|---|---|
| Phase tag | analyse |
| Other phase tags | none |
| Kind of finding | cause |
| Question answered | why |
| Strongest statement it supports | show a link between things |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return 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.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | assumption and limitation statement | none | no |
| decision-informing | assumption and limitation statement | none | no |
| decision-informing | alternative explanations check | none | no |
| high-stakes | assumption and limitation statement | none | no |
| high-stakes | alternative explanations check | none | no |
| high-stakes | second technique with different assumptions | none | conditional |
| high-stakes | expert review | needed | no |
Failure modes and limits
| Model suitability | human judgement required |
|---|---|
| Typical model failure | Produces a tidy chain of five answers that stops at a plausible but untested cause and presents it as the root cause. |
| Error sources | input data; coder or rater judgement; expert opinion |
| Certainty limits | Certainty 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). |
Related techniques
- pairs with TC1-02 Fishbone diagram (Ishikawa diagram, cause and effect diagram): the fishbone diagram shows the many causal paths that one why chain leaves out
- pairs with TC1-03 Fault tree analysis Also serves: Assess actors, options and risks.: a fault tree tests whether combinations of events, not one chain, cause the problem
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.