When Capability Meets Capacity
“I know how to do this. I just can’t seem to do it right now…”
Have you ever experienced some version of this?
The confused frustration of:
I know my stuff.
I've done this before.
I've put in the work.
So why does it suddenly feel out of reach?
Maybe you've blanked in an interview.
Or lost your cool in an important conversation.
Or found yourself falling back into old habits you thought you'd already changed.
You didn't suddenly lose the capability.
You simply couldn't access it in that moment, under those conditions.
In my previous blog, I explored why understanding isn't capability. Today, I want to explore what comes after capability: capacity.
Because once we know how to do something under supportive conditions, the question changes.
It's no longer simply: Can I do this?
It becomes: Under which conditions can I do this?
So if you're currently looking at a team thinking, "They know how to do this. Why aren’t we seeing the results yet ?".
Capacity is often the missing piece.
Let's unpack the difference between capability and capacity.
1. Capability ≠ Capacity
We look at what people can do and assume they therefore have the capacity to do it well on a regular basis.
Unfortunately, these aren’t the same thing.
Capability is what your system has learned and can draw from. It's an internal library of patterns, skills and responses built through experience.
Do you know how to ride a bicycle?
Can you give useful feedback?
Can your team collaborate effectively?
Capability develops through learning and experience. It is something you build and continue to develop throughout your life.
Capacity is different. It is what you currently have the bandwidth to access and use.
The capability may be there.
But in the moment, you may not have enough available attention, energy or emotional bandwidth to retrieve it, apply it or do it well.
Because capacity fluctuates. It is influenced by:
Time
Attention
Energy
Resources
Emotions
Physical and cognitive space
You can see this clearly in sport.
A footballer can take hundreds of penalty kicks in training. They know the technique. They've done it successfully countless times. They are highly capable.
But during a game, we're not just watching whether they know how to perform.
We're watching whether they can access that capability under different conditions.
The same thing happens at work.
A leader may be perfectly capable of having a difficult conversation in a calm, well-prepared setting.
But put that same leader into a high-pressure stakeholder meeting and now the same skill requires more attention, focus, emotional regulation and energy.
The skill hasn't disappeared.
There is simply less capacity to draw on it because multiple things are pulling from the same finite capacity simultaneously.
2. Capacity Is limited
Unlike capability, capacity is finite.
A person can have a great capability to collaborate and still have very little capacity left to do it on a Wednesday evening.
Which is why capacity needs to be monitored, protected and managed.
This is one of the fundamental differences between working with humans and working with machines which I go deeper into with a separate blog post.
Because when human capacity gets stretched, our range narrows as the system tries to bring the load back within a manageable range.
What gets dropped depends on the person, the task and the type of capacity being consumed.
One person may lose access to perspective first.
Another may struggle to regulate their reactions.
Another may find it harder to tolerate uncertainty or hold complexity.
The problem is that when you're trying to do something precise or demanding, the things you drop to stay within capacity can have a disproportionate effect on the outcome.
Think back to the footballer.
In training, they may be able to execute a complex sequence almost automatically: reading the defence, judging the angle, controlling the ball and placing the shot exactly where they want it.
Now put them in front of 2,000 people, with the crowd booing and a difficult conversation with their coach still on their mind.
What gives?
Do they lose focus on the game?
Lose their emotional regulation?
Lose accuracy in the kick?
Organisational change creates a similar capacity problem.
We're asking people to develop and use new ways of working while their capacity is still being consumed by the existing system.
Meetings
Interruptions
Chasing information
Decisions
All of these consume capacity.
And new ways of working usually require more capacity than familiar ones.
They require more attention, more conscious effort, more cognitive space, and more tolerance for uncertainty.
So the question isn't only : Do people have the capability?
It is: How much capacity is actually available right now?
and : What is consuming it ?
Because more information or capability cannot, by themselves, solve a capacity constraint.
Moreover, capacity isn't only an individual resource.
Teams have capacity too.
In a healthy team, when one person's capacity drops, someone else may be able to pick up some of the load.
But when a team is overloaded, there is no spare capacity to give without dropping something or someone.
So work starts bouncing around.
A decision waits because nobody has the attention to make it.
A problem gets escalated because the person holding it doesn't have the capacity to resolve it.
A task gets passed to someone else, who is already carrying too much.
A question gets deferred until the next meeting.
And every time it moves, it consumes more capacity.
More coordination.
More handoffs.
More follow-up.
More decisions to revisit.
Eventually, the organisation can end up spending significant amounts of its limited capacity managing the movement of work rather than doing the work itself.
This is where capacity becomes systemic.
The problem isn't simply that individuals are overloaded.
It is that the system as a whole has run out of productive places for the work to go.
3. When Capacity Is the Constraint
If capacity, not capability, is the main constraint in your team, you need to find ways to reduce what is consuming the capacity.
I know three main ways :
Change the work.
Change the load associated with the work.
Add capacity from outside.
#1. Change the work — reduce complexity
This is often the most straightforward place to start.
If something can be simplified, eliminated, automated or sequenced differently, you create capacity without asking people to stretch further.
Remove unnecessary steps.
Protect focus time.
Automate a process.
Clarify a decision.
Reduce reporting requirements.
Sequence competing priorities.
The principle is simple: less complexity and fewer things moving at once means less capacity required to get the work done.
#2. Change the load associated with the work
Sometimes the work itself isn't the problem. It's the load around it. That load is often increased by:
Uncertainty — not knowing what will happen, what is expected, whether a decision is safe, or what others are thinking.
Pressure — deadlines, high stakes, scrutiny, urgency, competing demands, or simply having no room to breathe.
Emotional load — conflict, tension, fear, relationship strain, status concerns, disappointment, or having to manage your own reactions while still trying to do the work.
But what exactly consumes capacity also differs from person to person.
One person may find a particular type of work energising.
Their colleague two desks away may find it exhausting.
One person may thrive with ambiguity.
Another may spend enormous amounts of cognitive energy trying to work out what is expected.
So redistributing the load isn't simply about dividing work equally.
It's about noticing where capacity is being consumed and organising the work accordingly.
That might mean changing who carries what, matching work more deliberately to strengths and capabilities, reducing pressure, creating more slack, or taking something off someone's plate when they're already at their limit.
#3. Add capacity from outside
Sometimes the work can't be changed (or has already been changed) and still the existing team simply doesn't have enough capacity to carry what needs to happen next.
That's when you can bring capacity into the system from outside.
Sometimes that's another pair of hands.
A new hire.
Someone who can take work off the team's plate.
Sometimes it's specialist expertise.
Someone who brings knowledge or experience the team doesn't currently have.
But sometimes what's missing isn't knowledge or hands.
It's capacity to think, talk and work differently together. That's where facilitation can be useful.
A facilitator can temporarily take some of the following off the team's shoulders:
the structure
the goal
the process
the pace
the attention
the boundaries
the emotional tension
This creates more room for people to think, contribute, challenge, decide and work through the work that only this team can do — while someone else holds the conditions that make that possible.
If you look at a team and find yourself thinking:
But they know how to do this… why aren't they doing it?
Try asking a different question:
What would need to change for them to be able to access that capability here?
Because capability doesn't exist in a vacuum.
If your team is struggling to access the capability it already has, we can explore together what might need to change — and whether H&CO facilitation could help.
