Skip to content
COMPETENCY MAPPING

Competency mapping: the complete guide

Competency mapping turns fuzzy job descriptions into measurable behaviours you can assess, develop, and compare across roles. This guide walks it end-to-end: the four building blocks, the process in five steps, the framework methodologies that hold up, worked examples by function, and the six mistakes that turn a framework into shelfware within 18 months.

By Simon CarviPublished April 202614 min read

On this page

THE BASICS

What is competency mapping?

Competency mapping is the practice of defining, in observable terms, the behaviours and skills a role requires, and then rating each person in that role against those same behaviours on a consistent scale. The output is a framework: a structured map of competencies tied to roles, with proficiency levels that let you compare a person to a target and close the gap.

It is not a job description. Job descriptions list responsibilities. Competency maps describe the capabilities required to execute those responsibilities, broken down into behaviours specific enough that two reasonable managers, rating the same person, land on similar scores. Four components are load-bearing:

  • 1Competencies Named capabilities (Stakeholder Communication, Data-Driven Decision Making, Delegation). Not too many. A usable framework has 10 to 20 for a given role family, not 80.
  • 2Behaviours Observable descriptions of what the competency looks like in practice, written per level. 'Presents data to executive audiences with a clear recommendation' is a behaviour. 'Good communicator' is not.
  • 3A proficiency scale The same scale applied across every competency. We use Dreyfus 0 to 5. The scale is the rosetta stone that lets gaps be compared across people and roles.
  • 4Role profiles For each role, which competencies are required and at what target level. Without role profiles, a framework is just a list of words. With them, it becomes a tool.

Anatomy of a competency

Stakeholder Communication

The ability to translate complex information for different audiences and secure alignment on next steps.

Observable behaviours

How the competency shows up in the work

  • Presents a 3-year plan to the C-suite with quantified tradeoffs
  • Reframes technical blockers into business-language risks
  • Runs cross-team working sessions to consensus within 60 minutes
  • Adapts message density to audience (memo vs 3-slide overview)
Hard skills

Concrete techniques you can train and certify

  • Written structured memo (1-pager, pyramid principle)
  • Financial modelling (P&L impact, NPV scenarios)
  • Slide storytelling (SCQA structure)
  • Data visualization (pick the right chart)

A competency framework can stop at the competency level, OR go deeper by listing observable behaviours (green) AND the specific hard skills (red) that produce them. The deeper granularity is what makes assessments defensible.

WHY BOTHER

Why competency mapping is worth the effort

A mapped organisation can do four things a non-mapped organisation struggles with. Hiring gets a consistent bar. Development plans become specific instead of wishful. Succession planning works on data instead of manager reputation. And internal mobility stops being a conversation between two people who agree on the candidate and starts being a comparison of the candidate's profile against the target role's profile.

The return is slow but structural. In year one, the framework is the output. In year two, the review cycle runs on competency data. In year three, the individual development plan cycle stops inventing goals from scratch because gaps are produced automatically from the assessment. The common mistake is expecting year-three value in year one: the framework has to run through two review cycles before the vocabulary stabilises.

  • 1Hiring bar calibration Candidates are rated against the role's competency profile, not the interviewer's memory of last week's candidate. Cross-interviewer variance drops.
  • 2Defensible development plans The gap analysis is data, not opinion. The IDP targets the gap, not the performance review grievance.
  • 3Succession without surprises Role-readiness is a score, not a guess. Internal candidates surface that managers would not have named unprompted.
  • 4Internal mobility A sales manager moving to customer success stops being a leap of faith and becomes a visible delta with a pre-built learning plan.

THE PROCESS

How to build a competency framework in 5 steps

A framework that sticks is built top-down in structure and bottom-up in vocabulary. Top-down: start from the organisational strategy and name the capabilities the strategy requires. Bottom-up: gather the language managers actually use, so the framework does not feel imposed. Five steps, in order.

WHAT IT LOOKS LIKE

What a competency profile actually looks like

