How to do a skills gap analysis

Content aligned to the Capability Guide PDF for this topic. Q2 2026 refresh.

Where does a skills gap analysis begin?

Begin with a question your leadership team can answer in one sentence: what capability must this team hold twelve months from now to deliver the plan? A skills gap analysis is not a morale exercise or a training wish-list. It is the deliberate comparison of where capability sits today against where the business will need it, quantified skill by skill, prioritised by impact, and converted into owners, dates, and budgets.

World Economic Forum research finds that 63% of employers cite skills gaps as the top barrier to transformation, while 39% of workers' core skills are expected to change by 2030 (World Economic Forum, 2025). CIPD's Labour Market Outlook shows many UK employers still face hard-to-fill roles linked to capability, not headcount alone (Chartered Institute of Personnel and Development, 2024). Those figures explain why gap analyses fail when they only list today's pain points: the skills that will hurt you next year rarely look urgent this quarter.

What is a skills gap analysis, really?

A skills gap analysis is a structured comparison between the capability your workforce currently has and the capability it needs to meet organisational goals. The gap is the measurable distance between those two pictures — found deliberately, not discovered when a project stalls.

Every analysis rests on three states. Current state is what people can demonstrably do now, recorded in a skills matrix on one consistent scale. Desired state is what the work requires today and what it will require as strategy, technology, and regulation shift. The gap is the difference between them, expressed as a number you can rank, fund, and revisit.

The matrix and the analysis are linked but not identical. The matrix is your evidence base: who holds which skill at which level. The analysis is what you do with that evidence — set scores against required levels, quantify shortfalls, and turn them into a plan. Data without analysis is inventory; analysis without data is opinion.

Why look forward, not only at today's weaknesses?

Teams that only catalogue present problems miss the gaps that decide next year's delivery. The desired state must include skills the business will need as it grows, adopts new systems, enters markets, or faces new regulation. Map those requirements before the gap becomes urgent and you retain lead time to train, cross-train, or hire calmly.

Skills gaps rarely announce themselves. They surface as missed deadlines, rework, audit findings, or quiet over-reliance on one expert. A forward-looking analysis drags those risks into the open while closing them is still affordable. That is the difference between discovering a gap when it stops you and seeing it months ahead on your terms.

Gartner reports that only 8% of organisations have reliable workforce skills data (Gartner, 2024). Without a defined scale and honest scoring, gap figures inherit that unreliability. Invest in the matrix first; the analysis becomes fast once current state is trustworthy.

What are the seven steps, in order?

1. Define required capability, including the future. List skills the work needs and the level required for each — for example Level 3 in data analysis, not "data analysis" alone. Draw on today's roles and where the business is heading: new platforms, markets, compliance, growth. For a researched menu of forward-facing candidates, see The 2026 Skills Index, the top 100 hard and soft skills for 2026.
2. Prioritise skills before you measure. Mark which are business-critical, revenue-impacting, regulated, or strategic. When gaps appear, you already know which deserve attention first.
3. Measure current capability honestly. Score every person on the same scale with evidence. Combine self-assessment, manager validation, and hard proof where it exists. The matrix is the natural home for this step.
4. Quantify the gap per skill. Set current against required and express the difference as level gaps, percentage points, or coverage counts. "We feel thin on compliance" becomes "46% current versus 75% required — 29 points."
5. Rank gaps by impact. Combine gap size with the priority you assigned earlier. A modest gap on a regulated skill can outrank a larger gap on something peripheral.
6. Choose how to close each gap. Train, cross-train, redesign work, or recruit — match the intervention to size and urgency rather than defaulting to one tool.
7. Re-run on a cycle. Re-measure when the desired state shifts and on a fixed cadence so you see gaps closing and spot new ones forming while they are still small.

Document decisions from each cycle beside the matrix: named owners, training dates, hire briefs, cross-training pairs. That log proves the analysis changed behaviour, not only produced a slide.

Once your red zones are visible, the Pareto principle is the quickest way to decide which to fund first.

How does the 0–5 scale turn gaps into numbers?

Measuring a gap needs current and required capability on the same clear scale. The Upleashed 0–5 framework assigns proficiency weightings: Level 1 = 25%, Level 2 = 50%, Level 3 = 75%, Levels 4 and 5 = 100%, with Level 0 excluded from averages. Average a skill column to get team current capability as a percentage; compare to the required level (also a percentage); the gap is the difference in points.

Worked example — Data analysis (strategic priority, required Level 3 = 75%). Six-person team scores: 2, 1, 2, 1, 2, 1 → weightings 50, 25, 50, 25, 50, 25 → average 225 ÷ 6 = 38% current. Gap = 75% − 38% = 37 percentage points — large, on a strategic skill, therefore top priority for the plan.

What does a quantified gap table look like on a real team?

Below is a skill-level summary for a six-person customer operations team after scoring. Required future level is Level 3 (75%) for each skill unless noted.

