Competency Frameworks

Most organisations have a competency framework. A far smaller proportion have one that anyone actually uses. The pattern is familiar: HR invests significant time designing a framework, launches it with good intentions, and watches it gradually disappear from management conversations until it exists only as a policy document and a set of boxes on the annual appraisal form. The framework failed not because the competencies were wrong but because it was designed without the conditions that make adoption genuine rather than nominal.

A competency framework is the structured definition of the knowledge, skills, behaviours, and attitudes that employees need to perform effectively in their roles and to drive the organisation’s strategy. When it is designed well and embedded properly, it provides the common language through which hiring decisions are made, development needs are identified, performance conversations are structured, and talent decisions are taken. When it is designed poorly or launched without proper implementation, it generates compliance paperwork and management cynicism in equal measure.

---

Key Takeaways

Strategy First. A competency framework that does not connect to the organisation’s strategy is a collection of generic descriptors, not a management tool. Every competency in a useful framework should be traceable to a strategic requirement

3 types Core competencies (required of all employees), leadership competencies (required of managers and leaders), and functional or technical competencies (required of specific roles or disciplines). Most frameworks combine all three in a tiered structure

Behaviours Not traits. The most usable competency frameworks are defined by observable behaviours (what a person does) rather than personality attributes (what a person is like). Behaviours can be assessed, developed, and coached. Traits cannot.

Use drives Value. A competency framework that is used only in annual appraisals delivers a fraction of its potential value. Frameworks embedded in hiring, development planning, promotion decisions, and succession planning deliver compounding returns across every people management process

• A competency is a cluster of related knowledge, skills, and behaviours that enables effective performance in a role or at a level of responsibility. Competencies are not the same as skills: a skill is a specific technical capability; a competency is the broader capability that encompasses skills, knowledge, and the behaviours through which they are applied.
• The most effective competency frameworks contain between 8 and 15 competencies per level. More than this creates assessment fatigue and dilutes the signal. Fewer may leave critical capability dimensions undefined.
• Proficiency levels within each competency (typically 3-5 levels, from developing to expert or from entry to senior) allow the framework to describe what effective performance looks like at each career stage without requiring a separate framework for each role.
• The biggest predictor of whether a framework will be used is whether managers had meaningful involvement in its design. Frameworks imposed by HR without manager engagement are systematically less embedded in day-to-day practice than those co-designed with the people who will use them.

---

Step 1: Connect to Strategy Before Defining Competencies

The starting question in building any competency framework is not “what competencies do people need?” It is “what does the organisation need to achieve, and what capabilities do people at each level need to have to make that happen?” This strategy-first orientation produces frameworks that reflect the organisation’s actual direction rather than a generic list of admirable workplace behaviours.

The strategy-to-competency logic follows a clear path: strategic objectives (what the organisation is trying to achieve in the next three to five years) lead to capability requirements (what people need to do differently or better to execute that strategy) lead to competency definitions (the behaviours, skills, and knowledge that constitute those capabilities at each level of the organisation). Competencies defined without this strategic grounding tend to be generic, uncontested, and uninspiring, which is why “communication,” “teamwork,” and “customer focus” appear in almost every framework regardless of what the organisation actually needs its people to do.

For leaders who want to understand how competency frameworks connect to the broader strategic workforce planning picture, our article on how to identify skills gaps in your workforce covers the systematic approach to mapping current capability against strategic requirements that should precede any framework design.

---

---

The Three-Layer Architecture of Most Effective Frameworks

Layer 1: Core Competencies Required of everyone The behaviours and values that the organisation expects from every employee regardless of role or level. These reflect organisational culture and strategic values. Typically 4-6 competencies. Examples: Integrity and ethics, customer focus, continuous learning, collaboration, safety awareness (in high-hazard sectors)

Layer 2: Leadership Competencies Required of managers and leaders The additional behaviours required to lead, develop, and manage others effectively. Applied at different proficiency levels from team leader through to senior executive. Typically 5-8 competencies. Examples: Developing others, strategic thinking, decision-making, influencing and engaging stakeholders, driving change, commercial acumen

Layer 3: Functional / Technical Competencies Role or discipline specific The technical knowledge and specialist skills required for specific roles, functions, or disciplines. Maintained by the relevant function rather than centrally by HR. Typically 5-10 competencies per function. Examples: Financial modelling (Finance), safety management systems (HSE), procurement law (Procurement), machine learning (Data Science)

Writing Competencies That Are Actually Useful

The quality of competency definitions is the most common point of failure in framework design. Vague, aspirational competency descriptions (for example, “demonstrates strong leadership” or “communicates effectively”) provide no guidance on what effective performance looks like and no basis for meaningful assessment. Behavioural competency descriptions provide observable, assessable evidence of each competency at each proficiency level.

