What Is a Competency?
A competency is a named, leveled cluster of abilities, knowledge, and behavior a role needs to deliver a specific work outcome, written so an assessor can judge how well someone performs it.
By Samantha, SkillsDB|Published |Updated
What It Is
A competency groups the things a person must know, do, and show to achieve a result the organization depends on. Where a skill names one ability, a competency names the outcome and the abilities behind it. "Configure a firewall rule" is a skill; "Deliver network changes without unplanned outages" is a competency that draws on several skills plus the judgment to sequence and verify them. Every competency carries a scale, usually the same 0 to 5 scale used for skills, with level descriptors written as observable behavior rather than adjectives. A role states the level it requires for each competency; an assessment records the level a person demonstrates; the difference is the gap that development closes. Competencies are written in the organization's own language, because a definition imported from a generic catalog rarely matches how the work is actually done and is quietly ignored by the managers meant to use it.
Key Facts
- A competency has three parts: the outcome, the skills and knowledge behind it, and the leveled behavior that shows it.
- Most roles are described by 6 to 12 competencies; more than that and assessment stops being done consistently.
- Four working types are used in practice: core, functional, leadership, and behavioral; a role usually mixes at least three.
- Competencies are leveled on the same scale as skills, 0 (N/A) to 5, so a person's record reads consistently across both.
- The required level is a property of the role; the assessed level is a property of the person; neither is meaningful without the other.
- A competency definition is complete only when two assessors reading it would place the same person at the same level.
The Four Types of Competencies
| Type | What it covers | Example | How it is assessed |
|---|---|---|---|
| Core | Behavior expected of everyone, regardless of role | Acting on safety observations before the shift ends | Manager observation against a common rubric |
| Functional | The technical work a job family exists to do | Diagnosing and restoring cooling capacity in a live data hall | Practical demonstration or work-sample review |
| Leadership | Directing, developing, and deciding for others | Running a shift handover so that open risks transfer with names and deadlines | manager and stakeholder input plus outcome evidence |
| Behavioral | How work gets done under pressure and with others | Escalating a deviation within the agreed window even when the cause is unclear | Incident and review records over a period |
How SkillsDB Models It
In SkillsDB a competency is a Section inside a Career: a named group of Skills from the Skills Library, each carrying its own benchmark grade; the Career itself can be a job role, a competency group, or a success profile. Take a Nurse Clinician career with a Patient Assessment section holding three skills on a 1–5 grading scale: Vital Signs Interpretation benchmarked at 4, Triage Decision-Making at 3, Documentation at 3. A nurse assigned to the career sees each skill on her Skills Profile with a grade pill, green where her manager grade meets or exceeds the benchmark, red where it falls short, gray where nothing has been recorded. Her manager grades the same three skills in a manager assessment, then opens the Skills Matrix, where Patient Assessment is a column group header over its skills: the competency reads as a cluster of cells, not one score. Benchmarks can differ by Level, and a manager can set a Custom Benchmark for one person. See Competency Frameworks and the Skills Library.
Related
Define good. Then measure against it.
See how SkillsDB turns competency definitions into leveled assessments a manager can defend.
Book Demo