Skip to content

Skills gap analysis

Know the Distance Between the Skills You Have and the Skills You Need

A skills gap is a subtraction, and the arithmetic is the easy part. The work is in defining the standard a role requires, measuring what people can demonstrate against it, and then deciding which of the resulting gaps is worth money.

Book a Demo How skills are modelled

Gap analysis — Data Engineering, 48 people

Skills in role
14
Critical gaps
3
Role ready
58%
  • Pipeline orchestration Gap: 2 levels
  • Data modelling Gap: 1 level
  • SQL performance Meets requirement

Illustrative dashboard. Not customer data.

What this actually means

Required level minus measured level, done properly

The method has four inputs, and the analysis is only as good as the weakest of them. Most gap exercises fail on the first input: nobody wrote down what the role actually requires, so the comparison had nothing to compare against.

  • Input 01

    The role standard

    Which skills the role needs and at what level. Defined once per role, reviewed as the work changes, and written in observable terms so two managers would place the same bar.

  • Input 02

    The measured level

    Where each person currently stands on those skills, established from assessment evidence rather than a self-rating on a form.

  • Input 03

    The gap size

    The difference between the two, per skill, per person. A one-level gap and a three-level gap are different problems and should never be reported as the same red cell.

  • Input 04

    The population

    How many people share the gap. One person two levels short is a coaching conversation. Forty people one level short is a capability programme.

  • Input 05

    Criticality

    How much the work depends on the skill. A gap in a skill nobody uses this year is not urgent, however large it looks on a heat map.

  • Input 06

    The horizon

    Whether the requirement is current or arrives with next year's plan. A gap against a future standard is a hiring and development decision, not a performance issue.

The method

How a gap becomes a priority

Every gap on a heat map looks equally alarming, which is why heat maps rarely change budgets. Ranking needs the three factors below applied in order, and the result is a short list instead of a wall of red.

Step one

Compute the gap per person

For each skill in the role standard, subtract the measured level from the required level. Negative results are not gaps; they are capability the role does not currently use, and they belong in the mobility conversation.

Step two

Roll it up by skill

Aggregate across the population so you see how many people are short and by how much. This is where an individual development issue separates cleanly from an organizational capability issue.

Step three

Weight by criticality and horizon

A large gap in a peripheral skill ranks below a small gap in a skill the next twelve months depend on. Criticality is set by the business, not derived from the data.

Worked through, for one skill

  • Standard. Pipeline orchestration, Level 4, marked critical for the coming year.
  • Measured. Across the team, most people sit at Level 2, a few at Level 3.
  • Gap. Predominantly two levels, held by most of the population, in a skill the plan depends on.
  • Conclusion. This is a programme with a hiring component, not a course. A one-level gap in a peripheral skill elsewhere can wait.

Illustrative example. Not customer data.

The analysis ends with a ranked list. What you do with each item splits two ways: deepen the skill where the person stays, or move the person somewhere their profile fits better. Upskilling and reskilling are the two answers.

What it is for

The decisions a ranked gap list actually supports

  • Spend the training budget on the gap that matters.

    A ranked list makes the case for funding one programme and deferring another, in language a finance conversation can use.

    Prioritised investment

  • Know whether to build or to hire.

    A two-level gap held by most of a team is rarely closed by training alone. The size and spread of a gap is what tells you which lever to pull.

    Build-versus-buy input

  • See the gap before the project does.

    Running the analysis against next year's required standard rather than today's turns a staffing surprise into a plan with months in hand.

    Forward-looking standards

  • Give every manager the same picture of their team.

    The same method applied consistently, so a department head and a business unit leader are looking at comparable numbers rather than two spreadsheets.

    Consistent rollup

Questions

Questions about the method

Where does the required level for a role come from?

From you. The platform provides starting role standards and drafts skill definitions to react to, but the bar for a role in your organization is a business judgement. Most teams start by having two or three managers place the levels independently and reconciling where they disagree, which surfaces a lot on its own.

How is this different from a training needs survey?

A survey asks people what training they would like. A gap analysis compares a defined standard against measured capability and produces a ranked list of differences. The survey tells you about appetite, which is useful; only the analysis tells you about distance.

How often should the analysis be re-run?

The gap moves when either side of the subtraction moves, so it recalculates continuously as people are re-assessed and standards are edited. The useful cadence for reviewing it is usually planning-linked: once a quarter for progress, and whenever a role standard or a business plan changes materially.

What if we have not defined our roles yet?

That is the normal starting point, and it is why most engagements begin with one job family rather than the whole organization. Defining a handful of roles properly produces a usable analysis in weeks. Attempting all of them at once produces a taxonomy project that never ships.

Run the analysis on one job family

Bring one role with a headcount behind it. We will show you what defining the standard involves, how the levels get measured, and what the ranked gap list looks like at the end.

Book a Demo Enterprise overview

Keep reading