In some companies, being “good” means being always available.
Not available to design, improve, or prevent. Available to firefight.
In that environment, chaos stops being a problem and becomes culture: an operating mode that gives identity, prestige, and—most dangerously—a sense of control.
I call it a firefighting culture. And it doesn’t change with a speech. It changes when the system stops making firefighting the easiest path.
Culture isn’t what people say. It’s what the system rewards.
If the most valued person is the one who saves the day at the last minute, the real message is:
-
- planning has no status
-
- prevention is invisible
-
- saying “no” is risky
Culture is the outcome of thousands of micro-decisions the system pushes in one direction.
So when someone tells me “we need cultural transformation”, I translate it as:
> “We need to redesign signals, guardrails, and rituals so the right behavior becomes the easy behavior.”
## How I know chaos is identity (not just a bad week)
I hear it in daily language:
-
- “It’s always been like this.”
-
- “If I don’t run, it won’t happen.”
-
- “No time to do it right—only to put out fires.”
-
- “Planning is a luxury.”
-
- “The only thing that matters is fast response.”
-
- “Better not touch that.”
When that’s normal, the business pays a daily tax: burnout, quiet turnover, repeated errors, and margin erosion.
## The hero myth: when the organization becomes addicted to urgency
The “operational hero” is valuable. The problem is the system that makes them essential.
In firefighting cultures, heroes get rewarded for:
-
- absorbing exceptions
-
- solving “off the record”
-
- skipping steps to save the day
-
- doing magic with no trace
It works… until it doesn’t.
Because the system learns something lethal: urgency is a strategy.
## Cultural change without smoke: what I look at first
Before “values”, I look at three concrete things:
### 1) What earns prestige?
Not what’s written—what’s celebrated.
Do people celebrate heroic saves, or stable weeks with no surprises? Do they praise promises, or capacity protection?
### 2) What does the system punish?
Sometimes it punishes quietly:
Escalating risks “annoys”, asking for data “slows”, following process “looks slow”.
### 3) What is inevitable by design?
If the system forces improvisation, culture becomes improvisation—by survival.
## The classic mistake: trying to “change culture” without changing friction
Culture changes when friction changes.
If doing the right thing requires approvals, waiting, re-arguing priorities daily, and compensating for missing data, then the right thing is expensive—and expensive behavior gets abandoned.
Firefighting is cheap: react, decide hot, bypass steps, promise to calm.
The company designs its own addiction.
## Human indicators that a team is ready to leave chaos
I notice readiness when people start asking—without the vocabulary—for “system”:
-
- fatigue from surprises
-
- conversations about limits
-
- frustration with rework
-
- desire for clarity and predictability
-
- a key question: “How do we stop this from happening again?”
That question is the start of a learning culture.
## The real transition: from reacting to designing
Effective cultural transformation is a shift in center of gravity:
-
- react → anticipate
-
- improvise → decide with criteria
-
- essential individuals → a defensible system
-
- urgency as status → stability as achievement
And it must be visible in daily work.
## Rituals: where culture becomes practice
I don’t believe in rituals for ritual’s sake. I believe in rituals as mechanisms.
A useful ritual:
-
- has a clear cadence
-
- produces a visible commitment or decision
-
- leaves a trace (even minimal)
Without trace, everything falls back to memory and charisma.
## The silent lever: decision guardrails
In firefighting cultures, everything is negotiable—so everything gets negotiated late.
Guardrails aren’t rigidity. They’re speed with coherence.
I look for boundaries like:
-
- what can be promised and what cannot
-
- what risk forces escalation
-
- which exception is allowed and who approves
-
- what priority wins when there’s conflict
That reduces fights, anxiety, and inconsistency.
## Evidence culture is changing (without opinions)
I care about observable shifts:
-
- fewer end-of-week emergencies
-
- fewer “off the record” fixes
-
- fewer rescue messages
-
- more decisions recorded
-
- less single-person dependency
-
- more cross-team coherence
-
- a different pride: “this worked because the system made it easy”
When that pride appears, culture already changed—even if nobody announced it.
## The risk: confusing calm with slowness
Some leaders fear losing speed if they leave chaos.
The irony: chaos feels fast but is slow in outcomes—repeats errors, reopens decisions, drains energy.
Leaving chaos doesn’t mean being slow. It means being predictable.
## Closing
I don’t try to “convince” culture. I redesign the system so the right behavior becomes inevitable: what’s celebrated, what’s measured, what guardrails exist, and what rituals keep decisions coherent.
If you want, we’ll review it in 15 minutes: where chaos is currently rewarded, what frictions make the right behavior expensive, and what minimal changes would start producing stability without relying on heroes.