A competency profile is usually rendered as a spider chart (radar plot): one axis per competency, one ring per proficiency level, current and target values plotted as two overlaid polygons. The visual makes the gaps between 'where the person is' and 'where the role targets them' instantly legible, which is the single most useful thing a framework can produce for a development conversation.

For organisations moving from spreadsheets to a platform, this is usually the visual that wins. A list of numbers does not spark a coaching conversation. A profile with visible gaps does.

Example: HR Manager competency profile. Purple = role target. Green = current assessment. The gap between the two is where the IDP focuses.

METHODOLOGIES

Framework methodologies that hold up

You do not need to invent a framework from scratch. Three published methodologies plus a hybrid cover almost every enterprise use case. Pick the one that matches your audience, then adapt the vocabulary to your organisation's language.

SFIA 9: the skills framework for the digital age

Maintained by the SFIA Foundation, updated to version 9 in 2024. Covers 127 digital and business skills across 7 categories, each with 7 responsibility levels (Follow to Set Strategy). Well suited to technology organisations, IT shared-services, and regulated industries where skill certification matters.

Strengths: globally recognised, extensive published behavioural anchors, mapped to multiple certifications. Caveat: heavy for non-technical functions (sales, creative, operations) where the vocabulary feels imported.

EXAMPLES

Competency targets by role

A framework is easier to evaluate when you see the outcome. Here are four roles with their competency gaps and the resulting development plan. Same framework, same Dreyfus scale, same 70/20/10 structure. Different role profiles. Different priorities.

Individual Development Plan

Priya Mehta · Marketing Manager

In Progress
On the job(70%)

Lead the Q3 brand reposition launch as primary stakeholder owner

Sep 30

Present quarterly marketing results to the C-suite (own the deck)

Oct 15
Through others(20%)

Bi-weekly 1:1 coaching with the VP Marketing

ongoing→ Helen R.
Training(10%)

Communicating with Executives (1-day workshop)

Aug 20

WHAT TO AVOID

Six mistakes that kill competency frameworks

More frameworks fail from these six causes than from any theoretical flaw. The pattern is so consistent that we screen for them in the first kickoff with every new customer.

  1. Too many competencies

    80 competencies is a filing cabinet, not a framework. 10 to 20 per role family is workable. More than that and managers stop using the framework because calibrating 80 scores is impossible in one sitting.

  2. Behavioural anchors that are not observable

    'Strategic' is not a behaviour. 'Presents a 3-year plan to the executive team with tradeoffs' is. If two managers cannot watch the same meeting and land on similar scores, the anchor is too abstract.

  3. No proficiency scale (or multiple scales)

    'Rate each competency on a scale of 1 to 5' is ambiguous. What is a 3? Dreyfus with named levels (novice to master) removes the interpretation problem. One scale across all competencies is non-negotiable.

  4. No role profile

    Without a target level per competency per role, the assessment is floating: there is nothing to measure 'gap' against. Role profiles are the piece most organisations underinvest in, and it is why their first assessment cycle produces data nobody can use.

  5. Building in the HR team alone

    A framework built by HR, handed to managers, fails on contact with reality. Co-build with 5 to 8 senior managers from the affected functions. Their vocabulary goes into the anchors, and they become the internal champions.

  6. Freezing the framework after rollout

    Expect to revise 10 to 20 percent of the behavioural anchors after the first two review cycles. The framework is a living artefact. Customers who publish 'the framework' as a laminated wall chart and never touch it again are the ones whose managers silently stop using it.

HUNEETY PLATFORM

How Huneety handles competency mapping

Competency mapping is heavy work done well, or mess done badly. Huneety removes the mess: AI-drafted frameworks from your job descriptions, visual role profiles, gap analysis computed per person against role targets, and a framework that stays current as roles evolve instead of ageing into shelfware.

360 Assessment Results

Marketing Manager

  • Strategic Thinking

    L2L4
    −2.0
    P1

  • Communication

    L3L4
    −1.0
    P2

  • Data Analysis

    L4L4
    ✓
    —

  • Decision Making

    L2L3
    −1.0
    P3

Auto-generated

