Some of the most expensive recurring problems survive because the organisation keeps solving the problem presented to it instead of asking whether something else is actually happening.
That is one of the surprisingly useful leadership lessons buried inside Die Hard.
On Christmas Eve, terrorists seize Nakatomi Plaza, take hostages and apparently make political demands. Police respond. The FBI arrives. Procedures swing into action. Everyone begins solving what appears to be a hostage crisis.
Except Hans Gruber is not really conducting a terrorist operation.
He is committing a robbery.
And that distinction changes everything.
For CEOs exhausted by recurring problems, Die Hard offers a powerful lesson in karamawari: competent action against an incorrectly framed problem can create enormous activity without producing the outcome you actually need.
The First Explanation Can Become a Trap
Hans Gruber gives the authorities a story.
They accept enough of it to begin acting.
That is exactly how organisations can become trapped by recurring problems.
Customer complaints rise.
"It is a service problem."
Margins fall.
"It is a cost problem."
A transformation slips.
"It is an execution problem."
Employees leave.
"It is a retention problem."
A system repeatedly fails.
"It is a technology problem."
Each diagnosis may be plausible. There may even be considerable evidence supporting it.
That is what makes misdiagnosis dangerous.
Once the problem has a name, the machinery of the organisation starts moving.
Budgets appear. Consultants arrive. Projects launch. KPIs are created. Executives are assigned. Technology is purchased.
The organisation becomes extremely busy solving the explanation.
Hans Gruber Needs the Authorities to Behave Predictably
Gruber's plan becomes particularly interesting through a karamawari lens because he does not merely anticipate the authorities' response.
He needs it.
He expects established procedures to produce predictable behaviour, including the FBI cutting the building's power, which ultimately helps him overcome the vault's final electromagnetic lock.
The people trying to stop him inadvertently advance his plan.
Organisations can create similar traps.
A business unit misses its numbers, so leadership imposes tighter controls.
People respond by becoming more cautious.
Decisions slow.
Performance deteriorates further.
Leadership sees worsening performance and concludes that even stronger controls are required.
Or employees stop raising problems because leaders react defensively.
Management sees fewer reported problems and concludes things are improving.
Eventually a serious failure occurs.
The response is more reporting.
People become even more careful about what they report.
The attempted solution strengthens the conditions creating the problem.
That is karamawari at its most expensive.
John McClane Has One Advantage: He Is Inside the Problem
John McClane understands something the authorities outside the building cannot easily see.
Reality.
He sees what is actually happening.
He encounters the people involved, observes their behaviour, gathers fragments of information and gradually develops a different understanding of the situation.
This matters for CEOs.
Recurring problems are often diagnosed from too far away.
Board papers.
Dashboards.
Executive summaries.
Incident reports.
Consultant presentations.
All are useful, but every layer compresses reality.
The people closest to the problem often possess fragments that never survive the journey upwards.
The frontline employee knows the workaround.
The customer knows where the experience actually fails.
The middle manager knows which target drives dysfunctional behaviour.
The analyst knows which number everyone quietly distrusts.
The project team knows which deadline became impossible six months ago.
Senior leadership sees the impact.
The organisation sees the conditions.
Effective diagnosis requires connecting both.
Do Not Confuse Confidence With Understanding
Deputy Police Chief Dwayne Robinson is a useful organisational character because he repeatedly forms confident conclusions from incomplete information.
CEOs should recognise the danger.
Under pressure, organisations reward certainty.
"What is happening?"
"What caused it?"
"When will it be fixed?"
Those questions demand answers, often before sufficient evidence exists.
Someone produces a plausible explanation.
The explanation becomes the diagnosis.
The diagnosis becomes the programme.
The programme becomes expensive.
And once millions have been committed, questioning the original diagnosis becomes increasingly uncomfortable.
The organisation stops investigating whether it is right and starts proving why it must be.
Recurring problems should make leaders less certain, not more.
If three competent solutions have failed, the fourth should not begin with:
"What should we try next?"
It should begin with:
"What have all three attempts assumed to be true?"
The Failed Fixes Are Evidence
This is where Die Hard becomes particularly useful.
Every interaction reveals something about Gruber's real objective.
Recurring problems do the same.
Suppose an organisation has tried restructuring, new technology, training, additional governance and replacing leadership.
The problem returns.
Those failed solutions are not merely disappointments.
They are diagnostic evidence.
Ask what each solution changed.
Then ask what every solution left untouched.
Perhaps reporting changed but incentives did not.
Processes changed but decision rights did not.
Leadership changed but expectations did not.
Technology changed but workarounds survived.
Structure changed but assumptions remained.
Somewhere among those untouched conditions may be the mechanism recreating the problem.
Sometimes the Response Is Part of the System
The deepest lesson from Die Hard is not simply "diagnose better."
It is more uncomfortable.
Your organisation's response to the problem may itself be one of the conditions keeping the problem alive.
Every recurrence triggers another intervention.
Another committee.
Another control.
Another transformation.
Another restructure.
Another expert.
Another heroic rescue.
Eventually the organisation can spend so much time responding to recurrence that responding becomes part of how the business operates.
The wheel spins faster.
Costs accumulate.
People work harder.
And the underlying condition remains.
That is 空回り, karamawari.
The lesson from Nakatomi Plaza is simple: before committing more resources to solving the problem in front of you, make sure you understand the game you are actually playing.
Because the most dangerous recurring problem may not be the one your organisation keeps failing to solve.
What if the problem your leadership team has been fighting for years is actually the problem your organisation has been inadvertently trained to see?
0 Comments