Competency Model: Definition, Purpose, Examples, and How It Differs from a Framework

The term competency model is used constantly in HR, learning, and workforce design. It is also one of the most consistently misused constructs in the field.

In practice, I see competency models confused with competency frameworks, job descriptions, values statements, performance scorecards, and even training curricula. The result is predictable: unclear role expectations, inconsistent assessment, and endless debate about what “good” actually looks like in a role.

This article is intentionally precise. It does not try to sell competency models as a cure-all. Instead, it explains:

• What a competency model actually is
• How it differs from a competency framework
• What belongs inside a competency model — and what does not
• How competency models should be built and used in practice
• The most common mistakes that cause them to fail

If you are designing roles, assessing performance, or building development pathways, this distinction is not academic. It is operational.

What is a competency model?

A competency model is a role-specific or cohort-specific application of competencies that defines the abilities required for effective performance in a particular context.

A competency model does not invent competencies.
It selects, applies, and contextualises competencies drawn from a broader system.

In practical terms, a competency model answers this question:

What competencies, at what level, are required for success in this specific role or group?

A competency model is an applied profile that specifies which competencies are required for a particular role, level, job family, or cohort, and the proficiency level expected for each. Competency models typically draw from an organisation-wide competency framework and tailor expectations and indicators to a defined context.

The purpose of a competency model

Competency models exist to translate shared structure into role-level clarity.

A competency framework provides consistency across the organisation. A competency model provides relevance.

Used properly, competency models:

• clarify role expectations
• support structured hiring and selection
• provide a stable reference for performance conversations
• inform targeted development planning
• enable fair, role-based assessment

Without models, frameworks remain abstract.
Without frameworks, models become inconsistent and idiosyncratic.

Competency model vs competency framework

This distinction underpins the entire cluster and must be explicit.

Competency framework

• Organisation-wide in scope
• Defines shared competency language
• Includes domains, definitions, proficiency levels, and governance rules
• Changes infrequently

Competency model

• Role-, level-, function-, or cohort-specific
• Applies selected competencies from the framework
• Sets target proficiency levels for a defined context
• Changes as roles evolve

Put simply:

Frameworks standardise.
Models contextualise.

If every role has bespoke competency definitions, you do not have competency models. You have fragmentation disguised as structure.

How competency models are built

A defensible competency model follows a repeatable design logic. Skipping steps is the fastest way to undermine credibility.

1. Define the role or cohort boundary

The first decision is scope. The model must apply to a clearly defined group.

Examples:

• Frontline people leaders
• Senior account executives
• Graduate engineers
• Agile coaches
• Customer support specialists

If the boundary is vague, the model will be too.

2. Select competencies from the framework

A competency model does not include everything. Selection is the point.

Good practice:

• select a limited number of relevant competencies
• avoid overlapping or redundant constructs
• ensure coverage without overload

Most effective models include 6–10 competencies. More than that reduces usability and focus.

3. Set target proficiency levels

This is where competency models do real work.

For each selected competency, the model specifies:

• the required proficiency level for the role
• not the individual’s current capability
• not an aspirational future state

This distinction is essential. Models define role requirements, not performance ratings.

4. Tailor indicators to the role context

While definitions and proficiency logic come from the framework, models often include role-relevant indicators or examples.

These:

• clarify expectations
• reduce ambiguity
• improve assessment consistency

Indicators must still align with the underlying framework. They should not redefine the competency.

5. Apply weighting or emphasis (optional)

Some models weight competencies differently.

For example:

• technical depth may outweigh leadership in early-career roles
• stakeholder influence may dominate in senior roles

Weighting should be used sparingly. Over-engineering turns models into scoring systems rather than expectation guides.

What belongs in a competency model

A well-constructed competency model typically includes:

• a clear role or cohort definition
• selected competencies (sourced from the framework)
• target proficiency levels for each competency
• role-relevant indicators or examples
• optional weighting or emphasis guidance

That is sufficient.

When models expand beyond this, they usually start absorbing constructs that belong elsewhere.

A worked example: role-based competency model

