Ben Satchwell explains why competency frameworks can support development only within the boundaries of current role performance, because they were built for assurance and consistency. Ben contrasts this with capability frameworks, designed for future readiness, and argue the strongest approach is to connect both: competencies evidence mastery, capabilities guide growth.
This is the second article in a three-part series examining the evolving relationship between competence and capability frameworks – and how each supports performance, development and strategy. Part one was about improving our language.
Almost every organisation modernising its approach to learning and performance eventually asks the same question: If we already have a competency framework, can we use it for development too?
Competency frameworks can build mastery within a role, yet they struggle to drive the kind of growth organisations now need
It’s a fair question, and the short answer is yes, but only up to a point. Competency frameworks can build mastery within a role, yet they struggle to drive the kind of growth organisations now need: adaptability, innovation, and readiness for change. To see why, we need to look at what each framework was built to do.
Built for assurance, not evolution
Competency frameworks were created for consistency. They define what “good” looks like today: the observable behaviours and outcomes that signal proficient performance. That’s why they’re so effective for recruitment, certification and compliance.
But this same precision limits their reach. By design, competency frameworks measure performance as it currently exists. They tell us how reliably someone meets today’s expectations not how ready they are for tomorrow’s challenges. When they’re stretched into development tools, they often create a ceiling. People learn to perfect what already exists rather than prepare for what’s next.
Built for development, not definition
Capability frameworks flip that logic. They describe the integrated abilities a team or organisation must demonstrate to deliver future outcomes. Where a competency framework measures depth of mastery, a capability framework builds breadth of adaptability.
One asks: “Can this person do the job now?”
The other asks: “Can this system respond to what’s coming next?”
Capabilities integrate knowledge, skill and behaviour across changing contexts. That’s why they’re inherently developmental, they focus on potential, not proof.
Two philosophies of learning
Underneath the frameworks sit two different learning logics.
| Competency Frameworks | Capability Frameworks | |
| Assumption | People learn by mastering defined tasks to a standard | People learn by integrating knowledge and judgement across contexts |
| Orientation | Present-focused | Future-focused |
| Learning model | Behaviourist – repetition and feedback | Constructivist – reflection, experimentation, adaptability |
| Language | Apply, perform, comply | Integrate, anticipate, innovate |
| Outcome | Reliable performance | Agility and growth |
Both are essential:
- Competency frameworks strengthen what you already do well
- Capability frameworks stretch what you might need to do next
Where competency frameworks do support development
Used correctly, competency frameworks remain powerful development tools, especially in professions where mastery can be objectively demonstrated. Think nursing, engineering, cyber-security. In these settings, “development” means moving from partial competence to full competence, closing performance gaps within the current role.
That’s developmental, but it’s bounded. Once the person meets the standard, the framework’s job is done. The learning cycle ends where competence is proven.
Where they hit their limits
Problems arise when development needs to build adaptability, creativity or cross-functional thinking. Competency frameworks codify what’s already known. They’re backward-looking by nature: excellent at benchmarking current performance, less useful for shaping what comes next.
Consider two parallel statements:
- Competency: Writes clear, accurate reports using established templates
- Capability: Synthesises insights across disciplines to inform future strategy
Both sound developmental, but only one moves the person into new territory. When development goals reach beyond the boundaries of today’s work, capability becomes the more powerful lens.
Complementary, not competing
The most effective organisations don’t choose between the two – they connect them. Competency frameworks provide evidence of mastery. Capability frameworks provide direction for growth.
Together they create a feedback loop:
- Capability defines what the organisation needs
- Competency data shows what exists
- Development bridges the gap
- Capability maturity improves.
The mistake many make is asking one framework to do both jobs. That’s when learning strategies stall and performance conversations become muddled. Keep them distinct but connected, and each strengthens the other.
A useful rule of thumb
If your goal is assurance, use competencies. If your goal is evolution, use capabilities.
Competency frameworks measure performance and target immediate improvement. Capability frameworks shape development and strategic alignment. Never rely on competencies alone if your ambition is transformation as they describe what is, not what could be.
Why this distinction matters now
Work is changing faster than most frameworks can keep up. The shelf life of technical skills is shrinking, AI is accelerating knowledge work, and adaptability has become the defining advantage.
In this environment, a competency-only approach risks creating high-performing employees who are perfectly prepared for a world that no longer exists. Capability frameworks keep organisations oriented to the future by linking development to evolving outcomes, not static standards.
The takeaway
You can use a competency framework for development. Just know what kind of development you’re getting. It will help people get better at what they already do. It won’t necessarily help them do something new. Competency frameworks build reliability. Capability frameworks build resilience.
Used together, they give organisations the dual focus they need: consistent performance today, and adaptive capacity for tomorrow.
Ben Satchwell is Head of Capabilities at Acorn
