The recurring problem your leadership team barely notices may be carrying more economic weight than the enormous problem consuming the entire board agenda.
A teaspoon is tiny.
You could hold one comfortably between two fingers.
But if that teaspoon contained neutron-star material, it would weigh billions of tonnes on Earth.
The reason is density.
An extraordinary amount of matter has been compressed into an extraordinarily small space.
There is a useful lesson here for CEOs dealing with recurring problems.
We tend to judge problems by their visible size.
How many people are affected?
How frequently does it happen?
How many complaints have we received?
How many hours of downtime did it cause?
How prominent is it on the executive dashboard?
But size and weight are not the same thing.
And neither are frequency and economic consequence.
Some problems are organisationally dense
Imagine a recurring reconciliation error that appears only four times a year.
Operationally, it looks small.
Perhaps a handful of people spend two days fixing it each time.
The obvious calculation might therefore be:
Eight days of effort. Annoying, but hardly a CEO problem.
Except the error affects a regulatory submission.
Now the weight changes.
The remediation effort might be small, but compressed inside that seemingly minor problem are regulatory exposure, executive accountability, reputational damage and potentially significant financial consequences.
The visible incident is the teaspoon.
The risk sitting inside it is the neutron star.
Frequency can fool us
Recurring problems are often prioritised using frequency.
Something happening every day attracts attention.
Something happening twice a year can appear less important.
That is perfectly rational until consequence enters the equation.
A payment failure affecting a few customers might happen rarely.
But if the same weakness could one day affect thousands, the historical frequency tells you very little about the exposure.
A manufacturing defect might occur only occasionally.
But if it appears in a safety-critical component, counting incidents alone badly understates its importance.
A senior employee might repeatedly intervene to rescue a failing process.
The intervention takes twenty minutes.
No customer notices.
No SLA is breached.
Nothing appears on the risk dashboard.
Tiny problem.
Except perhaps the entire process depends upon knowledge held inside that person's head.
The twenty-minute workaround is hiding an enormous dependency.
Remove the person and suddenly the teaspoon weighs billions of tonnes.
The visible cost is often the lightest part
This is where recurring problems become commercially deceptive.
Leadership teams can become very good at calculating the obvious cost.
Rework.
Overtime.
Refunds.
Downtime.
Remediation.
Additional headcount.
But recurring problems can carry much denser costs.
Management attention.
Delayed investment.
Lost customer confidence.
Control exposure.
Accumulated technical debt.
Strategic distraction.
Dependence on particular employees.
Opportunity cost.
Reduced organisational resilience.
And perhaps most dangerously, the possibility that today's minor incident is evidence of a condition capable of producing tomorrow's major one.
That changes the question.
Instead of asking:
"How much did this incident cost?"
Ask:
"What economic exposure is concentrated inside the conditions that allowed this incident to occur?"
Those are very different calculations.
A workaround can make a heavy problem look light
Capable organisations are particularly vulnerable to this illusion.
Why?
Because capable people absorb weight.
They catch errors before customers see them.
They work late to recover deadlines.
They remember undocumented exceptions.
They know who to call.
They escalate around broken processes.
They reconcile inconsistent data manually.
They quietly stop small problems becoming large ones.
Leadership therefore sees a relatively inexpensive incident.
But that may simply mean somebody else is carrying its weight.
This is one reason recurring problems can survive for years.
The organisation measures the cost that escapes the system rather than the effort required to prevent it escaping.
Eventually, the workaround becomes part of normal operations.
The organisation hasn't eliminated the problem.
It has become stronger at carrying it.
Measure density, not just volume
When deciding whether a recurring problem deserves executive attention, frequency should therefore be only one dimension.
Ask what sits inside each occurrence.
What dependency does it reveal?
What customer relationship does it threaten?
What decision does it delay?
What risk does it expose?
What management capacity does it consume?
What workaround keeps it invisible?
What would happen if that workaround failed?
And critically:
How large could the consequence become without the underlying condition materially changing?
A frequent low-consequence problem may genuinely be irritating rather than strategic.
A rare problem with enormous concentrated consequence may deserve immediate attention.
The dashboard will not necessarily tell you which is which.
Stop measuring problems by how much space they occupy
CEOs have finite attention.
Naturally, the loudest, largest and most frequent problems compete successfully for it.
But recurring problems don't politely advertise their economic significance.
Some occupy entire transformation programmes while producing surprisingly little consequence.
Others appear as a small exception in an operational report while quietly carrying regulatory, customer, financial or resilience exposure vastly disproportionate to their size.
The challenge is not simply identifying how often something goes wrong.
It is understanding what is compressed inside each recurrence.
Because the smallest item on your executive dashboard may not be the lightest problem in your organisation.
So if one of your seemingly minor recurring problems suddenly stopped being contained tomorrow, how much would that teaspoon really weigh?
0 Comments