top of page

When Incompetence Becomes A Health and Safety Policy

  • Writer: Alice
    Alice
  • Apr 1
  • 4 min read

Cracking the Code: When Competence Becomes a Liability


Dear Reader,


There is a point in certain environments where health and safety stops protecting people.


It starts protecting dysfunction.


Not intentionally.

Not explicitly.

But consistently enough that the pattern becomes undeniable.


What is framed as caution becomes delay.

What is framed as inclusion becomes tolerance for poor performance.

What is framed as safety becomes a mechanism for avoiding responsibility.


And in that shift, something dangerous happens.


Competence is no longer the stabilizing force.


It becomes the disruption.


A glowing cube in a dark, smoky room enclosed in cracked glass. Text: "When Incompetence Becomes a Health and Safety Policy."


WHERE IT BEGINS


In functioning systems:

• safety protects people

• standards protect outcomes


In failing systems:

• safety language protects incompetence

• standards are treated as pressure


You’ll hear:

• “we need to be careful”

• “let’s not rush”

• “we need to consider everyone”


But what is actually happening is:

avoidance disguised as responsibility.



COMFORT AS AN OPERATING MODEL


There are environments where:

• no one is allowed to feel challenged

• no one is expected to improve

• no one is held accountable in real time


Because discomfort is treated as harm.


So the system reorganizes itself around:

emotional comfort over functional integrity


And once that becomes the baseline,

anything that introduces clarity feels like disruption.



WHEN EXPERIENCE BECOMES A THREAT


There is another pattern that becomes visible across sectors.


Not just within a single organization—

but across industries, across roles, across environments.


People who have spent their entire careers inside one system

often learn how to function within it.


They learn its language.

Its pace.

Its unwritten rules.


They learn how to navigate it.


But navigation is not the same as understanding.


And when someone enters that environment

with experience drawn from multiple systems—


with exposure to different standards, different pressures, different ways of solving—

something shifts again.


Not because the new perspective is incorrect.


But because it is unfamiliar.


And unfamiliar, in a system that equates stability with sameness,

is often treated as risk.



THE FRICTION POINT


What happens next is predictable.


The person with broader experience:

• identifies inefficiencies quickly

• recognizes patterns that repeat across systems

• proposes solutions that bypass unnecessary complexity


And instead of that being received as value,

it is filtered through a different lens:

• “that’s not how we do things here”

• “you’re moving too fast”

• “we need to align with existing processes”


What is actually being defended is not the process.


It is the identity built around that process.



THE REAL ISSUE


Because when someone arrives with:

• pattern recognition

• transferable knowledge

• the ability to simplify


they are not just contributing.

they are revealing that complexity was never required to begin with.


And that is destabilizing for anyone

whose value has been built on navigating that complexity.



WHEN LEADERSHIP WAS FORMED IN A DIFFERENT WORLD


There is another layer that rarely gets examined.


Many of the structures still in place today

were shaped by people trained in a fundamentally different technological environment.


Not just earlier—

but structurally different.


Before:

• real-time global connectivity

• distributed systems operating simultaneously

• instantaneous access to information

• rapid iteration across industries


The frameworks made sense.


They were built for:

• slower feedback loops

• localized decision-making

• limited visibility


But the world did not stay there.


It moved.


Rapidly.



THE DISCONNECT


We now operate in environments shaped by:

• systems thinking

• cross-functional integration

• real-time data

• global interdependence


Yet many decision-making structures remain anchored in:

• hierarchy over flow

• process over outcome

• control over adaptability


This is not about age.


It is about:

whether the operating model has evolved with the environment.



WHERE IT BREAKS


Because when someone enters with:

• cross-sector experience

• modern pattern recognition

• the ability to move at the speed of current systems


they are not just faster.


They are:

aligned with the world as it exists now.


And that creates friction with structures

designed for a world that no longer exists.



WHEN ABUSE GETS REWARDED


Not all abuse looks like aggression.


Sometimes it looks like:

• chronic underperformance that others must compensate for

• repeated mistakes with no consequence

• passive obstruction

• learned helplessness that becomes normalized


And the people who:

• carry the load

• fix the problems

• maintain standards


are expected to:

absorb the impact without reaction


So the system ends up rewarding:

• those who take least responsibility

• those who resist pressure

• those who require accommodation without contribution



THE INVERSION


At a certain point, the roles flip.

• competence becomes “intense”

• clarity becomes “harsh”

• efficiency becomes “risky”


And incompetence becomes:

• protected

• accommodated

• sustained


Not because it works.


But because:

the system cannot function if it is exposed.



THE HEALTH AND SAFETY PARADOX


A system that claims to protect people

but allows:

• ongoing inefficiency

• hidden errors

• unaddressed gaps

• redistributed workload onto the competent


is not safe.


It is:

structurally unsafe.


Because what it avoids in discomfort

it creates in long-term instability.



THE PATTERN REPEATED


I’ve seen this across sectors, across roles, across environments.


Different industries. Same pattern.


The resistance is not to the solution.

It is to what the solution makes unnecessary.



WHAT EVERYTHING ANSWERS TO


At some point, you stop asking:


“Why is this being resisted?”


And you start asking:


“What does my presence make visible here that cannot be tolerated?”


Because in a functioning system, competence creates relief.


In a failing one, competence creates pressure.


And pressure, when it cannot be resolved,

is often misnamed as risk.


When a system rewards comfort over competence, it is not protecting people—

it is protecting its own inability to function.


Own your path ahead,

Alice

Comments


bottom of page