The Law of Displaced Diagnosis
IN ONE LINE
Problems tend to be diagnosed where they become visible, not where the conditions producing them began.
Three minutes.
The law
When something goes wrong, we naturally look at the place where it went wrong.
Delivery is slow, so we examine delivery.
People keep leaving, so we examine retention.
Decisions take too long, so we examine governance.
Projects miss their commitments, so we examine project management.
Performance varies, so we examine the people performing the work.
None of those places is an unreasonable place to look. The problem is real there.
But the place where a problem becomes visible and the place where it originates are not necessarily the same.
The symptom tells you where the problem surfaced. It doesn’t tell you where to stop looking.
That is the Law of Displaced Diagnosis.
Why it happens
Visible problems give us something concrete to investigate.
If a project is late, we can examine its plan, team, governance and delivery practices. If turnover is high, we can look at engagement data, managers and retention initiatives.
The diagnosis has an appealing logic because the evidence is right there.
But organisations connect things that can look separate from one another.
A delivery team may be struggling because priorities keep changing elsewhere.
A manager may appear indecisive because five senior stakeholders are asking for different things.
A project may repeatedly miss deadlines because new work is added without anything being removed.
A team may look underpowered because its strongest people are constantly pulled away to solve problems elsewhere.
By the time the consequence becomes visible, its cause may be several decisions away.
Organisations often blame the last pair of hands to touch the problem.
And once we’ve found a plausible explanation there, the investigation can stop.
Why good interventions can fail
This is where displaced diagnosis becomes expensive.
If we diagnose a capability problem, we improve capability.
If we diagnose weak governance, we add governance.
If we diagnose poor execution, we strengthen execution.
The intervention can be excellent.
It can also be aimed at the wrong thing.
Then something frustrating happens. People work hard to implement the solution, there may even be an initial improvement, and eventually the problem returns.
The natural conclusion is often that the intervention didn’t go far enough.
So we do more of it.
More process. More oversight. More training. More management attention.
But if the conditions producing the problem remain untouched, we’re becoming increasingly sophisticated at treating its consequences.
You can get very good at fixing the wrong problem.
Look upstream
The Law doesn’t say that every problem originates at the top.
Sometimes a delivery problem really is a delivery problem. Sometimes someone needs training. Sometimes a process is poor. Sometimes a team needs to perform better.
The point is simpler.
Don’t confuse proximity to the symptom with proximity to the cause.
Before deciding where to intervene, follow the problem backwards.
What happened immediately before this?
What made that happen?
What decision, constraint or competing demand shaped it?
Keep going until the explanation stops being who failed to deal with the problem? and starts revealing what kept producing it?
That may lead downward, sideways or upward.
The direction doesn’t matter.
Finding the cause does.
Use the law
When a recurring problem appears, ask:
Are we fixing where the problem is, or where the problem comes from?
Then test the proposed intervention.
If it works perfectly, what changes upstream?
If the answer is nothing, look again.
You may still need to treat the immediate problem. Sometimes you absolutely should.
Just don’t mistake treating it for explaining it.
Where a problem appears tells you where to start investigating, not where to stop.
Last updated October 2026