To make this concrete, here is what a clean, defensible competency model looks like when applied to a role.

Example: Senior Account Executive (Sales)

Role boundary
Enterprise B2B sales role responsible for complex deal cycles and long-term account growth.

Selected competencies

• Commercial judgement
• Customer engagement
• Negotiation and influence
• Pipeline management
• Ethical decision-making

Target proficiency levels

• Commercial judgement – Advanced
• Customer engagement – Advanced
• Negotiation and influence – Advanced
• Pipeline management – Proficient
• Ethical decision-making – Proficient

Role-specific indicators (excerpt)

• Structures multi-stakeholder deals and anticipates commercial trade-offs
• Adapts negotiation strategy to power dynamics and risk exposure
• Maintains forecast accuracy across extended sales cycles

Notice what this model does not include:

• KPIs or quotas
• learning courses
• values statements
• personality traits

Its sole purpose is to define what competency the role requires, clearly and consistently.

What does not belong in a competency model

Competency models often fail because they absorb unrelated constructs.

A competency model should not include:

• values or culture statements
• personality traits
• KPIs or performance targets
• training activities
• tenure expectations
• subjective adjectives like “strong” or “excellent”

These may connect to the model, but they are not the model.

Competency model vs job description vs skills profile

Another frequent source of confusion is treating these tools as interchangeable.

They are not.

‍

A competency model sits between job descriptions and skills:

• broader than individual skills
• narrower than a full role description

When organisations collapse these into a single artefact, clarity is lost and assessment becomes subjective.

Competency models and assessment

Competency models are often misused in assessment because the role requirement and the person are conflated.

A clean assessment logic separates:

• role requirement (the competency model)
• individual competency (observed evidence)

The model defines what the role requires.
Assessment compares evidence against that requirement.

This separation:

• reduces bias
• improves consistency
• keeps performance conversations grounded

Reuse vs duplication: the hidden design decision

One of the most important design choices in competency modelling is whether models are reused or endlessly duplicated.

Healthy patterns:

• models reused across similar roles
• minor contextual notes instead of rewrites
• central governance of changes

Failure patterns:

• one model per role “just in case”
• identical competencies rewritten with new wording
• local tailoring without approval

If two roles require the same competency at the same level, they should use the same model or a shared base model. Duplication is not flexibility. It is entropy.

Common mistakes with competency models

Most competency models fail for predictable, structural reasons.

Mistake 1: Treating a model as a framework

If every role has bespoke definitions, consistency is already lost.

Mistake 2: Overloading the model

Models that include values, KPIs, behaviours, and learning plans stop being usable.

Mistake 3: Confusing role requirements with person assessment

Models define expectations, not performance ratings.

Mistake 4: Too many competencies

If a manager cannot remember the model, they will not use it.

Mistake 5: Uncontrolled local tailoring

Local “tweaks” without governance destroy comparability faster than any design flaw.

When you should not use a competency model

Competency models are not always the right tool.

Avoid formal models when:

• roles are highly experimental or short-lived
• teams are intentionally fluid
• work outcomes matter more than consistency

In these contexts, lightweight role charters or skills-based approaches are often more effective.

How many competency models should an organisation have?

Fewer than most think.

Good practice:

• reuse models across job families
• avoid one-model-per-job unless necessary
• design models around levels and competency bands

If your organisation has hundreds of unique competency models, governance has already failed.

Final takeaway

A competency model is not a framework, not a values list, and not a performance scorecard.

It is a precise, applied tool that translates shared competency definitions into clear role expectations.

When competency models are built on top of a well-governed competency framework, they enable fair assessment, meaningful development, and role clarity. When they are built in isolation, they create inconsistency dressed up as structure.

FAQ

What is a competency model?

A competency model defines which competencies and proficiency levels are required for success in a specific role, level, or job family.

How is a competency model different from a competency framework?

A framework defines the system and shared language; a model applies selected competencies to a specific context.

How many competencies should be in a competency model?

Typically 6–10. More than that reduces clarity and usability.

Can competency models change over time?

Yes. Models should evolve as roles change, while the underlying framework remains relatively stable.

‍