A well-written competency definition at a specific proficiency level should answer the question: what would I observe this person doing and saying if they were demonstrating this competency at this level? The answer should be specific enough that two independent assessors would reach substantially the same conclusion about whether a specific piece of behaviour represents this proficiency level.

Example: Communication Competency, Three Proficiency Levels

Level	Behavioural Indicators (what effective performance looks like)
Developing	Shares information clearly in routine contexts. Listens actively and asks questions to check understanding. Structures written communications logically. Adapts style when given feedback that communication has not landed as intended.
Proficient	Proactively adapts communication style and content to the audience without being prompted. Structures complex information clearly for non-specialist audiences. Presents confidently and handles challenging questions directly. Chooses the most appropriate channel and format for each communication.
Expert	Regularly influences senior stakeholder decisions through compelling communication of complex, ambiguous, or contested information. Coaches others on communication effectiveness. Is sought out by peers as a communication advisor. Structures organisational narratives that align and motivate across functions and levels.

Embedding the Framework: Making It Real

A framework only delivers value when it is embedded in the actual processes through which people are hired, developed, evaluated, and promoted. The more processes it touches, the more familiar and genuinely useful it becomes to managers and employees alike.

Hiring and selection: Competency-based interviews (structured questions designed to elicit evidence of specific competency behaviours from past experience) are significantly more predictive of job performance than unstructured interviews. Embedding the framework in job descriptions, interview question banks, and assessment scoring significantly improves hiring quality.

Onboarding: Introducing new joiners to the competency framework during onboarding, explaining what each competency means in the context of this organisation and how it will be used in their development and performance conversations, builds early familiarity and sets expectations about the standard of performance that is valued.

Performance conversations: Structured competency-based performance conversations (discussing specific examples of competency behaviours alongside outcome achievement) are more developmental and more fair than outcome-only appraisals. They focus the conversation on how performance was achieved, not just what was achieved, which is where development insight typically lives.

Development planning: Competency gaps identified through assessment become the basis for individual development plans. This connection between assessment and development is what makes competency frameworks genuinely developmental rather than merely evaluative. Our article on how to create a skills matrix for your team covers the practical tool for tracking competency and skill levels across teams that makes development planning systematic rather than ad hoc.

Succession planning: Competency profiles for key roles define what a successor needs to demonstrate before they are ready to step up. Comparing current competency levels against future role requirements produces the development roadmap that makes succession planning actionable rather than aspirational. Our article on the succession planning framework covers this connection in depth.

---

---

Getting Manager Buy-In: The Critical Implementation Challenge

The most common reason competency frameworks fail to embed is not that they are poorly designed. It is that the managers who need to use them were not sufficiently involved in creating them and do not see them as genuinely useful tools. Managers who regard competency frameworks as an HR imposition rather than a management aid will use them minimally, formulaically, and reluctantly.

Building genuine manager buy-in requires: involving line managers as active contributors to the framework design (not just recipients of consultation), piloting the framework with a small group of engaged managers before full rollout, demonstrating early wins (using the framework to make a hiring or promotion decision that managers agree is better than what they would have done without it), and providing practical tools (interview guides, development conversation starters, assessment scoring rubrics) that make the framework easy to use rather than time-consuming to apply.

The manager capability dimension is equally important. Managers who have not developed the skill to give specific, behavioural feedback, to structure developmental conversations using competency evidence, and to conduct fair, structured assessments, will not use the framework effectively regardless of its quality. Building this capability is part of the implementation plan, not an afterthought. Our article on the manager as a coach covers the conversational skills that make competency-based development conversations genuinely developmental rather than just structured appraisals.

Conclusion: Frameworks That Work Are Management Tools, Not HR Documents

The competency frameworks that become genuinely embedded in organisational practice share a common characteristic: they were designed with the people who will use them, in service of management decisions that genuinely matter, with enough simplicity to be practical and enough specificity to be useful. They are regarded by managers as tools that make difficult conversations easier and hiring decisions better, not as compliance obligations imposed by HR.

Building that kind of framework takes more time than producing a document. It requires genuine engagement with the strategy, the managers, and the evidence about what effective performance actually looks like in this organisation. But the return is a system that compounds over time: every hiring decision made better, every development conversation more focused, every promotion decision more defensible, and every succession plan more grounded in capability evidence rather than familiarity and relationship.

Related reading: A competency framework is most powerful when combined with robust performance measurement. Our article on how to build a KPI framework that actually drives performance covers the performance measurement disciplines that complement competency assessment in a complete people performance system.

---