I define a leadership capability framework as a written, level-by-level description of the behaviours and judgement an organisation expects from its leaders, precise enough that two managers watching the same person would agree on whether a capability is present. The Center for Creative Leadership puts the purpose plainly: a capability model shows which characteristics leaders need to demonstrate to execute the business strategy. It is not a personality profile, a values poster or a competency wheel.
I've built these for scaling companies for years, and I'll tell you the uncomfortable part first. The framework is the easy bit. Many organisations treat it as the finish line: a laminated card, a slide, a wheel. On its own it changes nothing. What follows covers what a framework contains, a slice of one so you can see the shape, how to build it, why it fails, and where the system that embeds it comes in.
What is a leadership capability framework?
It is a structured model of the knowledge, behaviours, judgement and mindset leaders need to perform in one specific organisation, yours. It goes beyond what leaders must deliver and defines how they are expected to lead in order to deliver it. That is the difference between a framework and a generic leadership model lifted from a textbook. A good one is tailored to your strategy, your culture and the way your business actually runs, and it translates abstract ideas about leadership into behaviours someone could watch happen in a decision or a difficult conversation.
The four parts every framework needs
- Named capabilities: The short, deliberate list of capabilities your strategy depends on. Not a shopping list: the few that your next stage of growth demands.
- Behavioural anchors: Each capability written as something a leader visibly does, so it can be coached, assessed and recognised. "Inspiring" is a trait. "Makes the trade-off explicit and commits the team to it" is a behaviour.
- Level definitions: How each capability shows up as responsibility grows, from first-line team lead to the C-suite. The same word means different things at different altitudes, and the framework has to say so.
- Embedding points: The named decisions the framework touches: hiring, promotion, development, feedback and performance review. A capability that changes no real decision is decoration.
This is also where the framework separates from a competency framework. I have written separately about leadership capabilities vs competencies: a competency list describes skills a role needs, and a capability framework describes the judgement that holds when conditions change. That piece covers why capability, not competency, is the unit worth measuring. This one covers what you do with the unit once you have chosen it.
What does a leadership capability framework look like in practice?
The table below is a slice of a framework, shown so you can see the level of precision to aim for. It is illustrative: I wrote it for this article and it does not describe any client's framework. Two capabilities are shown across three levels, with the observable behaviour and the evidence source that would settle whether it is present.
| Capability (illustrative) | Level | Observable behaviour | Evidence source |
|---|---|---|---|
| Owns decisions | Frontline leader | Makes calls within the team's remit without waiting for approval, and says what was decided and why | Decision log kept by the team; manager's review of three recent calls |
| Owns decisions | Functional leader | Names which decisions sit with their team and which they will escalate, and holds that line when pressed | Written decision rights for the function; count of escalations that should not have been made |
| Owns decisions | Enterprise leader | Decides where a choice crosses functions, accepts the trade-off in public and reviews the result | Executive meeting record; outcome review after the decision |
| Develops others | Frontline leader | Gives specific feedback each week and agrees one development stretch with each person | Direct reports' answers on a short pulse; stretch assignments recorded |
| Develops others | Functional leader | Builds capability through the managers beneath them and not through their own effort | Managers' development plans; internal moves into larger roles |
| Develops others | Enterprise leader | Names and develops the successors who will replace them | Succession slate reviewed by the CEO and CHRO; readiness evidence from real assignments |
Notice what the right-hand column does. It stops the framework being a matter of opinion. If a manager says a leader develops others, the question becomes which evidence says so. A framework with the first two columns and no fourth cannot settle a promotion argument.
CCL's own approach shows how a library can feed this. Its Leadership Gap Indicator draws on a Leadership Capabilities Library, and the standard set in its Discovery Insights option has ten capabilities: boundary spanning, change leadership, develop others, equity, diversity and inclusion, feedback, initiative, learning agility, relationship management, resilience and systems thinking. Treat a list like that as raw material. The skill is selecting the few that your strategy depends on, then writing each as behaviour.
How do you build a leadership capability framework?
You build a leadership capability framework by defining capability as observable behaviour, mapping it by level and embedding it in the systems the business already uses. Writing the document is the short part. Everything that makes the document live is the build. CCL's published sequence for a capability model starts from strategy: articulate the organisation's purpose, goals and competitive position, identify the capabilities that map to them and to your existing internal resources, then review and select from a library. That sequence is sound, and I add the steps that follow.
- Start from strategy: Decide what the business has to become, then name the leadership capabilities that growth depends on. Ask which ones you must have in place five years from now, not which ones are fashionable.
- Define by behaviour, not personality: Write each capability as something a leader visibly does. If two managers would score the same person differently, the wording is not yet precise enough.
- Map it by level: Define how each capability shows up for a team lead, a functional head and an executive. Use different words at different levels, because the work is different.
- Attach evidence: Decide in advance what counts: decisions owned, stakeholder outcomes and patterns over time. Agree it before anyone is assessed.
- Embed it in real decisions: Wire the framework into hiring, promotion, development, feedback and performance review. If it does not change a real decision, it is not installed.
- Build the architecture around it: Add the decision rights, development pathways, cadence and measurement that keep capability compounding after the launch attention fades.
Expect the rollout to take time. A 2023 benchmark from Cornell's Center for Advanced Human Resource Studies spoke to 14 companies about how they measure leadership capabilities. All of them used a leadership measurement tool, some as an input into performance and promotion decisions and others for development only. The report says most found the change curve steep and took at least a year to scale, and the consensus was to be transparent and patient. If a vendor promises a live framework in a quarter, ask what they mean by live.
Why do leadership capability frameworks fail?
Leadership capability frameworks fail when they are treated as a document and not as a system. They are written, launched, admired and then disconnected from the decisions that run the business. The failure is rarely in the content. The pattern is familiar: a polished framework lands, leaders nod, and nothing about how anyone hires, promotes or holds people to account changes. Within a year it is a relic of a workshop nobody remembers. The reasons echo why conventional leadership training rarely changes performance: the intervention sits outside the system it was meant to improve.
- It hardens into a static checklist that lags the business and stops describing the leadership you now need.
- It defines traits and not behaviours, so nobody can tell whether a leader has the capability.
- It is owned by one team or one champion, so when they move on the framework goes dormant.
- It has no evidence column, so it cannot settle a promotion decision and people stop consulting it.
A 2026 bibliometric review of 1,993 leadership-competency publications makes the first point from the research side. Its authors say many institutions still treat competency models as static, and they argue these should be adaptive, context-responsive capabilities that evolve with the organisation. Each of the four failures above is a structure problem and not a wording problem. You do not fix them by rewriting the framework. You fix them by building the system that keeps it alive, which is the work I describe in building leadership capability architecture.
How is a framework different from Leadership Capability Architecture?
A framework is the list of capabilities. Leadership Capability Architecture, which I developed, is the system that designs, embeds and scales those capabilities so an organisation can grow without its leadership becoming the bottleneck. It has three steps. Design diagnoses constraints and aligns systems to strategy. Embed builds capability into the leadership workflow. Scale means leaders developing leaders. The framework belongs at the first step. The other two are where it either becomes real or does not.
Embed looked like this with one client. In one change programme the work finished and attention moved on. My advice was to build reinforcement in from the start: leaders reviewed the behaviour regularly and rewarded it, and the change became normal. That is the test I use for a framework. It has worked when it has stopped being a project.
Hand-over matters as much as installation. In another engagement I left the leadership team with a one-page operating rhythm, a decision log and a simple diagnostic they could repeat every 12 months. I checked back after 36 months. When I looked again, the team was running it themselves and had adapted my methods to its own context. I hand over frameworks that the client can run independently, because a framework that needs me every month has created a dependency.
Which capabilities should a leadership framework include?
Include the capabilities your strategy depends on, and fewer than you think. The CCL library shows how long the menu can get: its original research survey used 20 competencies selected from 56, and the 2022 guide lets an organisation choose up to 20 from its library. Even that is a large number for a busy line manager to hold in their head. Twenty capabilities is not a framework. It is a wish list, and a wish list is what you reach for when you have not done the hard work of choosing.
Cut until it hurts, then cut once more. What survives is what your strategy genuinely depends on, and a shorter, sharper set is the one people will use on a Tuesday when a real decision lands on their desk. If you are starting from nothing, ask what leadership has to become for your strategy to be possible, name the three or four capabilities that gap depends on, and write each as a behaviour a colleague could observe. The guide to measuring leadership capability across an organisation covers the evidence side, and the behavioural competencies underneath leadership capabilities help when you need the skill level beneath a capability.
How a framework supports growth
Done properly, a framework makes leadership consistent and transferable, so the business stops depending on a handful of individuals and starts producing capable leaders predictably. It reduces reliance on any one leader's style, smooths transitions and shifts the organisation from short-term fixes to long-term capability building. In my view, companies that grow beyond a founder's reach need to move from competency lists to capability standards and then to a leadership operating system that carries the standard into daily work. The systems fast-scaling companies need describes what sits around it.
If you want to see where your leaders stand against a standard before you write one, the leadership assessments give you a baseline, and the CapabilityAI page shows how an AI leadership coach is set up on this framework. For the longer treatment of the architecture itself, read the comprehensive guide to Leadership Capability Architecture and the piece on leadership framework vs leadership architecture.
The definition I work from
This is the sentence I use. A leadership capability framework is a written, level-by-level description of the behaviours and judgement your organisation expects from its leaders, precise enough that two managers watching the same person would agree on whether the capability is present. That precision is the whole game. If your framework cannot settle a promotion argument, it is a mood board.
The framework that changes who gets promoted is worth more than the elegant one that changes nothing. Aim for useful before you aim for beautiful, then put the system underneath it so it outlasts the people who wrote it. If you are choosing between named frameworks, this comparison of four leadership frameworks sets out what each answers.
Related reading
- Leadership Capabilities vs Competencies: Know the Difference
- A Comprehensive Guide to Leadership Capability Architecture
- What Is Core Leadership Capability?
- Leadership Capacity Vs Capability: How to Build
- The Leadership Capability Stack
- Why Leadership Capability Does Not Scale With Company Growth
- Scaling Leadership Capability After a Funding Round
- How Do You Build Leadership Capability Across Business Units?
- How to Develop Leadership Capability Skills at Workplace