Listen to a workforce planning meeting and you will hear three words used almost interchangeably: skills, competencies, and capabilities.
This is more than a vocabulary problem. If a team can’t agree on what it is measuring, it can’t agree on what “better” looks like. These terms sit at different levels, and each level is measured in a different way.
Skills: the specific things people do
A skill is a specific ability to perform a task, and it can be learned and practiced. Asking a good diagnostic question is a skill. So is handling a pricing objection, giving clear feedback, or explaining a premium increase in plain language.
Skills are the smallest unit. They are also the easiest to observe, because you can watch someone do them.
Competencies: skills bundled for a role
A competency groups related skills, along with knowledge and behaviors, into what someone needs to perform well in a role. “Consultative selling” is a competency. It includes questioning, active listening, objection handling, and next-step planning.
Competencies are usually defined by role or job family. They answer the question: what does a strong person in this job look like?
Capabilities: what the organization can reliably do
A capability is something a team or organization can do consistently at scale. “Resolve a complex customer issue on the first call” is a capability. It depends on people’s skills, but also on processes, tools, and how work is organized.
Capabilities answer a different question: what can this organization actually deliver?
Why the level matters for measurement
Each level is measured differently:
- Skill: observe someone doing it and score it. Example: handling a pricing objection.
- Competency: combine the scores across the skills in the bundle. Example: consultative selling.
- Capability: look at team-level performance and business results. Example: first-call resolution.
Most measurement problems come from mixing levels. A manager rates someone “good at communication,” which is too broad to coach or compare. A leader asks whether the organization has a “customer-centric capability” but has no skill-level evidence behind the answer.
Three habits that keep this practical
1. Pick your definitions and stick to them. Different organizations use these words differently, and that is fine. What matters is that everyone in yours uses them the same way.
2. Measure at the skill level first. Skills are specific enough to observe and score, and they roll up into everything above them.
3. Name skills as actions. “Explains an increase in plain terms” is measurable. “Communication” is a category.
Get the levels right and the rest of the series gets easier: assessing skills, mapping them across teams, and tying them to business results.
Next in this series: why skill gaps quietly cost organizations money.
.png)
