Skip to content

Skills & Workforce

A practical guide to skills gap analysis

H
Huneety Team
·April 17, 2026·5 min read
Heat map grid showing gap severity across departments and competencies

Define the competency framework first

The framework decides what you measure, so it has to be right before assessments start. Each role needs competencies up to its cap (8 for ICs, 10 for managers, 12 for directors) with at least one third behavioral. The competencies should map to observable behaviors on a defined proficiency scale (Huneety uses Dreyfus 0 to 5).

If you already have a competency mapping process, audit it for two things. First, check that every competency has clear behavioral indicators at each level. Second, confirm that proficiency targets are set per role, not per department. A senior engineer and a junior engineer share the same competency list but different target scores.

Organizations without an existing framework can start from a pre-built skills taxonomy covering 1,700+ skills across 20 root categories. The taxonomy provides the structure; your team customizes it to match your vocabulary and your roles.

Framework benchmarks
1,700+
pre-built skills across the full taxonomy
20
root competency categories covering behavioral and technical domains
8 (IC), 10 (manager), 12 (director)
Role-level caps
Minimum one third behavioral competencies per role

Choose the right assessment method

The method you pick affects both accuracy and buy-in. 360-degree assessments give the richest signal because they combine self-assessment with feedback from managers, peers, and direct reports. A minimum of seven assessors per person produces reliable scores.

For teams running their first gap analysis, a simpler approach works too: manager-only ratings against the framework, or self-assessment followed by manager calibration. The trade-off is accuracy. Self-assessment alone carries bias. Manager-only ratings miss the peer perspective.

Whatever method you choose, run the assessment across all roles in the scope at the same time. Staggered assessments create comparison problems: a department assessed in January and another in June cannot be compared cleanly because conditions change.

Set clear expectations before assessments launch. Assessors need to understand the proficiency scale (what does a 3 look like versus a 4?), the purpose (development, not performance review), and the timeline. Poor communication here produces inflated scores or low response rates, both of which corrupt the gap data.

Read results with heatmaps

Raw scores are hard to act on. Two views make them useful.

The health heatmap is a department-by-competency matrix that color-codes gap severity. Each cell shows the average gap for one competency root across one department. The scale runs from healthy (gap of 0.5 or less, green) through minor, moderate, and significant, up to critical (gap above 3.0, red). Learn how heatmaps work in practice

Gap severity scale

Healthy zones

  • Gap 0.5 or less: On target (green)
  • Gap 0.5 to 1.0: Minor, monitor only (amber)
  • Gap 3.0+: Critical, immediate action (dark red)

Problem zones

  • Gap 1.0 to 2.0: Moderate (orange)
  • Gap 2.0 to 3.0: Significant (red)

The gap analysis chart sorts competencies by gap size in horizontal bars. Color-coding flags critical gaps (1.5 or above) in red, severe gaps (1.0 to 1.5) in orange, moderate gaps (0.5 to 1.0) in amber, and on-target gaps (below 0.5) in green. This chart answers the question “where are our biggest gaps?” in one glance.

Together, the heatmap shows where gaps concentrate by department, and the gap chart shows which competencies carry the largest gaps across the organization. One is geographic; the other is thematic.

Start at the top, then drill down. The first view should be readiness by department, country, or job level. This shows where organizational capability is strong and where it is thin before anyone looks at an individual score. Only after the organizational picture is clear should HR drill into team-level and then individual-level gaps.

At the individual level, two views matter. The gap-vs-role view shows each person’s current score against their role’s target for every competency. The gap-vs-career-path view shows the same scores against the requirements of their next target role. These are two different gap pictures for the same person. The first tells you what to fix now. The second tells you what to develop for promotion readiness.

Complete guide

Go deeper on skills gap analysis

Read the complete pillar guide for frameworks, methods, and worked examples.

Read the guide

Prioritize gaps with the burden score

Not every gap deserves the same investment. A critical gap affecting three people costs less than a moderate gap affecting 300. The burden score captures this.

Process
  1. Count affected employees

    how many people have a gap on this competency

  2. Calculate average gap depth

    the mean distance between target and actual score

  3. Multiply

    affected employees times average gap depth equals the burden score

  4. Rank

    sort all competencies by burden score, highest first