Read the table in three passes. Size: Data analysis and Compliance show the largest shortfalls. Impact: both are flagged critical — regulated or strategic — so they lead the plan ahead of the smaller CRM gap. Surplus: Complaint handling already exceeds requirement; capable people there can coach others or absorb work while gaps close elsewhere.

Re-run the same table next quarter against unchanged required levels. Narrowing gaps are proof your interventions worked; widening gaps signal a shifting desired state or stale scores.

How do you close gaps once they are ranked?

Each prioritised gap has more than one fix. The right choice depends on size, timescale, and whether the skill must exist inside the team or can be bought in.

• Train or upskill when existing people part-hold the skill and time allows — start before the capability is needed, not when work lands.
• Cross-train or reskill when coverage is thin but at least one expert exists — protect the expert's time to teach.
• Redesign work when capability sits elsewhere and growing it is too slow — useful as a bridge, not a permanent substitute for strategic gaps.
• Recruit when the gap is too large, too specialised, or too urgent to grow internally — reserve for gaps training cannot close in time.

A practical rule: close foreseeable, lasting gaps by developing people you already have; reserve recruitment for gaps that are genuinely too big or too urgent. The quantified gap tells you how far you must move; re-measurement tells you whether you arrived.

What mistakes undermine a gap analysis?

Only looking at today. Future-facing skills are where transformation risk lives; omit them and the analysis comforts rather than prepares.

No proficiency levels in the desired state. "We need data analysis" cannot be measured. Specify the level required or the gap stays a vague impression.

Leaving gaps qualitative. Rankings need numbers. Put a figure on every gap.

Ranking by size alone. The widest gap is not always the top priority. Weight regulated and strategic skills first.

Inflating current scores. Generous ratings shrink gaps on paper and leave them open in reality.

Running the analysis once. A single snapshot dates quickly. Cadence is where the value compounds.

What if you inherit a matrix that is only half built?

Edge case: you join a team mid-year with partial scores, outdated job descriptions, and no required-level row. Do not run a full gap analysis on bad data — you will prioritise fiction. Spend the first cycle fixing foundations: agree ten to fifteen vital skills, publish descriptors, set required levels from actual work packages, and re-score with dual assessment. Run a directional gap read on the three skills leadership already names as critical, but label it provisional until the matrix completes.

If two departments merged, resist blending grids until roles stabilise. Hold separate matrices for one quarter, then harmonise skills and required levels in a joint calibration. Merged teams that rush a single grid often encode old role assumptions and hide duplicate coverage.

How do you connect gap analysis to training and hiring?

Translate the top three gaps into business cases, not course catalogues. For each gap, state the risk if unclosed (audit failure, project slip, key-person exposure), the intervention, the owner, and the re-measure date. Training requests without a gap number struggle for budget; gap-led requests cite coverage and compliance impact.

Pair this guide with identifying team gaps, prioritising development, and building the matrix that supplies your current-state data. Each page owns one decision in the same workflow.

Which site tools support a skills gap analysis?

• Capability gap ROI calculator
• Skills gap analysis examples
• How to run a skills audit
• Free 5×5 mini-matrix builder
• Upleashed 0–5 methodology
• 0–5 descriptor generator

How does this guide connect to the rest of the site?

Download skills-gap-analysis.pdf for workshops and calibration. This page adds worked examples and implementation notes the printable guide does not include.

The methodology pillar documents the Upleashed 0–5 framework used across 106.5M+ assessments. Pair it with the descriptor generator so raters share one definition per level.

For a pre-wired grid (required levels, coverage row, capability averages), open the Excel Skills Matrix Template (£199). Scale beyond Excel when you need continuous evidence — PulseAI automates the same 0–5 method.

Treat capability ratings as living data: date changes, separate them from performance conversations, and review after role or tooling shifts.

Frequently asked questions

What is a skills gap analysis?

It is a structured comparison between the capability your workforce currently has and the capability it needs to meet organisational goals, now and in the future. The gap is the measured distance between those two states, quantified per skill so it can be ranked and acted on.

How is a gap analysis different from spotting weaknesses?

Spotting weaknesses is reactive and often limited to today. A proper gap analysis defines a forward-looking desired state, measures current capability on the same scale, quantifies the difference, and prioritises by impact so you find gaps early rather than when work stalls.

What are the main steps in a skills gap analysis?

Define required capability including future needs, prioritise skills by impact, measure current capability honestly in a matrix, quantify the gap per skill, rank gaps by impact not size alone, choose how to close each one, and re-run the analysis on a regular cycle.

How do you quantify a skills gap?

Express current and required capability on the same scale — for example the Upleashed 0–5 framework with proficiency weightings — then take the difference. Average scores in a skill column to a current percentage, set the required level as a percentage, and the gap is the difference in points.

How often should you run a gap analysis?

Re-run at least annually and whenever strategy, systems, regulation, or team mix shifts. Teams with a living matrix can read gaps continuously; others should align gap reviews with quarterly matrix refresh.

Do you need special software for a gap analysis?

No. A well-built spreadsheet with required levels and gap formulas is enough for most teams. Software helps when many teams need shared, dated updates and automated reminders, but the method works without it.