The Superficial Diagnosis Loop
The pattern in which an organisation repeatedly treats the visible symptoms of a problem without reaching the conditions producing them.
IN ONE LINE
The problem you can see may be real. It still may not be the problem you need to solve.
Three minutes.
What it is
Something isn’t working.
Delivery is slow. Costs are rising. Turnover is high. Quality is inconsistent. Decisions take too long. A function is underperforming. Customers are unhappy.
These are real problems. They can be measured, discussed and investigated.
But they are also outputs of a system.
The Superficial Diagnosis Loop begins when the organisation sees one of those outputs and treats the place where it has become visible as the place where it originated.
Slow delivery becomes a delivery problem, so project management is strengthened. High turnover becomes a retention problem, so an engagement initiative begins. Poor performance becomes a capability problem, so people are developed, reorganised or replaced. Decisions are slow, so another governance process is introduced.
Every intervention has a logic to it.
And sometimes it works.
But when the underlying conditions sit somewhere else, the intervention acts on the symptom while leaving its source intact. The organisation gets temporary relief, visible activity or both. Then the problem returns, perhaps in a slightly different form, and another intervention begins.
The symptom tells you where the problem became visible. Not necessarily where it began.
That distinction is the heart of the pattern.
What creates it
Visible problems attract attention. If delivery is late, the natural place to investigate is delivery. If turnover is high, attention goes to the people leaving. We instinctively look for causes close to their effects.
Symptoms are easier to measure than conditions. A missed target can be counted. The competing priorities, unclear authority and accumulated decisions that contributed to it are much harder to put on a dashboard.
Action is rewarded. Once a problem is visible, there is pressure to do something about it. A restructure, programme, process change or new hire demonstrates action in a way that deeper diagnosis does not.
The cause may sit far from the symptom. Decisions made at one level can create consequences several layers away. By the time those consequences become visible, their connection to the original conditions may be difficult to see.
Looking upstream can be uncomfortable. A proper diagnosis may eventually reach decisions, assumptions or priorities set by people with more authority than those experiencing the problem. Stopping the investigation earlier is often easier.
This isn’t usually a failure of intelligence. It is a predictable consequence of trying to understand a complex system from the point where it appears to be breaking.
How to recognise it
The same problem keeps coming back. There have been multiple attempts to fix it, but the improvement either doesn’t last or the problem reappears somewhere else.
Interventions multiply. New processes, governance, programmes, consultants, restructures or hires are introduced, yet the underlying performance stubbornly refuses to shift.
The diagnosis closely resembles the symptom. Delivery is slow because delivery needs improving. Engagement is low because people are disengaged. Decisions are slow because the decision-making process needs tightening.
The description may be accurate. The explanation isn’t necessarily complete.
Different people encounter the same difficulty. Leaders or teams change, but familiar problems eventually return.
The intervention creates more work without removing the original problem. The organisation now has the symptom and the machinery introduced to solve it.
People start saying, “We’ve tried that before.” Not necessarily because the intervention itself was wrong, but because successive interventions have been aimed at roughly the same level of the system.
And perhaps the clearest signal of all:
The organisation keeps fixing things, but nothing seems to stay fixed.
What it gets mistaken for
Decisiveness.
When something important is going wrong, prolonged diagnosis can become an excuse for inaction. Organisations cannot investigate forever while results deteriorate.
But there is a difference between acting quickly and acting on the first available explanation.
The visible symptom deserves attention. It may require immediate action. A failing project may need stabilising today even if the reasons it is failing will take longer to understand.
The mistake is assuming that stabilising the symptom has diagnosed the cause.
A delivery intervention may improve delivery temporarily while the organisation continues to generate conflicting priorities. A new governance process may create clearer decisions while the same decisions continue to be escalated unnecessarily. A new leader may perform differently while inheriting exactly the same constraints as the last one.
Treating the symptom isn’t always wrong.
Stopping the diagnosis there is.
Why it persists
Because the first intervention often produces something.
A restructure creates movement. A new process creates clarity. A new leader brings energy. A programme focuses attention. For a while, things may genuinely improve.
That makes it difficult to distinguish between an intervention that has removed the cause and one that has temporarily compensated for it.
Then the underlying conditions begin producing familiar consequences again.
At this point, the failure of the intervention can itself be superficially diagnosed. Perhaps it wasn’t implemented strongly enough. Perhaps the team resisted it. Perhaps the new process needs more governance. Perhaps the new leader wasn’t quite right.
So another intervention is added.
The organisation is now trying to solve the consequences of the previous attempt to solve the consequences of the original problem.
A wrong diagnosis doesn’t just waste the intervention. It can create the next symptom.
That is where the loop becomes expensive.
What becomes possible
Going deeper doesn’t mean turning every organisational problem into an enormous systems investigation.
It means staying curious for one step longer.
Instead of asking only what is going wrong?, ask what would have to be true for this outcome to keep happening?
That shift changes the investigation.
Slow delivery may lead to competing priorities. Competing priorities may lead to decisions that were never properly sequenced. Those decisions may lead to strategic tensions that were never resolved.
High turnover may lead to overloaded roles. The overloaded roles may lead to unclear authority. The unclear authority may lead to decisions continually travelling upward, creating the very workload and frustration people are leaving to escape.
The eventual cause may be several steps away from the original symptom.
Once you find it, the intervention can become smaller rather than larger because you are no longer trying to compensate for the problem everywhere it appears.
Go far enough upstream and you may find one condition creating ten different problems.
Where to start
Take a problem the organisation has already tried to solve more than once.
Then put the previous interventions to one side for a moment.
ASK THIS
What conditions would have to exist for this problem to keep coming back?
Follow the answer upstream.
If delivery is slow, don’t stop at what is slowing delivery. Ask what creates those conditions.
If people lack authority, ask why decisions are being held elsewhere.
If priorities keep changing, ask where those changes originate.
If capable people repeatedly struggle, ask what they repeatedly encounter.
Keep going until you reach something that could plausibly explain more than the symptom you started with.
That is the point of diagnosis.
Not to find a more sophisticated name for what is going wrong.
To find what keeps producing it.
Last updated October 2026
