Ben Satchwell argues that muddled language is undermining people frameworks, HR systems and L&D credibility, especially as skills data becomes machine-readable. Ben clarifies the building blocks from knowledge to behaviour, explains why competencies evidence individual performance while capabilities describe systemic potential, and shows how aligning both creates readiness without duplication.
This article is the first in a three-part series exploring how organisations can clarify, connect and modernise their use of competence, capability and skills frameworks.
There’s a quiet crisis of language playing out in HR and learning. We talk about skills, competencies, capabilities, and knowledge as if they’re interchangeable. They’re not. The confusion is costing organisations clarity, coherence, and credibility.
The difference between capability and competency is the line between proving performance and enabling potential
I see it in tenders, frameworks, and platform integrations alike. Teams argue over definitions, systems can’t interoperate, and everyone wonders why their frameworks don’t quite align. The truth is that the difference between capability and competency isn’t academic hair-splitting. It’s the line between proving performance and enabling potential.
The blurred lexicon
The International Organization for Standardization (ISO) and the Skills Framework for the Information Age (SFIA) both recognise that terms like competence, capability and skill are used inconsistently. ISO 24773-1 even concedes they’re often treated as synonyms. SFIA takes the same pragmatic view: “Industry uses such terms almost interchangeably.”
But that flexibility hides a real problem. In practice, a competency framework and a capability framework serve very different purposes. One measures how work is performed today. The other defines what must be possible tomorrow. When those purposes blur, organisations end up trying to use one tool for two very different jobs.
The building blocks
To rebuild clarity, it helps to start from the ground up:
- Knowledge is conceptual understanding — the facts, principles and theories we hold in our heads
- Skill is the ability to apply that knowledge, often in controlled environments
- Behaviour is how that skill is expressed — the attitudes and interpersonal style that make it observable
- Competency is the consistent, demonstrated application of knowledge and skill to achieve results. It’s proof that someone can perform to an expected standard
- Capability, by contrast, is the integrated ability of people, systems, and processes to deliver outcomes repeatedly. It’s potential — the collective capacity that underpins resilience and adaptability
In short:
- Competency is individual and evidence-based
- Capability is systemic and future-focused
I spoke about this to Grant Nicholson, who is the Lead Capability Architect from the Australian Public Service, and he concurred that you can’t be competent at something until you’ve actually done the job.
Potential versus proof
The distinction of potential versus proof is more than a neat metaphor. It defines the logic of two very different frameworks.
A competency framework emerged from vocational and performance systems. It describes the standards of observable behaviour expected in specific roles: what “good” looks like, today. Its purpose is assurance: recruitment, certification, compliance, and appraisal.
A capability framework, on the other hand, looks beyond roles to the broader capacity of teams and organisations. It clusters knowledge, skills and behaviours into integrated capabilities that describe how value is created. Its purpose is development: shaping readiness for what’s next.
This is why capability statements sound aspirational and systemic (“builds partnerships that enable collective value”), while competency statements sound behavioural and evaluative (“engages stakeholders to deliver agreed outcomes”). Both use levels, but they scale different dimensions: capability tracks maturity of potential, competency tracks mastery of performance.
Why both use levels, and why that matters
People often ask: if both use proficiency levels, aren’t they the same? The answer lies in the direction of travel:
- Competency levels move from dependence to independence — can the person perform this task reliably, without supervision?
- Capability levels move from awareness to influence — can the person (or system) integrate, anticipate, and shape outcomes across contexts?
Both are useful. Competency progression tells you who can execute today. Capability progression tells you who can adapt tomorrow. Together, they form a line of sight from individual mastery to organisational readiness.
That line of sight is what most HR systems are still missing. Too often, performance and development data live in separate worlds, one focused on accountability, the other on aspiration. Aligning the two requires shared definitions at the foundation.
Avoiding duplication
Understanding the distinction also prevents one of the most common implementation traps: duplication. Individuals and roles use competencies because performance is personal and measurable. Teams and organisations use capabilities because strategic capacity is collective and developmental.
When organisations conflate the two, they end up re-writing the same behaviours in different places and confusing users about which framework applies when. Clear boundaries let both coexist without overlap, competencies anchor assurance, capabilities enable agility.
Why clarity matters now
This isn’t just a theoretical clean-up. As learning systems, AI tools, and workforce analytics become more data-driven, the cost of fuzzy language grows. Machine-readable frameworks depend on precision. Skills taxonomies, like those used by the OECD or Lightcast, can only connect content, capability, and career pathways when terms mean the same thing everywhere they appear.
Without shared definitions, data drifts, frameworks fragment, and insight evaporates. With them, organisations can finally align the micro (how an individual performs) with the macro (how a system evolves).
The takeaway
Language shapes logic. When we blur the boundaries between skills, competencies and capabilities, we end up measuring assurance when we meant to build ambition. Competencies prove what’s already working. Capabilities prepare us for what’s coming next.
Used together, they turn frameworks from static documents into dynamic levers — helping organisations not just perform, but progress.
Ben Satchwell is Head of Capabilities at Acorn
