SafetyPulse by ICAM Australia
Method choice5 min read · 2026-07-04

ICAM vs 5 Whys: choosing the right investigation method, and when to escalate

Not every event deserves a full ICAM investigation, and pretending otherwise is how investigation quality dies. Teams drowning in process for minor events have nothing left for the ones that matter. The real skill is matching depth to potential consequence, and keeping a clean escalation path when an event turns out to be bigger than it looked.

What 5 Whys does well

5 Whys is fast, teachable and honest about its ambition: follow the causal chain from the event backwards until you hit a condition worth fixing. For low-consequence events with contained causal chains (a delivery process failure, a repeated minor equipment fault) a disciplined 5 Whys closed out in a day beats an ICAM investigation that never gets resourced.

Its known weakness is single-track thinking: one chain of whys finds one cause, and complex events never have one cause. A branching 5 Whys (where each answer can spawn multiple whys, and terminal causes are tagged against the ICAM factor families) keeps the speed while softening the tunnel vision.

Where ICAM is non-negotiable

ICAM scopes by credible worst outcome, not actual harm. The near-miss that could have killed someone gets the full method: PEEPO evidence planning, the three-layer timeline, factor analysis across DF / IT / TE / OFT, and recommendations aimed at defences and organisational factors.

The middle tier most teams are missing

Between the two sits a streamlined ICAM (the same factor discipline, a reduced step set) for events that warrant more than 5 Whys but not a Level 3 investigation. In SafetyPulse this is ICAM Lite: event description, severity and SIF-potential call, evidence, factors, recommendations, report. Same vocabulary, proportionate effort.

Escalation is the feature that matters

The most important question isn't "which method?" It's "what happens when we chose wrong?". A 5 Whys that uncovers SIF potential must escalate to ICAM without re-keying the work: the evidence, timeline entries and factors already captured should carry across. If your process (or platform) makes escalation expensive, teams will quietly stay shallow. SafetyPulse escalates 5 Whys → ICAM Lite → full ICAM in one click, record intact.

Rule of thumb: choose by credible worst outcome, start proportionate, and make sure the road to more rigour is downhill.

SafetyPulse is investigation software built on the ICAM method, by the people who train it. See it against your own incident types.

Book a demo

Training

5 Whys Incident Investigation Workshop: ICAM Australia

More resources

Incident investigation software: what to look for in an ICAM-aligned platformA practical checklist for Australian safety teams evaluating incident investigation software: methodology fidelity, data residency, evidence traceability and measurable quality. Running an ICAM investigation digitally: from PEEPO to final reportHow a full ICAM investigation flows through a digital platform: planning, PEEPO evidence, factual timeline, contributing factors, recommendations and the final report.

All resources