The burden score prioritizes gaps by business impact, not just by average gap size. A competency with a 2.0 average gap across five people (burden: 10) ranks below a competency with a 1.2 average gap across 50 people (burden: 60). The second one drags on more of the organization.

This reranking changes decisions. Without burden scoring, HR teams chase the deepest gaps. With it, they chase the gaps that affect the most people at meaningful depth. The result is higher total proficiency lift per dollar spent.

Identify where gaps cluster

Before building development plans, look for patterns. Gaps rarely distribute evenly. Common clusters include:

  • A single department with gaps across multiple competencies (a team-level problem, often caused by rapid hiring or a leadership change)
  • A single competency with gaps across multiple departments (a systemic problem, often a missing training program or an outdated framework target)
  • A role-level pattern where all people in the same role share the same gap (a job-design problem, where the role’s competency target may be miscalibrated)

Identifying gap patterns helps you pick the right intervention. A team-level cluster calls for a targeted workshop or coaching engagement. A systemic competency gap calls for a new L&D program. A role-level pattern calls for a framework review before any training.

Use your experts as part of the solution. The same assessment data that reveals gaps also reveals who scores 4.0 or above on each competency. These are your internal experts. For core competencies and unique organizational competencies where external training does not exist, internal experts are the most credible development resource. Pair them with employees who have gaps on the same competency for mentoring, peer coaching, or stretch assignment sponsorship. The expert directory in the analytics view surfaces these matches automatically.

Turn gaps into development plans

Once gaps are prioritized and clustered, the action plan writes itself. Each gap maps to a development action distributed across the 70/20/10 model: 70% on the job, 20% through others, 10% formal learning.

For the highest-burden gaps, build individual development plans (IDPs) for every affected employee. Each IDP ties a specific competency gap to a specific development action with a deadline and a review cycle. The 70/20/10 split matters here: formal learning (courses, certifications) is the most expensive channel and produces the least autonomy. On-the-job stretch assignments produce the most lasting skill growth.

For budget decisions, connect gap closure to training ROI measurement. Run a follow-up assessment cycle after development actions complete. Compare before-and-after scores. The burden score reduction across the organization is your measurable return.

The catalog gap map shows which of your existing L&D programs cover which skill gaps. Three states matter: “covered” (a program addresses the gap), “uncovered” (no program exists for this gap), and “orphan” (a program covers a skill where no gap exists). Uncovered gaps need new investment. Orphan programs are candidates for retirement or reallocation.

Track IDP completion rates by channel. If 90% of completed activities are formal courses but scores barely move, the channel mix is wrong. Rebalance toward on-the-job assignments. The training ROI measurement article covers how to quantify this channel effect using before-and-after assessment data.

Built for HR teams

Skills analytics

See how the skills analytics dashboard turns assessment data into gap priorities, burden scores, and development plans.

Explore the platform

Frequently asked questions

Most organizations run a full gap analysis annually, aligned with budget planning. Quarterly pulse checks on the highest-burden competencies keep the data fresh between full cycles. The cadence depends on how fast your workforce changes.
For organization-wide insights, assess at least 80% of the population in scope. For department-level analysis, every person in the department should be assessed. Partial data creates blind spots that distort the heatmap.
Yes. Manager-only ratings or self-plus-manager calibration both produce usable gap data. 360-degree assessments add the peer and direct-report perspective, which improves accuracy, but they are not a prerequisite.
The catalog gap map flags "uncovered" gaps where no current L&D program addresses the skill. For these, the 70/20/10 model helps: assign on-the-job stretch projects and peer mentoring while you build or source formal content.
[Competency mapping](/competency-mapping) defines what good looks like for each role. A skills gap analysis measures how far your current people are from that standard. Mapping comes first; gap analysis comes second. You cannot measure a gap without a target.

Ready to run your first skills gap analysis with real data? Talk to the Huneety team about setting up your framework and assessment cycle.

Skills & Workforce

Ready to close the gaps?

Book a demo. We'll show you how it works with your competency framework.