When the same people repeatedly save the day, CEOs should be asking why the day keeps needing to be saved.
Most organisations admire heroic performance.
A major project begins to unravel and an experienced leader steps in. A critical customer threatens to leave and a team works through the weekend. A deadline looks impossible until several people put everything else aside and somehow get it across the line.
Disaster avoided.
Relief follows. Then recognition.
The people involved are praised for their commitment, resilience and willingness to go above and beyond.
And they probably deserve it.
But there is a danger hidden inside that applause.
The rescue can become more interesting than the reason it was necessary
Heroic recoveries make compelling stories because they have protagonists, jeopardy and resolution.
Systems rarely do.
Nobody tells an exciting story about a well-designed process that prevented the crisis from occurring.
That creates an unusual leadership bias.
We notice the extraordinary effort required to recover performance far more readily than the ordinary organisational conditions that made extraordinary effort necessary.
The project was saved.
But why was it struggling?
The customer stayed.
But why did the relationship reach breaking point?
The deadline was met.
But why did meeting it require people to work until midnight?
Once the immediate problem disappears, the urgency to answer those questions often disappears with it.
Success can hide failure
This is where heroic recovery becomes particularly dangerous.
A successful outcome can persuade leadership that the system worked.
Sometimes it demonstrates precisely the opposite.
Imagine a project scheduled to finish on Friday. It finishes on Friday, so the dashboard remains green.
But twenty people worked nights and weekends for a month. Decisions were repeatedly escalated. Other priorities were abandoned. Senior executives personally removed obstacles. Experienced employees compensated for broken processes.
The result says success.
The conditions say something very different.
If leadership measures only the outcome, the organisation learns the wrong lesson.
Instead of asking what made the extraordinary effort necessary, it celebrates the extraordinary effort itself.
Heroism can become an invisible operating model
This is where an occasional rescue can become a recurring organisational problem.
People learn what the organisation values.
If preventing problems attracts little attention while rescuing them attracts recognition, rational people notice.
If the person quietly removing systemic weaknesses receives less visibility than the executive dramatically resolving the resulting crisis, the organisation inadvertently establishes a hierarchy of value.
Fire prevention becomes invisible.
Firefighting becomes leadership.
More dangerously, management can begin incorporating heroic capacity into its assumptions.
“We'll find a way.”
“The team always delivers.”
“Sarah will sort it out.”
“We've handled worse.”
What began as exceptional effort gradually becomes expected capacity.
Budgets become tighter. Timelines remain unrealistic. Dependencies go unresolved. Decision bottlenecks persist. Resources stay constrained.
Why change the system when capable people continually compensate for it?
The economics of heroism are rarely visible
For CEOs and boards, this isn't merely a cultural concern.
It has a commercial cost.
Every rescue consumes capacity that could have been deployed elsewhere.
Senior management attention is diverted. Strategic work is delayed. Employees compensate for structural weaknesses with additional labour. Other projects inherit the consequences of resources being redirected. Burnout and turnover risks increase.
Yet much of that cost never appears beside the problem that created it.
The project may show as successfully delivered while the cost of rescuing it is dispersed throughout the organisation.
That makes heroic recovery deceptively cheap.
The organisation sees the avoided failure.
It doesn't necessarily see the opportunity cost of avoiding it.
The hero may be part of the warning system
None of this means organisations should stop recognising people who step forward when things go wrong.
They should.
The mistake is allowing recognition to become the end of the conversation.
Every heroic intervention should trigger another question:
What did this person have to overcome that our system should not have required them to overcome?
Look behind the hero and you may find recurring conditions: unclear decision rights, conflicting incentives, unrealistic planning assumptions, weak interfaces between functions, information arriving too late, chronic resource constraints, fear of escalation or processes that work only when experienced people circumvent them.
Those conditions matter because the hero eventually goes home.
The system stays.
From heroic recovery to Karamawari
This is one way organisations drift into 空回り (karamawari): enormous effort creates motion without progress.
A problem appears.
People compensate.
The organisation recovers.
Heroes are celebrated.
The conditions remain.
Then the cycle begins again.
The organisation can become extraordinarily competent at solving the consequences of problems it remains surprisingly poor at preventing.
For CEOs and boards fed up with recurring problems, that distinction matters.
The next time somebody saves the day, recognise them.
Then investigate why they had to.
Because the ultimate measure of a strong organisation isn't how many heroes it can produce; it's how many recurring crises no longer require one.
So when you look at the heroes your organisation celebrates most, what recurring weaknesses might they actually be protecting you from seeing?