Competency Framework: Define Performance Expectations at Every Level
A competency framework gives managers a shared, observable definition of what good performance looks like at each level of a role, so that hiring, developmen…
Topic: People Management
Why It Matters
Promotion conversations are where vague expectations become expensive. When a team member asks what it would take to reach the next level and the honest answer is "more of the same, but better", your credibility takes a hit. The same gap shows up in hiring panels that cannot agree what "senior" means, and in reviews that reward visibility over contribution.
A competency framework closes that gap by writing down what good looks like at each level of a role family. It turns private judgement into shared, explicit criteria.
Used well, it gives managers a common language for hiring, development, performance and progression, and gives employees a visible path instead of a guessing game.
The need has grown as structures flatten, roles change faster and employees expect transparency about how career decisions are made.
A competency framework is also the usual foundation for a capability matrix, which maps individuals against the framework's dimensions to show where team strength sits and where the gaps are.
Before reading further, it is worth checking whether this addresses a problem you actually have. Consider these questions.
Have two people at the same grade in your area been assessed against noticeably different standards, with nobody able to explain why?
When someone asks what separates their level from the next one, do you find yourself describing people you admire rather than behaviours you can observe?
Are you about to build a skills or capability matrix and unsure where its dimensions should come from?
Origin & Underlying Logic
A competency framework is a formal organisational definition of the behaviours, skills and knowledge expected at each level of a role family. Each competency is named, defined, and broken into proficiency levels described through observable indicators.
The idea traces to psychologist David McClelland, who argued in the early 1970s that aptitude tests predicted job performance poorly. He proposed identifying the competencies that distinguished superior performers instead.
Richard Boyatzis extended the work to management roles in the early 1980s, and the approach spread through HR practice from there.
The underlying logic is simple: performance is driven by behaviours that can be described, observed and developed. Defining them consistently reduces the influence of impression and personal preference, and links people decisions to what the organisation needs.
The shift it asks of a manager is from "Do I rate this person?" to "What evidence have I seen against an agreed description?" Related approaches include job architecture, career ladders, skills taxonomies, behavioural interviewing and the capability matrix.
Structure & Application
The frameworks share the same building blocks, even when the terminology differs. Understanding what each one does makes it easier to judge whether a framework you inherit is fit for purpose.
Competency clusters: broad groupings such as technical expertise, client impact, leadership or commercial judgement. They keep the framework navigable.
Competency definitions: a one or two sentence statement of what each competency means in this organisation, not in general.
Proficiency levels: usually four or five stages, mapped to grades or career stages, describing how the competency grows in scope and complexity.
Behavioural indicators: observable examples of what someone does at each level. This is where frameworks succeed or fail.
Role mapping: which competencies apply to each role, and at what level.
These elements depend on each other. Clusters without sharp definitions blur together; levels without concrete indicators collapse into adjectives such as "good", "strong" and "exceptional". The indicators are what make assessment fair, because two managers can point at the same evidence.
Variations are common. Some organisations separate core competencies (expected of everyone) from functional and leadership competencies. Others build separate frameworks per role family, and newer approaches lean towards granular skills taxonomies. The tool is designed at organisational or function level but lives or dies at team level, where managers apply it in real conversations.
The typical format is a grid: competencies down the side, levels across the top, indicators in the cells. A well-built competency framework fits on a few pages per role family.
If yours needs a binder, it will be referenced rarely and trusted even less. The aim is a document a manager can open during a one-to-one and use to anchor a specific conversation about evidence and next steps.
Quick-start: Pick one role family you manage and write down three things that genuinely separate your strongest performer from a solid performer at the same level, in terms you could observe. Then ask yourself which of those belong in a framework, and which are simply that person's style. Separating the two is harder than it looks, and it is where proper implementation begins.
FAQ
Q: What is a competency framework?
A: A competency framework is a structured definition of the behaviours, skills and knowledge expected in a role family, set out across proficiency levels. It describes what good performance looks like at each stage of a career path, using observable indicators. Organisations use it to make hiring, development, performance and promotion decisions more consistent and easier to explain to employees.
Q: What is the difference between a competency framework and a capability matrix?
A: A competency framework defines the standard: which competencies matter and what each level looks like. A capability matrix applies that standard to real people, mapping each team member's current level against the required level for their role. The framework is the reference; the matrix is the snapshot. A capability matrix built without a framework tends to rely on inconsistent, subjective ratings.
Q: What types of competencies does a framework usually include?
A: Most frameworks combine three types. Core competencies apply to everyone and often reflect organisational values. Functional or technical competencies relate to a specific discipline, such as financial analysis or software engineering. Leadership competencies describe how people manage others, make decisions and shape direction. The balance between them should reflect what genuinely drives success in the roles being described.
Q: Is a competency framework worth it for a small team?
A: For a team of fewer than about eight people with one manager, a full framework is often more structure than the situation needs. A clear role expectations document per level can deliver most of the benefit. The case strengthens as soon as several managers are assessing people in the same roles, or when you are preparing for growth.
Q: How do I know if a competency framework is right for my situation?
A: Look for symptoms of inconsistency. If promotion decisions are questioned, if managers rate similar performance differently, or if people cannot describe how to progress, a framework is likely to help. If the real issue is pay, workload or a specific manager's capability, a framework will not fix it. Diagnosing the true problem first saves months of wasted effort.