A job advert asks for “strong communication skills”. A manager says a candidate lacks “the right competencies”. A coach tells you to “build your abilities”. Three words, used as if they meant one thing. They do not, and mixing them up causes quiet mistakes: hiring for the wrong thing, or spending a month on a course that was never going to fix the problem you actually have.
Ability: the capacity you bring before anyone teaches you
An ability is an underlying capacity. Examples are picking up patterns in numbers quickly, holding several pieces of information in mind at once, or following a spoken argument while thinking about your reply. Abilities are general rather than tied to one job, and they tend to change slowly compared with skills.
At work an ability shows up as ease. Someone who sees at a glance how the pieces of a schedule fit together is showing an ability, even if they have never been trained in scheduling. Ability can make learning faster, but it does not settle where anyone ends up, because practice and circumstances matter too.
Skill: something you learned to do and can demonstrate
A skill is a specific thing you have learned to do. Building a pivot table, writing a database query, drafting a clear client email, running a retrospective: each is a skill. Skills are concrete and usually checkable. You can hand someone a task and watch, or look at a piece of finished work.
That checkability is why skills dominate resumes and job adverts. It is also why they are an incomplete answer. Two people can both be skilled at running a team meeting, and one of them reliably sends the notes afterwards while the other does so when they remember. The skill is the same; something else differs.
Competency: knowledge, skill and behavior in a real situation
That “something else” is what competency models try to capture. A competency is a bundle: the knowledge you need, the skills you can apply, and the behavior you actually show, all in a particular context. The context is not decoration. “Handling a customer complaint” means something different at four o’clock on a Friday with an angry customer than it does in a training role-play.
- Knowledge: you know the refund policy and where the exceptions are.
- Skill: you can write a calm, clear reply and settle a heated call.
- Behavior: you pick the complaint up promptly, stay steady, own the problem and follow up when you said you would.
Knowledge and skill are about what you could do. Behavior is about what you reliably do. A self-rating like the Competency Test sits on the behavior side of the bundle: it asks how often you act in particular ways, not whether you are able to.
What goes wrong when the three get swapped
Take a Monday stand-up where one colleague’s updates are always vague. The problem could be a gap in knowledge (they do not understand the system well enough to describe it), a gap in skill (they have never learned to structure a short update), or a gap in behavior (they know and can, but avoid saying where they are stuck). Each calls for a different fix.
- In hiring. An advert asks for a software tool because tools are easy to list, when the real problem on the team is that handovers are undocumented. The new hire has the skill and the problem remains.
- In self-development. You tell yourself you are “bad at follow-up”, sign up for a course on project tools, finish it, and still let messages sit. The missing piece was a habit, not a tool.
- In feedback. “You need better communication skills” can mean anything from “write shorter emails” to “speak up in meetings”. Without asking which, you may fix the wrong thing.
A useful habit: when someone names a gap, ask whether it is something you do not know, something you cannot yet do, or something you can do but do not do reliably.
Why organizations define competencies differently
There is no single agreed list of competencies, and no single agreed way to build one. Industrial and organizational psychologists who examined how organizations build competency models found that practice varied widely from one organization to the next (Shippmann et al., 2000). Later work set out guidance for doing it well, such as basing competencies on careful analysis of the work itself (Campion et al., 2011).
In practice this means one employer’s “communication” may be a list of observable behaviors, and another’s may be a vague heading that mixes in writing skill and general confidence. When an advert or a review form uses the word, look for the examples under it, or ask what someone would be seen doing. And treat any set of six, including the one on JobCannon, as one reasonable way of cutting the same territory, not as the definition.
Where the Skills Audit and the Competency Test fit
On JobCannon the two tools split the territory. The Skills Audit inventories skills: what you can do. The Competency Test rates behaviors: how often you act in six ways at work. Neither measures ability, and the Competency Test is a self-rating that is not a validated instrument and does not predict job success.
Used together they can show a useful mismatch. A long list of skills with a low planning rating suggests you can do the work but do not yet do it in a reliable way. The reverse, strong habits and a thin skills list, suggests the next step is learning, not discipline. For what a result means, see what a competency test is; for the six areas themselves, the six core work competencies.