Top 3 gaps identified · IDP auto-generated

  • Huna AI generates a first-draft framework

    Feed in your job descriptions and pick a reference methodology (SFIA 9, Korn Ferry, or blank). Huna produces a competency list with behavioural anchors at 5 proficiency levels, ready for HR to edit.

  • Visual role profiles

    Spider charts per role, side-by-side comparisons across roles, and gap heat maps at the department level. The visual is the tool, not an afterthought.

  • Gap-driven IDPs in one click

    Competency gap becomes a draft 70/20/10 action plan the manager edits. The framework is not a document; it is the input to the development cycle.

  • Framework stays current

    When roles change, the AI suggests framework updates rather than letting the document age. New job descriptions produce deltas the HR team reviews, not a framework that is 18 months out of date.

See Huneety competency mapping

WHO USES IT

Teams that rely on competency mapping

Competency mapping is infrastructure, not a deliverable. Two audiences use it hardest: in-house HR teams running annual development cycles, and external consultants who need a structured assessment to anchor their engagements.

In-house HR teams

HR teams use competency mapping to calibrate hiring, structure development cycles, and surface succession candidates. The framework becomes the shared language across recruiters, managers, and the learning team. The ROI is slow (two cycles) but compounding.

For HR teams

HR and leadership consultants

Consultants use a shared framework across client engagements to move faster and produce comparable insights. With a white-label platform, the framework becomes a branded deliverable: the consultant's methodology, packaged in the client's workspace.

For consultants

GO DEEPER

Competency mapping subtopics

Three deeper reads for specific angles of the framework-building job. Start with the framework examples if you are sourcing behavioural anchors for the first time.

Competency framework examples

Six real frameworks by function (engineering, sales, leadership, customer success, marketing, operations) with behavioural anchors.

The Dreyfus proficiency scale

Why we default to Dreyfus 0 to 5 as the scale across every competency, and how each level maps to development verbs.

Soft skills vs hard skills in a framework

How to structure frameworks that cover both technical and behavioural capabilities without one drowning the other.

FREQUENTLY ASKED

Common questions about competency mapping

Answers to the questions that come up most in the first HR-team kickoff.

10 to 20 per role family is the workable range. Fewer than 10 and you cannot describe the role. More than 20 and the assessment becomes impossible to calibrate in one sitting. Some organisations use 40 plus, but they almost always report that managers only actively use the top 15.
Yes. The scale without anchors is unusable. A '3 out of 5' means different things to different managers. One sentence of observable behaviour per level is the minimum. It is tedious to write but non-negotiable for defensible assessments.
Manually: 3 to 6 months for a mid-sized organisation (200 to 1,000 employees), including interviews, drafting, manager review, and pilot. With AI assistance: 2 to 3 weeks to draft, plus 4 to 6 weeks of HR editing and calibration. The editing cannot be skipped. The drafting is what AI genuinely accelerates.
Build your own, informed by a published methodology. Adopting a published framework wholesale produces language your managers do not use, and adoption suffers. The published methodologies are best used as scaffolding: structure and proficiency scale from them, vocabulary from your own organisation.
Minor revisions after every review cycle (10 to 20 percent of anchors adjusted). Major revisions every 2 to 3 years, or when the business strategy changes materially. The framework is a living document; treating it as finished is the single most common cause of adoption decay.
Competency ratings and performance ratings are different and should stay different. Performance is 'did you deliver the results'. Competency is 'what capabilities do you demonstrate'. A high-performing level-2 Strategic Thinker is not a contradiction. Collapsing them into one rating is how frameworks get corrupted.
Skills mapping catalogues discrete technical skills (Python, SQL, negotiation). Competency mapping describes integrated behaviours that combine multiple skills with judgment (Data-Driven Decision Making, Stakeholder Communication). Skills are easier to train. Competencies are easier to develop. Most organisations need both.

Related terms

The Competency Mapping glossary lands with our upcoming term library. Until then, the full vocabulary lives inside the platform itself.

Map your first competency framework on Huneety

Upload a job description, pick a reference methodology, and Huna AI drafts the framework. HR edits, pilot on one department, run your first assessment cycle in 3 weeks.

See Huneety competency mappingTalk to sales