Competency Framework Guide: How to Build One That HR Teams Actually Use
A practical guide to designing a competency framework that survives contact with your organisation - from defining competency levels to embedding them in hiring, reviews, and development plans.
Most competency frameworks end up in a shared drive folder no one opens. They get built in a six-month project, launched at an all-hands, and quietly abandoned by the time the first performance cycle comes around. This guide is about building one that doesn't.
What a Competency Framework Actually Is
A competency framework is a structured description of the behaviours, skills, and knowledge that make people effective in your organisation - and at different levels within it. It answers the question: "what does good look like here?"
Done well, it connects hiring criteria, performance evaluation, development conversations, and promotion decisions to a consistent language. Done badly, it's a jargon document that nobody trusts.
The distinction usually comes down to whether the framework reflects how people actually work, or how someone in an HR project workshop imagined they work.
Before You Build: Three Questions to Answer
Who is this for? A framework for a 50-person professional services firm is not the same as one for a 3,000-person logistics company. Scope early. Covering every role with one framework usually produces something generic enough to be useless for all of them.
What decisions will it inform? If the answer is "performance reviews only," you can build something lean. If it also feeds hiring rubrics, promotion criteria, and L&D planning, you need more structure. Design for use cases, not completeness.
Who needs to believe it? A framework only works if line managers trust it enough to have real conversations from it. This means involving them in design, not just sign-off.
The Core Components
Competency Categories
Most effective frameworks organise competencies into two to three categories:
- Functional competencies - role or function-specific skills. Data analysis for analysts, sales methodology for account executives, clinical skills for healthcare roles.
- Behavioural competencies - how people work across roles. Communication, problem-solving, collaboration, adaptability.
- Leadership competencies - relevant for people managers and senior contributors. Strategic thinking, developing others, decision-making under uncertainty.
Keep the total number manageable. Eight to twelve competencies per category is usually the ceiling before the framework becomes unwieldy.
Proficiency Levels
Every competency needs levels - usually three to five - that describe what the competency looks like as it develops. Levels should be behavioural, not aspirational.
Bad level description: "Demonstrates excellent communication skills."
Good level description: "Adapts communication style to the audience - simplifies complex topics for non-specialists, uses technical precision when communicating with specialists. Proactively flags ambiguity rather than proceeding on assumptions."
The test: could a line manager and an employee independently read the level description and agree on whether the employee meets it? If not, rewrite it.
Behavioural Indicators
Below each level, list two to four specific observable behaviours. These are the evidence base for conversations and assessments. They should describe actions, not traits.
Trait: "Is a good listener." Behaviour: "Asks clarifying questions before proposing solutions. Summarises what they heard to check understanding before moving on."
Building the Framework
Step 1: Research
Talk to people who are genuinely excellent at the roles you're mapping. Ask: "Walk me through a recent project you're proud of. What made the difference?" Extract the behaviours that appear consistently. Talk to their managers too - ask what separates high performers from average performers in concrete, observable terms.
This is the part that gets skipped. Don't skip it.
Step 2: Draft
Group the behaviours into competency themes. Write level descriptions working upward from foundation to advanced. For each level, ask: "what does the person at this level do differently from the level below?"
Draft with two to three competencies first. Get feedback before building out the full set.
Step 3: Calibration Workshops
Run workshops with a mixed group of managers. Give them example employees (anonymised) and ask them to rate using the draft framework. Where do people disagree? That disagreement reveals where your level descriptions are ambiguous or your behavioural indicators are missing.
Expect two to three rounds of revision.
Step 4: Integration
A framework in isolation does nothing. Build it into:
- Job descriptions - use competency language to describe what you're hiring for
- Interview guides - map behavioural interview questions to competencies and levels (ATS platforms with skills intelligence like Talecto can automatically score candidates against competency-based criteria at screening stage, before interviews even begin)
- Performance review templates - replace vague rating scales with competency-based self-assessments
- Development planning - use the framework to structure conversations about where someone wants to grow
Common Failure Modes
Too many competencies. Reviewing 20 competencies twice a year is a checkbox exercise. Eight to ten competencies that you take seriously is better than twenty you rush through.
Generic behavioural language. If every company in every industry could use your behavioural indicators unchanged, they're not grounded enough in how your organisation actually works.
No maintenance plan. Roles change. New skills become critical. A framework from 2022 will start misfiring by 2025 if nobody owns updates. Assign an owner and schedule annual reviews.
HR owns it, managers don't. If line managers see the framework as an HR tool imposed on them, they'll fill in the forms and ignore the substance. The framework needs to be useful to managers for their own conversations - not just useful to HR for reporting.
Keeping It Alive
The organisations that get long-term value from competency frameworks treat them as living documents, not finished products. They:
- Update competencies when role requirements change significantly
- Check inter-rater reliability periodically - are managers using levels consistently?
- Use data from performance cycles to spot competencies that never differentiate (which usually means the descriptions are too vague to assess)
- Connect L&D offerings explicitly to competency gaps at the team and individual level
A competency framework that people trust enough to have honest development conversations is one of the most valuable tools an HR function can build. The barrier isn't complexity - it's the discipline to keep it grounded in how work actually happens.
A competency framework is most useful when paired with a skills gap analysis that tells you where your workforce currently sits against the levels you've defined, and a learning and development strategy that closes those gaps deliberately.