Capable vs capability — building people who can deliver value
Most organisations misunderstand “capability.” This guide explains the difference between capable and capability—and how to develop people who can deliver value now and in the future.
Capable vs capability — building people who can deliver value
Managers often ask how to scale capability, deploy capability, or build organisational capability.
Before designing programmes, structures, or training, it is worth clarifying what capability actually means — and why conflating it with being capable causes systemic problems.
The goal is straightforward: people who can deliver value now, and who can grow to deliver more value (for themselves, and the business) in the future.
Editor's note — where this sits
This essay sits in the Flywheel layer of the Idea to Value system — the layer concerned with how capability compounds through sustained practice. It argues that developing people requires seeing three distinct categories clearly, and that the failure to distinguish between them is where most organisational learning investment goes wrong.
The Idea to Value system — five layers
Three distinct observations about people
The distinction is subtle but important — and it splits into three, not two.
Capable — someone can already do the work. They have demonstrated the ability to perform at the required level. They need conditions that allow them to continue doing so, and to grow, not development programmes.
Has capability — someone has the latent potential to become capable. They cannot yet do the work at the required level, but with the right investment — coaching, on-the-job practice, time — they could. This is where development effort belongs.
Doesn't have capability — someone is not suited to this work, and investment in their development for this role will not produce the outcome required. This is the category most organisations avoid naming — but it is the most important one to be honest about. Misreading this as the second category wastes time, overloads coaches and mentors, and fails the individual by placing them in work they cannot do.
Quick reference — three categories
The flywheelCapable, has capability, doesn't have capability
Three distinct observations about people. Confusing them leads to misaligned development investment, overloaded experts, and individuals placed in roles they cannot succeed in.
Most organisations blur these three categories into one. They describe people as having capability when they mean capable. They invest in development for people in the third category who need a different role, not more training. They run team-level capability programmes when the work is individual.
Precision in language here prevents systemic failure.
Focus on individuals, not abstract teams
You do not manage a team. You manage individuals.
Individuals differ in their current ability, potential to grow, motivation and aspiration, and suitability for certain kinds of work. No team-level training programme accounts for this. No capability framework maps to it.
Training the team rarely produces competence. Developing individuals does — because development requires knowing which category someone is actually in, what they are motivated by, and what the gap between their current performance and the required standard actually is.
Turning capability into capable
For the people in the second category — those with latent potential — development follows a consistent pattern.
It begins with knowing what the work actually requires, not what a competency framework says it requires. Standards must be behavioural and specific enough that both the manager and the individual can see clearly whether they are being met.
It requires knowing the individual — their motivations, strengths, limits, and aspirations — through regular one-to-one conversation rather than annual reviews. Development plans built without this knowledge tend to develop the organisation's assumptions about the person rather than the person themselves.
The learning itself belongs in real work. Task acquisition beats theory every time. Pair developing people with capable practitioners. Let them do the work with guidance, not watch it being done. Measure success not by course completions but by behaviour change — whether decisions, habits, and outcomes have shifted.
A manager's paradox
The best managers build people who others want to hire.
People leaving is not failure — it is evidence of development. Organisations that focus on capability as a system rather than people as individuals tend to build frameworks, not competence.
Effective management is not about building capability frameworks. It is about cultivating capable people whose strengths align with meaningful work.
From the Cultivated library
10 Behaviours of Effective Employees
Free eBook · Coaching guide · Digital
The behaviours that distinguish people in category one from those still developing — and the coaching guide for managers who want to move individuals from capability toward capable, deliberately and with evidence.
Free to start
Get the free eBook →Workshops & Keynotes
In-person or virtual · Bespoke
For leadership teams who want to see their people clearly — which category each person is actually in, where development investment belongs, and how to have the honest conversations that capability development requires.
Enquire
Start the conversation →
