Almost every organisation I work with makes the same mistake: competencies get treated as leadership. They're not. A competency is a skill you can demonstrate on a good day, in a controlled setting, with no pressure on you. A capability is what's left when the pressure doesn't let up — when the stakeholder is angry, the numbers are wrong, and the room is waiting for you to decide. Most leadership frameworks measure the first thing and call it the second. That's the whole problem in one sentence.
I didn't arrive at this distinction from a textbook. I arrived at it from watching technically excellent people get promoted into roles they couldn't hold — not because they lacked skill, but because skill was never the thing missing. What was missing was the capacity to carry judgement, ambiguity, and other people's trust at the same time. That's not a competency. You can't put it on a training slide and tick it off. It has to be built, tested, and evidenced in real decisions, under real constraints, over real time.
So when I say capabilities and competencies aren't the same thing, I don't mean it as a semantic nitpick. I mean it as the reason most leadership development spend doesn't survive contact with a hard quarter. Organisations build competency libraries because libraries are easy to build. They're measurable, they're trainable, they look rigorous in a slide deck. But they answer the wrong question. The right question was never "can this person do the task?" It's "can this person be trusted to own the outcome when nobody is checking their work?"
That's the frame this whole piece is built around, and it's the same frame behind every leadership capability framework I build with clients: capability is a role-world question, competency is a skills-world question, and conflating the two is why promotions keep rewarding the wrong things.
Why I stopped trusting competency libraries
I used to think a well-built competency framework was most of the job. It isn't. A competency library tells you whether someone can name the right behaviours in an interview. It tells you nothing about whether they'll make the unpopular call when the popular one is easier and nobody will notice for six months. I've sat across from leaders who could recite every competency on the wall and still froze the moment a decision actually cost them something — political capital, a friendship, a comfortable narrative about themselves.
Leaders live in two worlds simultaneously, and most frameworks only measure one of them. There's the role world — what the role actually requires to produce outcomes through other people: judgement under incomplete information, decision ownership, influence without formal authority, and the unglamorous work of shaping a culture nobody assigned you to shape. Then there's the skills world — what a person can personally do, the learned techniques, the frameworks, the tools in the kit bag. Competency models live almost entirely in the skills world. Capability lives in the role world. When you only build for the skills world, you get leaders who are fluent but not trustworthy under load.
That gap shows up in three places I see constantly, in almost every organisation I've advised. Leadership development turns into a training calendar instead of an outcomes programme — activity gets confused with progress. Promotions go to whoever is most visibly expert, not whoever is most reliably accountable for enterprise-level outcomes. And performance conversations turn subjective and political, because nobody defined what "good" looks like at this level, in this context, under these constraints — so the loudest opinion in the room wins instead of the clearest evidence.
This is precisely where executive coaching earns its keep, but only if it's built around capability, not competency completion. Coaching that just reinforces a skills checklist is expensive babysitting. Coaching that builds judgement, decision ownership, and the stomach for accountability — that's what actually moves a leader from competent to capable. It's why I built leadership capability architecture around evidence in real work, not attendance in a workshop.
The Capability Lens — how I actually tell the difference
The Capability Lens: five questions a competency list can't answer
- Does it hold under pressure?: A competency is proven in a calm room. A capability is proven when the room isn't calm — deadline compression, conflicting stakeholders, incomplete data. If the behaviour only shows up when conditions are favourable, it's a skill, not a capability.
- Is the evidence a decision or a demonstration?: Competency evidence is a demonstration: a role-play, a training completion, a manager tick-box. Capability evidence is a decision that was owned, with a consequence attached to the person who made it — not a plan that was drafted and handed off.
- Does it scale with complexity, or break?: Some skills transfer cleanly across contexts — a negotiation technique works whether the deal is small or large. Capability doesn't transfer that cleanly. The capacity to negotiate under board-level scrutiny with three conflicting stakeholders is a different, harder thing than the negotiation competency itself, and most frameworks pretend it's the same skill just "applied more." It isn't.
- Would it survive without the leader being told what to do?: Competency can be coached in the moment — someone can prompt the right technique. Capability is what a leader does when there's no one in the room to prompt them. If the behaviour collapses without a script, you've trained a skill, not built a capability.
- Is it visible in outcomes twelve months later, or only in the workshop feedback form?: The only honest test of a capability claim is whether the outcome it was supposed to produce actually showed up — team retention, decision speed, succession depth — months after the training budget was spent. Competency scores rarely correlate with that. Capability, properly evidenced, does.
I use this lens with every client engagement because it forces an uncomfortable but necessary reframe: most "leadership gaps" that get diagnosed as skill gaps are actually capability gaps wearing a skill gap's clothing. You don't fix a capability gap by sending someone to a workshop on the competency that sits nearest to it. You fix it by giving them real decisions, real stakes, and real accountability — with a coach or a structure around them that catches the pattern, not the individual failure.
Where competency thinking actively damages leadership pipelines
I want to be specific about the damage, because "competencies aren't enough" sounds abstract until you see it play out in a succession plan. A competency library, on its own, cannot tell you what "good" looks like at each leadership level — frontline, functional, enterprise — because it was never built to be level-aware in the first place. It flattens a functional leader and an enterprise leader into the same skill statements, as if influence at a departmental level and influence at a board level require the same muscle. They don't. One requires managing through people you know well. The other requires managing through people who don't report to you, don't trust you yet, and don't have to listen to you at all.
The second failure is treating capability as something you build primarily in a classroom. You don't. Capability is built through purposeful practice on real work, through mentoring that forces a leader to sit with a hard decision instead of handing it upward, and through deliberate exposure to complexity slightly ahead of comfort. This is the actual mechanism behind good leadership coaching — not knowledge transfer, but structured exposure with accountability attached. A leader who has been coached through five genuinely hard calls has more capability than one who has completed twenty modules.
The third failure is the one people underestimate most: ignoring the operating environment a leader sits inside. Capability isn't a personal attribute you can assess in isolation — it's constrained or amplified by the operating system around the leader. Meeting cadence, decision rights, how conflict gets handled, whether ownership is actually clear or just assumed. I've watched genuinely capable leaders look incompetent inside a broken operating rhythm, and I've watched moderately skilled leaders look exceptional inside a well-designed one. If you assess capability without assessing the system the leader operates in, you will misdiagnose the problem almost every time — and you'll coach the person when you should have redesigned the structure.
Building a framework that actually holds someone accountable
A leadership capability framework only earns its keep if it survives contact with a real promotion decision, not just a training catalogue. So what's the sequence? I use one, and the order matters — skip a step and the framework collapses back into a competency list with better branding.
Start with outcomes, not adjectives. Don't describe leaders with words like "strategic" or "resilient" — describe what they need to produce: execution that holds up under pressure, a culture that doesn't fracture when things get hard, decision cycles that are fast and still accountable, a pipeline of successors who are actually ready. Adjectives are unfalsifiable. Outcomes aren't.
Then define capability by level, deliberately. Frontline leaders stabilise execution and coach daily performance. Functional leaders integrate across teams and build capability through the managers beneath them, not just through their own effort. Enterprise leaders set direction, own risk at a system level, and — critically — develop the successors who will eventually replace them. If your framework uses the same language for all three, it isn't a framework. It's a poster.
Then attach evidence rules that can't be gamed by good intentions. Decisions made and owned, not plans proposed. Stakeholder outcomes, not stakeholder meetings attended. Patterns across time, not a single strong quarter. This is the difference between a framework that reduces subjectivity in a promotion decision and one that just gives the subjectivity better vocabulary.
And finally, close the loop with coaching and practice, or the framework stays theoretical. Convert every capability expectation into a weekly practice a leader is actually accountable for. Use reflective review — not performance review — to sharpen judgement after real decisions, not hypothetical ones. Assign live work that produces evidence, not workshop attendance that produces a certificate. If your framework doesn't route back into someone's actual week, it will sit in a shared drive being admired and never used. Further reading: Pessimistic vs Optimistic: Know the Difference.
The distinction I want you to leave with
If you take one thing from this, take this: capability is not a bigger, more advanced competency. It's a different category of thing entirely. A competency is something a person has. A capability is something a person can be trusted with. That difference — has versus can be trusted with — is the entire reason competency-based leadership systems keep producing leaders who look ready on paper and aren't ready in the room.
I'll go further, because I think this is the part most frameworks are too polite to say out loud: you cannot train your way to capability. You can only earn it, through decisions that had real consequences, reviewed honestly, repeated under increasing complexity. Coaching accelerates that earning process. Training, on its own, does not. Conflating the two is how organisations spend heavily on leadership development and still watch their succession plans fail the moment real pressure arrives.
This is also why I don't build competency libraries for clients anymore, not as a standalone deliverable. I build capability architectures — level-aware, outcome-anchored, evidenced through real decisions — because that's the only version of "leadership standards" that survives a hard year. A competency library survives an audit. A capability architecture survives a crisis. Those are not the same test, and only one of them is the one your organisation actually needs to pass.
So the next time someone hands you a competency framework and calls it a leadership strategy, ask the only question that matters: does this tell me who I can trust with the decision nobody wants to make? If the answer is no, you don't have a leadership framework. You have a very well-organised skills inventory — and it will not tell you who your next generation of leaders actually is.