A competency framework should make everyday people decisions easier, not create another HR document that managers rarely open. Knowing how to create a competency framework that employees and leaders can genuinely use starts with a clear view of the work that drives organisational performance.
For many organisations, the need becomes obvious when expectations vary between managers, promotion decisions feel inconsistent, or training is selected without a shared picture of the capabilities people need. A well-designed framework brings structure to these decisions while still allowing for the different demands of roles, teams and career stages.
Start with the business problem, not a list of skills
A competency framework defines the knowledge, skills, behaviours and personal attributes required for effective performance. It gives the organisation a common language for what good performance looks like, from entry-level roles through to senior leadership.
The first question is not, “Which competencies should we include?” It is, “Which workforce decisions do we need this framework to improve?” The answer may be workforce planning, leadership development, recruitment, succession planning, performance conversations, or a combination of these.
This distinction matters. A framework designed primarily to improve customer experience will give greater weight to service recovery, communication and relationship management. One created to support growth into new markets may prioritise commercial awareness, adaptability and strategic thinking. If every possible competency is included, the framework becomes difficult to apply and less useful to managers.
Agree the intended outcomes with senior leaders, HR and a representative group of line managers before drafting anything. Set practical measures of success too. For example, you may expect managers to use the framework in annual reviews, see clearer development plans within six months, or improve consistency in interview assessment.
Build the right structure for your organisation
Most frameworks work best when they have a small number of competency groups. The exact structure depends on the organisation, but it commonly includes core competencies for all employees, functional competencies for particular job families, and leadership competencies for people managers and senior leaders.
Core competencies reflect how people are expected to work across the organisation. They may include collaboration, accountability, communication or customer focus. Functional competencies describe the expertise required in specific areas, such as HR operations, finance, sales, administration or technical delivery. Leadership competencies focus on the ability to set direction, develop people, manage performance and lead change.
Avoid treating seniority as the only difference between levels. A more senior employee is not simply expected to demonstrate the same behaviour more often. Their contribution may shift from completing tasks well to improving systems, influencing stakeholders and building the capability of others.
A concise framework is usually more effective than an exhaustive one. As a working guide, many organisations can operate well with six to ten core competencies, supported by targeted functional and leadership content. The right number depends on the size, complexity and purpose of the business, but clarity should take priority over completeness.
Gather evidence from the workplace
The strongest competency frameworks are grounded in the reality of the organisation, rather than copied from a generic template. Existing job descriptions, performance appraisal forms, customer feedback, operating procedures, business plans and training records are valuable starting points.
Then speak to people who understand the work. Interview high-performing employees, experienced managers and key internal stakeholders. Ask what separates reliable performance from exceptional performance, where new employees commonly struggle, and which behaviours create problems when they are absent.
It is also useful to examine roles that are changing. Automation, new reporting requirements, shifting customer expectations and hybrid working arrangements can all alter the capabilities a role requires. A framework should reflect the organisation’s future direction, not only its current job descriptions.
When gathering input, distinguish between an individual’s personal style and behaviour that can be observed, developed and assessed. “Confident” is open to interpretation. “Presents recommendations clearly, responds constructively to questions and adapts the message for the audience” is more specific and more useful.
Write clear competency definitions and behavioural indicators
Each competency needs a plain-language definition followed by behavioural indicators. The definition explains the capability. The indicators show what it looks like in practice.
For example, a competency called “Collaborative Working” might be defined as building productive relationships and contributing to shared outcomes across teams. At an individual contributor level, observable indicators could include sharing relevant information promptly, asking for input from colleagues and following through on agreed actions. At a management level, indicators may include resolving cross-team priorities, creating conditions for open communication and aligning teams around a common outcome.
Good behavioural indicators are specific enough to guide a performance conversation, but not so narrow that they become a checklist. Use action-based language such as “analyses”, “explains”, “prioritises”, “challenges” and “develops”. Avoid vague terms such as “has a positive attitude” or “is a team player”, as different managers may interpret them differently.
A useful test is whether a manager could answer three questions from the wording alone: What would I see this person do? What would weaker performance look like? What support would help them improve?
Set proficiency levels with care
Proficiency levels allow the same competency to apply across different roles while making expectations proportionate. They are often described as foundation, working, proficient and advanced, although the labels matter less than the distinction between them.
At foundation level, an employee may apply a skill with guidance in familiar situations. At proficient level, they work independently, handle more complex situations and support colleagues. At advanced level, they may set standards, solve unfamiliar problems and shape practice across the organisation.
Do not create levels simply by adding words such as “more” or “consistently”. The behaviours should reflect a meaningful increase in scope, judgement, influence or accountability. This is especially important for leadership competencies, where a manager’s ability to develop others and make sound decisions under pressure cannot be assessed through task completion alone.
Not every competency needs every level. A specialist role may require advanced technical expertise but only a working level of budget management. Mapping requirements role by role prevents inflated expectations and gives employees a realistic development path.
Validate before rolling out the framework
Before final approval, test the draft with a cross-section of users. Ask managers whether the language reflects real performance expectations and whether they could use it in recruitment, feedback and development discussions. Ask employees whether they understand what progression looks like.
This stage often identifies hidden problems. Two departments may use the same term differently, or a competency may unintentionally favour a particular communication style rather than the outcome required. Validation also helps build ownership, which is essential when managers will be expected to use the framework consistently.
A pilot with one business unit can be sensible when the organisation is large or the framework introduces a significant change to performance management. A smaller organisation may instead validate through focused workshops and refine the framework before wider communication.
Embed it in people processes
A competency framework only creates value when it is used. Build it into the moments where people make decisions: job design, hiring, induction, probation reviews, performance discussions, learning plans, promotion assessments and succession conversations.
Managers need practical support, not just a copy of the framework. Briefing sessions should show them how to use behavioural indicators to give balanced feedback, identify development needs and avoid rating employees according to personal preference. Calibration discussions between managers can further improve fairness, particularly where performance ratings inform pay or promotion.
Training should also be connected to identified capability gaps. If a group of new managers needs stronger coaching skills, for example, the development programme should be followed by workplace application, manager feedback and opportunities to practise. This makes learning visible in performance rather than leaving it as a course attendance record.
Review the framework as the organisation changes
Competency frameworks need governance. Assign clear ownership, usually within HR or a people development function, and schedule a review at least annually. Review sooner when strategy, roles or operating models change substantially.
Look for evidence of use. Are managers referring to the framework in appraisals? Are development plans becoming more focused? Do employees understand the skills needed for their next role? If the framework is not influencing these conversations, the issue may be the language, the level of manager capability or the way it has been introduced.
Creating a framework takes thoughtful consultation, but it should ultimately simplify work for everyone involved. When expectations are clear and applied fairly, employees can take ownership of their growth, managers can lead with greater confidence, and the organisation can invest in capability where it will make the greatest difference.