Before You Fix Performance,
Diagnose It
Performance can look deceptively simple. Someone isn't delivering what we expected, a team is missing targets or quality has slipped.
We can see the gap — but seeing the gap doesn't necessarily tell us what is producing it.
Elaine Wright · Simply Wright · September 2026
A performance gap is an observation, not an explanation
I've always been slightly cautious about the word performance — not because it isn't important, but because it can make something complex sound deceptively simple.
Someone isn't delivering what we expected. A team is missing targets. Work is taking too long. Quality has slipped.
Something needs to improve.
Once we describe something as a performance issue, it can feel as though we already know what the problem is. I'm not sure we always do.
Sometimes poor performance really is about capability, effort or behaviour. Sometimes expectations were never particularly clear in the first place. Sometimes people are working incredibly hard inside processes that make it unnecessarily difficult to succeed.
There may be competing priorities, unclear decisions, duplicated work, poor information or systems that create more friction than support.
And sometimes what appears to be an individual performance problem is something much bigger becoming visible through one person or one team.
The label 'underperformance' tells us there is a gap. It doesn't necessarily tell us why that gap exists.
That distinction matters because the explanation we choose shapes what we do next.
The same outcome can have very different causes
Once something has been labelled a performance problem, the response can start to feel fairly obvious.
More clarity. More monitoring. More accountability. More support. Perhaps a performance improvement plan.
Sometimes those things are absolutely appropriate.
But imagine two people producing exactly the same disappointing outcome.
One doesn't yet have the capability required to do the work. The other is highly capable but spends a significant proportion of their time navigating a cumbersome process, waiting for decisions and responding to priorities that repeatedly change.
The performance outcome may look similar - The response shouldn't be.
That's what makes performance interesting. The outcome itself gives us useful information, but not necessarily enough information to know what needs to change.
The gap between effort and outcome
One of the things I find particularly useful is looking at the relationship between effort and outcome.
If someone is putting in considerable effort but still struggling to deliver, what is absorbing that effort?
If several capable people are struggling with the same thing, what might that tell us?
If performance improves significantly when a particular barrier is removed, what does that suggest about where at least part of the problem sat?
A cumbersome process, late information, conflicting priorities, slow decisions, overlapping responsibilities or constant interruption may each seem relatively small when considered separately.
Together, they can have a substantial effect on what people are able to deliver.
If capable people are working hard and repeatedly struggling to achieve the required outcome, that pattern is worth being curious about.
It doesn't prove that the problem sits in the system, but it gives us a reason to look beyond the assumption that people simply need to try harder.
Performance doesn't belong entirely to the individual
The more I've worked with teams and organisations, the less comfortable I've become with treating performance as though it belongs entirely to the person doing the work.
Individual contribution absolutely matters. People make choices. They bring different levels of skill, motivation, confidence and experience.
There are times when someone genuinely isn't meeting the expectations of their role and that needs to be addressed.
But people are also working inside something.
They are responding to the clarity they have, the resources available to them, the behaviour around them, the decisions being made, the systems they have to navigate and the signals they receive about what really matters.
Those conditions can support good performance, constrain it or sometimes pull people in completely different directions.
That doesn't remove individual accountability.
Nor does looking at the system mean assuming that every performance problem has an organisational explanation.
For me, it simply makes the picture more complete. If we only look at the individual, we may miss conditions that are influencing what they can reasonably achieve. If we only look at the system, we may miss something that genuinely does sit with the individual.
From 'who?' to 'what is producing this?'
Perhaps this is where the question changes.
Rather than beginning with:
Who is responsible for this performance?
I find it more useful to ask:
What combination of things is producing the performance we are seeing?
That might include capability, effort or individual behaviour.
It might include clarity, workload, priorities, resources, processes, decision-making, leadership or technology.
Quite often, I suspect, it will include more than one thing.
And that matters because different explanations lead to different responses. We might need to develop capability, clarify expectations or address individual performance. We might need to redesign a process, resolve competing priorities or remove a barrier. We may need to do several of those things together.
The purpose isn't to make performance more complicated than it needs to be.
It's to avoid making it simpler than it really is.
Before we decide how to improve performance, do we understand what is producing the performance we have now?