The core idea
Root-cause analysis is often used as shorthand for investigating why a problem occurred. In complex work there may be several interacting contributing conditions rather than one root cause. NHS system-based learning guidance provides a useful example of examining work, context and interactions; our HR application is an editorial adaptation, not a clinical investigation protocol. Asking why repeatedly can help inquiry, but the answers need evidence.
Source and attribution [1]Using it in practice
Define the event or recurring pattern and reconstruct what happened using records and accounts from those involved. Ask what information, resources and constraints were present at the time. Distinguish hindsight from what people could reasonably know. Test competing explanations and look at normal successful work as well as failures. Choose actions that change the conditions, then evaluate whether the problem becomes less likely.
An example, not a reported case
Worked example · illustrative
A fictional employer repeatedly loses starters before their first paid shift. One explanation is poor commitment. A review instead finds delayed access approval, inconsistent contact details and uncertainty about available work. HR checks these observations across cases and with new starters. A pilot clarifies ownership of the handover and sends a confirmed first-shift plan. The evaluation tracks delays and actual starts rather than counting reminder emails.
What to watch for
A neat five-whys chain can reflect the investigator’s preferred story. Avoid ending at human error as if that explains the conditions that shaped action. Learning work does not replace appropriate accountability or formal processes. The purpose and handling of interviews should be clear, particularly where people may fear blame.
Test rather than assume
For each proposed cause, ask what evidence would be expected if it were true and what could contradict it. Look for cases where the same condition existed without the problem. This can reveal missing factors or an overly simple explanation.
Design a stronger action
A reminder or retraining may be insufficient if the system still makes the wrong action easy. Consider clearer ownership, better information and redesigned handovers. Assign an owner and review whether the action changed the relevant condition, not merely whether it was completed.
Take it into your next conversation
Three useful questions.
- What question can this method answer, and what can it not establish?
- Are the comparison, observation period and assumptions defensible?
- What decision follows, and how will its consequences be reviewed?
Go to the evidence
Sources & attribution
[1] NHS England: system-based learning response toolkit ↗
The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.
Published 2026-09-20 · Reviewed 2026-09-20. Editorial approach