Core Competency Framework: Definition, Structure and Application
The term "core competency" has been used loosely in two quite different contexts for over three decades, and the confusion causes real problems in practice. In strategy, core competencies are the firm-level capabilities that give an organisation its competitive advantage, popularised by Prahalad and Hamel in their 1990 Harvard Business Review work. In workforce design, a core competency framework means something different and more specific: the set of competencies expected of every person in the organisation, regardless of role, level, or function.
Most organisations that say they have a core competency framework mean the second thing. This article is about that second thing.
What Is a Core Competency Framework
A core competency framework defines the behaviours and standards of performance expected of all employees across an organisation, without reference to a specific role or function. These are the competencies that the organisation considers foundational: how people communicate, make decisions, collaborate, manage their own work, and operate with accountability.
Unlike role-specific or functional competency frameworks, which describe what is required in a particular job or function, a core competency framework describes what is required everywhere. It sits beneath all other workforce expectations as the common baseline.
Like any competency framework, it expresses those expectations as observable, assessable behaviours at different proficiency levels, not as values or aspirations, not as personality traits, and not as a list of tasks.
Why Organisations Need a Core Competency Framework
Without an organisation-wide behavioural standard, performance expectations are set differently in every team, function, and location. What counts as effective communication in one part of the business may be entirely different from what counts as effective communication elsewhere. Managers assess people against different internal standards, and the resulting inconsistency makes it difficult to compare performance, make fair promotion decisions, or build development pathways that apply across the organisation.
Research into competency-based framework development identifies this absence of a shared standard as a persistent barrier to equitable talent management and consistent people development at scale.
A core competency framework solves this by establishing a floor: the minimum behavioural standard that applies to every person, irrespective of what else their role requires. It makes the organisation's expectations explicit, assessable, and consistently applied.
How a Core Competency Framework Works in Practice
A well-designed core competency framework typically includes four to eight competencies. The number must be small enough for managers and employees to genuinely engage with and large enough to cover the dimensions of performance that matter most across the organisation.
Each competency is defined with behavioural indicators at multiple proficiency levels. The standard structure uses three to five levels, describing what the competency looks like for someone new to the organisation through to someone operating at an experienced or senior level. Deciding what behaviours are genuinely observable and distinguishable at each level is the hardest part of the design process.
Common core competencies across well-designed frameworks include communication and stakeholder engagement, collaboration and working with others, problem-solving and decision-making, accountability and delivery, and continuous learning and adaptability.
The specific competencies chosen must reflect the organisation's actual operating context. A public sector organisation will make different choices than a technology start-up, even if the broad categories look similar.
Guidance from the CIPD on competency frameworks emphasises that the value of any competency framework depends on its integration into performance, development, and hiring processes, not its existence as a document. A core competency framework that informs real conversations but sits outside the performance cycle has failed.
What a Core Competency Framework Is Not
A core competency framework is not a values framework. Organisational values describe what the organisation believes in, things like integrity, customer focus, or respect. A core competency framework describes how people are expected to behave. These are related but distinct. An organisation can have both and should not conflate them.
It is not a skills taxonomy or a skills inventory. A skills taxonomy catalogues what people can do, often tied to technical domains. A core competency framework describes how people do things, the behavioural qualities that are expected across the organisation regardless of technical domain.
It is not a capability framework. Capability frameworks describe what organisations require to performed effectively in the future, typically tied to functions or role families. Core competency frameworks describe what every person in the organisation is expected to bring to any role. The distinction is consequential: capability describes what demands are needed to perform in the future; core competency describes what a person must demonstrate.
It is not a leadership framework. Leadership competency frameworks describe what is required of people who lead others. Core competency frameworks describe what is required of everyone, including leaders, but the leadership requirements sit on top of the core, not as a replacement for it.
Named Frameworks and Standards
Several well-known models treat core competencies as a distinct layer within a broader competency architecture.
Korn Ferry (Lominger): The Lominger model organises its 67 competencies into factors, clusters, and individual competencies. Organisations using Lominger typically identify a subset of eight to twelve competencies as their "core", required of everyone, and then layer in additional functional or leadership competencies on top. This is the most widely deployed approach to structuring core competency frameworks in enterprise organisations.
CIPD Profession Map: CIPD's model for HR professionals includes a set of core behaviours expected of every HR practitioner regardless of specialisation. These include ethical practice, professional courage, and valuing people. The approach provides a useful reference model for how to differentiate core from specialist expectations in a framework.
SHRM Competency Model: SHRM organises its competencies for HR professionals into a similar architecture, with ethical practice as the core competency at the centre and behavioural and technical competencies layered around it. The explicit centring of one universal competency is a deliberate structural choice that reflects the organisation's view of what is non-negotiable at every level.
Research on competency modelling validation suggests that the selection of core competencies should be empirically grounded, not derived solely from stakeholder opinion or leadership aspiration. The competencies chosen should predict performance across a wide range of roles and contexts.
Common Failure Modes
The most frequent failure in core competency framework design is including too many competencies. Organisations that list fifteen or twenty competencies as "core" have produced a list, not a framework. A competency only functions as a performance standard if managers and employees can engage with it meaningfully in real conversations. Five or six well-chosen competencies will outperform twenty poorly differentiated ones in every context.
The second failure is writing competencies at such a high level of abstraction that they cannot be assessed consistently. "Demonstrates integrity" or "thinks strategically" sound like competencies but function as aspirations. Competencies must be expressed as specific, observable behaviours, not as qualities that require inference to detect.
The third failure is designing the framework for a single process and then trying to extend it. A framework built specifically for a performance review cycle will not translate easily into hiring rubrics, development planning, or succession assessments without significant retrofitting. Well-designed core competency frameworks are built for integration from the start.
Trade-offs and Constraints
The main trade-off in core competency framework design is between universality and precision. The more applicable a competency must be across the entire workforce, the more it must be expressed at a level of abstraction that may feel generic to any particular function or role. Organisations that try to make core competencies too specific will find they work well for one population and poorly for others.
This is why capability framework design and core competency framework design are typically treated as complementary rather than competing exercises. The core competency framework sets the universal behavioural baseline. Function-specific frameworks add the technical and contextual layers that the core cannot carry.
There is also a maintenance burden. Core competencies must remain relevant as the organisation's strategy and operating environment change. The competencies that made sense during a period of rapid growth may not be the same ones that matter most during consolidation, regulatory change, or significant technology adoption.
Frequently Asked Questions
What is the difference between a core competency framework and a competency framework?
A competency framework can apply to a specific role, function, or level. A core competency framework applies to every person in the organisation, regardless of their role or function. It represents the baseline expected of all employees.
How many competencies should a core competency framework include?
Four to eight is the practical range. Fewer risks leaving out dimensions of performance that genuinely matter. More risks producing a framework too unwieldy for consistent use in day-to-day performance and development conversations.
What is the difference between core competencies and organisational values?
Values describe what the organisation believes in. Competencies describe how people are expected to behave. Both matter, but they serve different purposes and should not be merged into a single framework. Conflating them tends to produce something that does neither job effectively.
Can a core competency framework be used for recruitment?
Yes, and this is one of its most valuable applications. Structured behavioural interviews built around core competencies produce significantly more reliable hiring decisions than unstructured interviews, particularly for candidates being assessed for behavioural fit rather than technical capability.
How often should a core competency framework be reviewed?
Every two to three years in a stable operating environment. If the organisation undergoes a significant strategic shift, merger, or change in workforce composition, a review should be triggered by the change rather than the calendar.
Is a core competency framework the same as a core skills framework?
No. A core skills framework catalogues the technical skills that are foundational across the organisation. A core competency framework describes the behavioural standards expected of everyone. Both are useful, but they describe different things and serve different purposes in talent management.