What if the problem isn’t performance — but processing power?
What if the problem isn’t performance — but processing power?
We treat performance like a personal trait.
If someone isn’t delivering, we assume it’s about effort, discipline, or behaviour.
So we respond with goals, feedback, coaching, KPIs.
We look at what they’re doing — and try to fix it.
But what if the issue isn’t behavioural at all?
What if it’s cognitive?
What if someone’s struggling not because they don’t care…
but because the way their brain processes the world doesn’t match the system they’re in?
And what if that mismatch is more common than we think —
but we keep calling it a “performance issue”?
Does this sound familiar?
You’ve worked with somebody like this.
They’ve got experience.
They’ve done this work before.
They’re smart. They care.
But something’s off.
They’re slower to respond.
They ask the same question twice.
They miss a detail you assumed was obvious.
They seem foggy — like they’re always one step behind the room.
So you start wondering:
Are they distracted?
Burnt out?
Not focused?
And quietly, the question creeps in:
Are they still the right fit?
It’s subtle. But it happens.
We don’t always name it out loud — but we feel it.
The part we don’t design for
Here’s what research and real life both point to:
Cognitive load changes performance.
When the brain is carrying too much — too many inputs, too many switches, too many hidden assumptions — it doesn’t just get tired.
It gets slower.
Working memory shrinks.
Attention fragments.
Decision quality drops.
And people don’t all carry the same load the same way.
Some need quiet to think.
Some need context before they can move.
Some need time to switch gears.
Some need things visual.
Some need less information — not more.
That’s not weakness.
That’s variation.
But most workplaces don’t design for variation.
They design for one style of brain:
Fast response.
Verbal confidence.
Constant availability.
High context switching.
And when someone can’t match that rhythm, we treat it like a personal gap.
What that assumption is costing us
Here’s the hard part to admit:
When someone struggles, we usually look inward — at them.
We give them tools. Training. Feedback.
We assume the system is neutral, and the problem lives in the person.
But what if the system is the mismatch?
What if the environment is tuned to one kind of processing speed and one kind of communication style…
and anyone outside that bandwidth has to burn extra fuel just to keep up?
That’s not a performance problem.
That’s a design flaw.
And it doesn’t just wear people down.
It wastes capability — quietly, daily.
People start thinking they’re the issue…
when really the system is asking their brain to run work in a format that doesn’t fit.
What if we’re measuring the wrong thing?
We often treat performance like it’s behaviour.
But behaviour is the output.
The symptom.
Under the surface, what you’re really seeing is bandwidth:
how much the brain is carrying
how often it’s switching
how much context it’s missing
how much recovery it’s getting
Bandwidth is invisible… until it breaks.
And by the time someone is missing deadlines or checking out in meetings, the overload has usually been building for a while.
So maybe the smarter question is:
What kind of brain is this system built for?
And who gets left behind — not because they can’t perform, but because the system assumes everyone processes the same?
A simple bandwidth audit (for leaders and teams)
This is where we can get practical — without turning people into diagnoses.
Here are five common bandwidth drains that look like “underperformance”:
1) Context switching
Too many projects. Too many channels. Too many resets.
Every switch has a cost — and some brains pay more.
2) Hidden assumptions
“We all know this already.”
“We covered this last month.”
“If you were on the thread…”
When context is missing, processing power gets used just catching up.
3) Noise and interruption as default
Open plans. Slack pings. Meetings stacked back-to-back.
You can’t think deeply if your brain never gets to settle.
4) Unclear priorities
When everything matters, nothing is clear.
The brain burns fuel trying to guess what “good” means.
5) No recovery
Not rest as a luxury — recovery as a cognitive requirement.
Without it, performance doesn’t stay stable.
If you’re seeing “performance issues,” check these first.
Because often, what looks like a person problem is actually a bandwidth problem.
The design moves that stop wasting capability
This is not about screening people out.
It’s not about “finding the right kind of brain.”
It’s about building systems that let more kinds of brains do their best work.
Three moves can change a lot:
1) Make context visible
Don’t make people hunt for meaning across ten threads.
Use simple tools:
a one-page brief
a decision log
“here’s what changed” updates
clear definitions of success and trade-offs
When context is visible, brains stop wasting fuel.
2) Reduce simultaneous priorities
If you want quality thinking, stop stacking work like a buffet.
Fewer active priorities = more usable processing power.
This is one of the cheapest strategy upgrades there is.
3) Protect focus and recovery
Build quiet into the system.
no-meeting blocks
fewer pings by default
50-minute meetings
real breaks
Not as wellness.
As performance infrastructure.
A final turn
Here’s the shift I keep circling:
We say someone’s not “performing.”
But what if their brain is working twice as hard… just to stay in the game?
Maybe performance isn’t failing.
Maybe it’s misfiring — under load, in a system that doesn’t fit.
And if that’s true, then performance management needs a new layer.
Not just behavioural insight…
…but cognitive design.
Not “How do we get more out of this person?”
But:
What happens when we stop managing people’s output…
and start managing their mental bandwidth?
Because performance isn’t just what we see.
It’s what the brain can carry underneath.
And maybe we’ve been looking in the wrong direction.