Skills vs. Competencies vs. Proficiency
Skills, competencies, and proficiency are three different kinds of record: a skill is a unit of ability, a competency is an outcome-shaped bundle of them, and proficiency is the measurement applied to either.
By Samantha, SkillsDB|Published |Updated
What It Is
The three terms answer three different questions. A skill answers "what can this person do?" and is the smallest unit an organization tracks, such as reading a wiring schematic. A competency answers "what outcome does the role need, and what combination of skills, knowledge, and behavior produces it?" and is defined per job family in the organization's own words. Proficiency answers "how well, right now?" and is a level on a scale attached to a skill or a competency, always with a date and a method behind it. Programs get into trouble when the terms blur: skills lists grow into unmanageable catalogs because competencies were never defined, competencies are written too broadly to assess because the skills inside them were never named, and proficiency becomes one number per person because it was never attached to anything specific. Keeping the three separate is what lets gaps, matrices, plans, and audits all read from the same record.
Key Facts
- A skill is the unit of ability; a competency is a role-shaped bundle of skills; proficiency is the measurement on either.
- Skills are owned by the skills library; competencies are owned by the job family or role framework; proficiency is owned by the assessment process.
- A typical role carries 6 to 12 competencies, each drawing on 3 to 8 skills.
- Proficiency uses one scale across skills and competencies, most often 0 (N/A) to 5.
- "Competence" names a person's general capability to do the work; "competency" names the defined, assessable thing an organization writes down.
- All three decay, for different reasons: skills through lack of practice, competencies through role change, proficiency through elapsed time since assessment.
Six Attributes Side by Side
| Attribute | Skill | Competency | Proficiency |
|---|---|---|---|
| Unit | One learnable ability | A bundle tied to a work outcome | A level on a scale |
| How many per role | 20 to 60 | 6 to 12 | One per skill or competency |
| How it is measured | Assessed at a level, or present/absent | Assessed at a level against descriptors | It is the measurement |
| Who defines it | Skills library owner, usually L&D | Job family or role owner with practitioners | The assessment method and its rubric |
| Changes when | Tools, procedures, or standards change | The role or its outcomes change | Time passes or a new assessment is recorded |
| Lives in | The skills library | The competency framework | The person-to-skill or person-to-competency record, with date |
How SkillsDB Models It
SkillsDB keeps the three as separate primitives. A Skill such as Root Cause Analysis lives once in the Skills Library, with Labels for filtering and a count of the people and careers that use it. A competency is structural: a Section named Problem Solving inside a Maintenance Technician career groups Root Cause Analysis with two neighbors, and each skill in it carries a benchmark grade per Level. Proficiency is the grade itself, recorded per person per skill on the organization's grading scale: an employee grade from the self-assessment and a manager grade from the manager assessment, kept side by side. So when a technician's manager grades Root Cause Analysis at 2 against a Level 2 benchmark of 3, the technician sees a red pill on her Skills Profile and the manager sees the same red cell in the Skills Matrix under Problem Solving. Raising the benchmark rewrites no grades, and a reassessment touches no definitions. See the Skills Library and Competency Frameworks.
Related
Three words. Three records. One system.
See how SkillsDB keeps skills, competencies, and proficiency as distinct primitives that still add up.
Book Demo