Skip to content
HOW TO IDENTIFY

How to identify skills gaps in your organisation

The first skills gap analysis cycle in an organisation is almost always done badly. The data is messy, the framework is half-ready, the priorities get set by gap size instead of business impact. This subtopic is the practical playbook: the three data sources that matter, how to run the first cycle in 3 weeks instead of 3 months, and the priority rule that separates a roadmap from a wishlist.

By Simon CarviPublished April 20268 min read

On this page

The three data sources you need

A defensible skills gap identification pipeline rests on three data sources. Skip any one and the gaps become anecdotal. Run all three and the output is a heat map the CFO can sign off on.

  • 1Role profiles with target levels Every role in scope has a list of required competencies with a target proficiency level per competency. This is the yardstick. Without it, the 'gap' is measured against the assessor's private expectation and stops being comparable across people or over time.
  • 2Structured assessment data Self plus manager at minimum, 360 (with peer and direct-report data) for senior roles. Self-only produces inflated current-level data and corrupts the whole analysis. The same scale across every rater and every competency.
  • 3Learning catalog inventory The list of courses, programs, and development resources your organisation already offers, mapped to competencies. This is what lets you overlay 'what we have' on 'what we need'. Most organisations discover their catalog overindexes on easy-to-procure courses and underindexes on the gaps that actually matter.

For the full methodology on designing the framework and the assessment, the skills gap analysis guide and the competency mapping guide are the upstream reads. This page assumes you have a framework and are running the first cycle.

360 assessment results

HR Manager

  • Talent & Career Management

    L2L4
    −2.0
    P1

  • Stakeholder Communication

    L2.5L3.5
    −1.0
    P2

  • Data-Driven Decision Making

    L2L3
    −1.0
    P2

  • Change Management

    L2.8L3
    ✓
    —

  • Workshop Facilitation

    L3.5L3
    +0.5
    P3

Auto-generated

Top 2 gaps seed the IDP. Lower-priority gaps go on the watch list.

Same view HR sees inside Huneety after a 360 or competency assessment closes. The priority column is the cue for which gaps become IDP targets this quarter.

Running the first cycle in 3 weeks

The first skills gap analysis cycle for a mid-sized organisation (200 to 1,000 employees) runs in 3 weeks if the framework is already in place. Most of the schedule is assessment submission and calibration, not analytics. Here is what weeks 1, 2, and 3 look like in practice.

  • 1Week 1: scope and launch Pick the population (by role, by department, or the whole org). Confirm role profiles and target levels for every role in scope. Configure the assessment campaign (raters, deadline, scale). Launch with a 1-page brief explaining purpose and anonymity.
  • 2Week 2: collect and remind Response rates drop off after 4 days without reminders. Two automated reminders at day 4 and day 8 get most groups above 70 percent. Chase the stragglers in the last 2 days. Close the campaign at end of week 2.
  • 3Week 3: compute, synthesise, debrief Day 11: reports generate. Days 12 to 14: manager debriefs happen. Day 15: HR consolidates the enterprise heat map. Day 15 to 21: L&D leadership meeting to agree on the top 3 investment priorities and the quarterly cadence.

The priority rule: not biggest, highest-impact

The most common first-cycle mistake: sort the heat map by gap depth, pick the top 3, buy training. This misses the point. The gap with the deepest score is often the gap nobody in the business cares about, or the gap that takes 3 years to close. A priority rule with three factors produces a defensible roadmap.

  • 1Gap depth How many levels below target, averaged across the population. A 1.5 gap matters more than a 0.5 gap, all else equal. This is the obvious factor and the reason most first cycles over-index on it.
  • 2Headcount affected A 1.0 gap affecting 120 people is strategically more important than a 2.0 gap affecting 4 people, even though the 2.0 gap 'looks bigger'. Population-weighted thinking.
  • 3Business impact Weight the competency by how central it is to the strategy. 'Customer obsession' matters more in a consumer business than in a B2B enterprise engineering org. The weights come from the executive team, not the HR team.
  • 4Formulaic priority score priority = gap_depth x headcount_affected x business_impact_weight. Items in the top quartile become the L&D roadmap. Items in the bottom quartile go on the watch list for re-assessment next cycle.

From role profile to priority list in 3 weeks

Automated assessment, three-level gap aggregation, configurable priority scoring. The heat map produces a roadmap the CFO can sign off on.

See how it works

Three failure modes in first-cycle identification

The same three patterns turn a first cycle into a shelfware heat map. Screen for them explicitly before launch.

  • 1Self-only assessment Without manager or peer data, the 'gap' reflects self-perception inflated by roughly 0.5 levels on average. The heat map overstates capability and underestimates the real gap. Minimum viable data is self plus manager.
  • 2No executive weighting on business impact If HR picks the priority competencies unilaterally, the roadmap gets rejected at the C-suite conversation. Get explicit business-impact weights from the executive team in week 1, not week 3.
  • 3One-off cycle with no re-assessment commitment Running this once produces a snapshot. Running it annually produces a trend line, which is what makes L&D investment measurable. Commit to the second cycle in the same conversation where you scope the first.

Identification on Huneety

On Huneety, the identification pipeline runs end to end on one platform. Role profiles live in the competency module. Assessments run on the same framework. Gaps compute automatically at individual, team, department, and enterprise level. The priority score is configurable (weight each factor to your organisation). L&D catalog overlay is a CSV upload. See Huneety skills analytics.

QUICK ANSWERS

Quick answers

How do we scope the first cycle?
Start with one role family or one department rather than the whole organisation. First cycles always uncover framework gaps and assessment-process issues; learning those at 50-person scale is much cheaper than at 500-person scale. Expand to the whole org in cycle 2.
What if our role profiles are incomplete?
Use Huna AI to draft them from job descriptions, then have HR and the hiring manager for each role edit in their vocabulary. 3 to 6 weeks of drafting time becomes 3 to 6 days. The drafting is what AI accelerates; the editing is where HR adds value.
Can we run the identification without a 360?
Yes, with self plus manager. Most first cycles run on self plus manager because 360 logistics for a large population are heavy. Move to 360 for senior roles and leadership in cycle 2 or 3, where the peer and direct-report perspectives add signal.

Continue learning

Skills gap heat maps explained

How to read a heat map, what the three views actually mean, and how to drill from the enterprise picture to named individuals.

Read the guide

Training ROI measurement

Connecting L&D spend to measured competency improvement over time. The framework that makes the CFO conversation defensible.

Coming soon

Run a first skills gap cycle on Huneety

Role profiles, assessment, gap aggregation, priority scoring, L&D catalog overlay. All in one pipeline, all in 3 weeks.

See Huneety skills analyticsRead the guide