Competency framework: a definition
A competency framework is a structured list of the competencies an organisation expects, with a description of what each one looks like at each level. It gives everyone a shared language for "what good looks like" in a role, which then drives recruitment, development, appraisals and career paths.
A competency is broader than a skill: it combines skills, knowledge and behaviour. "Uses Excel" is a skill; "analyses data to make sound decisions" is a competency. See skills matrix vs competency matrix for more on the difference.
What a competency framework contains
Competencies
Usually grouped into core (everyone), functional (per team) and leadership competencies.
Definitions
One or two sentences on what each competency means in your organisation.
Proficiency levels
Three to five levels, each with observable behaviours that show it.
Role profiles
The level of each competency required for each role or grade.
An example competency with levels
| Level | Problem solving: observable behaviour |
|---|---|
| 1. Developing | Identifies problems and escalates them with the relevant facts. |
| 2. Proficient | Solves routine problems independently and finds the root cause, not just the symptom. |
| 3. Advanced | Solves complex, unfamiliar problems and prevents them recurring through process changes. |
| 4. Expert | Anticipates problems across teams and coaches others in structured problem solving. |
Notice that each level describes something you could observe. That's what makes ratings consistent between managers.
Competency framework vs skills framework
A competency framework describes broad, fairly stable capabilities tied to roles and values. A skills framework (or skills taxonomy) lists the specific, more fast-changing skills people use, such as tools, systems, methods and certifications. Competency frameworks are best for role design and progression; skills frameworks are best for training, resourcing and compliance. Many organisations link the two: each competency is backed by the specific skills that demonstrate it.
How to build a competency framework
- Agree the purposeRecruitment, appraisals, career paths, compliance? It decides how detailed you need to be.
- Gather inputTalk to managers and strong performers in each role about what actually makes the difference.
- Draft a short listAim for around 6 to 12 competencies per role. More than that and nobody uses it.
- Write behavioural levelsFor each competency, describe observable behaviour at each level.
- Map rolesSet the expected level of each competency for each role or grade.
- Test, launch and reviewPilot with one team, refine the wording, then review at least yearly.
Putting the framework to work
A framework on its own is a document. It becomes useful when people are rated against it and the results feed decisions, which is where a skills or competency matrix comes in. Rate people against the levels, compare with the role profile, and the difference is your skills gap.
Set up skill groups per team, categories for core, technical and behavioural competencies, and a rating scale with your own level names. People rate themselves, managers confirm, and objectives track progress towards the levels you need. See how it works.