Safety Always, Not Safety First: Why Systems, Not Slogans, Decide Outcomes
- Luke Dam
- 2 hours ago
- 4 min read

For decades, organisations have proudly declared Safety First.
It appears on posters, policies, induction slides, and corporate values. It is usually spoken with sincerity and defended with conviction.
And yet, serious incidents, repeated failures, and organisational harm continue to occur — often in organisations that say Safety First the loudest.
This isn’t a contradiction.
It’s a clue.
The Problem With “Safety First”
At face value, Safety First sounds decisive. But language shapes how we think, and how we think shapes how we design work.
“First” implies a list of priorities.
And priorities can move.
In real work, safety competes with:
time
production
cost
customer demand
reputation
When pressure increases, priorities shift. Safety becomes something people are expected to “hold onto” while everything else accelerates.
That expectation is unrealistic- and unfair.
People Don’t Choose Unsafe Work
One of the most persistent myths in safety is that incidents occur because people failed to prioritise safety.
Decades of investigation evidence tells a different story.
People involved in incidents are rarely reckless. They are often:
experienced
capable
trying to do the right thing
adapting to the conditions around them
Their actions usually make sense at the time.
This matters.
Because if behaviour made sense, then the system allowed it to make sense.
What ICAM Shows Us
ICAM (Incident Cause Analysis Method) consistently demonstrates that incidents are not caused by single actions or bad decisions in isolation.
They emerge from systems operating under pressure.
ICAM shifts the question from:
“Who failed?”
To:
“How did our system make this outcome possible?”
That shift is profound.
It moves responsibility away from individuals with the least control, and toward the conditions created by organisations.
Safety Is an Outcome, Not a Priority
Safety is not something people do instead of working.
Safety is what results when work is:
well designed
realistically planned
adequately resourced
supported by leadership
protected by robust controls
When these elements are present, safe outcomes emerge.
When they are absent or degraded, harm becomes possible, regardless of how often safety is declared a priority.
This is why Safety Always is a more accurate framing than Safety First.
Pressure Changes What Feels Reasonable
Pressure does not make people careless.
Pressure changes what feels reasonable.
Under time and production pressure, people:
narrow their focus
rely on experience
accept higher levels of risk
skip steps that seem unnecessary
This is not a character flaw.
It is a human adaptation.
Systems that rely on people “making the right choice” under pressure are inherently fragile.
The Myth of the Unsafe Act
When incidents occur, organisations often stop the investigation at the behaviour:
failure to follow procedure
unsafe act
human error
This feels satisfying.
It provides a clear cause and a quick fix.
But it also stops learning.
Behaviour is rarely the cause of incidents. It is the symptom of deeper system conditions.
ICAM treats behaviour as something to be explained, not something to be blamed.
That distinction is where prevention lives.
Drift Happens Quietly
Organisations rarely jump from safe to unsafe.
They drift.
Controls erode. Shortcuts succeed. Exceptions become normal.
Success hides risk.
Over time, work looks efficient- right up until it fails.
This is why organisations are often shocked by incidents. They believed they were in control.
They weren’t reckless.
They were comfortable.
Leadership Shapes Risk, Often Invisibly
Most of the conditions that shape safety are created far from the frontline.
Leadership decisions about:
schedules
resourcing
staffing
incentives
priorities
Quietly define what is possible- and what is not.
These decisions are rarely labelled “safety decisions”.
But ICAM shows they are often the most safety-critical decisions of all.
Why Compliance Isn’t Enough
Many organisations respond to incidents with more rules, more training, and more reminders.
This assumes that compliance equals control.
It doesn’t.
Compliance tells us what should happen.
Capability determines what can happen- especially under pressure.
Safe systems do not rely on memory, vigilance, or heroics.
They absorb pressure so people don’t have to.
Learning Without Blame
Blame feels decisive.
Learning is harder.
Blame closes inquiry. Learning opens it.
ICAM creates space for learning by:
assuming actions made sense at the time
examining system conditions
focusing on failed or absent defences
Organisations that learn well don’t just close investigations.
They change systems.
Safety Always Is Not a Slogan
Safety Always is not a phrase to replace another phrase.
It reflects a different way of thinking:
Safety is not negotiable because it is not a trade-off
Safety is built into work, not layered on top
Safety is a leadership responsibility, not a frontline burden
When safety is treated as a condition rather than a priority, people stop being asked to choose between safety and success.
Beyond Safety
The same system conditions that produce safety incidents also underpin:
bullying and harassment
quality failures
safeguarding breakdowns
ethical breaches
ICAM is not just a safety method.
It is a framework for organisational learning.
What Maturity Really Looks Like
Mature organisations don’t talk about safety more.
They design better systems.
They:
resolve trade-offs upstream
listen to weak signals
treat deviation as information
protect learning from blame
Safety doesn’t need to be prioritised.
It emerges.
A Final Thought
When safety depends on people making the right choice under pressure, the system has already failed.
Safety is not first.
Safety is not last.
Safety is how work gets done.
If we want different outcomes, we must design different systems.




Comments