A skills gap analysis is a structured comparison between the skills your team currently has and the skills it needs, done before you write a job requisition, not after. It works by combining three inputs: an honest inventory of what current employees can actually do, a benchmark of what each role will require going forward, and outside market or industry data on where skills are shifting. Run in that order, it tells you whether a gap should be closed by training an existing employee, hiring externally, restructuring a role, or bringing in contract help, which means the analysis has to happen before the requisition, not as an afterthought once a req is already open.

That sequencing matters more than most workforce planning content admits. It is easy to skip straight to “we need to hire” the moment a project stalls or a team feels stretched. A proper skills gap analysis forces a pause: is this actually a headcount problem, or is it a skills problem that a hire will not solve either, because the market is short on that exact skill too?

Why Skills Gaps Are a Bigger Problem Than Most Teams Realize

According to the World Economic Forum’s Future of Jobs Report 2025, 63 percent of employers now identify skill gaps in the labor market as the primary barrier to business transformation between 2025 and 2030, up from 60 percent in the prior edition of the same report. The same report estimates that workers can expect roughly two fifths, 39 percent, of their existing skill set to be transformed or made outdated over that same period, and that if the global workforce were 100 people, 59 of them would need some form of training by 2030, with only 29 of those 59 upskillable in their current role.

Separately, McKinsey research that has circulated widely across the HR industry puts the share of companies reporting a skills gap somewhere around 87 percent. Whatever the exact figure, the direction is consistent across every source: most organizations are not short on people, they are short on specific, nameable skills, and most of them have not measured exactly which ones.

That last part is the actual opportunity. A skills gap analysis is not a research exercise for its own sake, it is the step that turns a vague feeling of “the team feels behind” into a specific, prioritized list you can act on, whether that action is training, hiring, restructuring, or contracting.

The Three Inputs Every Skills Gap Analysis Needs

Most published frameworks, including the ones from disprz, imocha, and thirst, converge on the same underlying idea even when they number the steps differently: you need a “what we have,” a “what we need,” and a way to compare the two that accounts for where the world is heading, not just where your org chart sits today.

1. Current employee skills (the “what we have” input)

This comes from a triangulated assessment, not a single source. Relying only on self reported skill surveys tends to overstate proficiency, while relying only on manager opinion misses skills a manager cannot directly observe. The more reliable approach combines three views:

• Structured self assessment against a defined proficiency scale, not an open ended “rate yourself”
• Manager review, weighted toward observed work output rather than general impressions
• Objective skills testing for technical or measurable competencies, which is where a formal skills assessment adds a layer of evidence the first two inputs cannot provide on their own

2. Role benchmarking against future need

This is the input most gap analyses shortchange. It is not enough to document what a role requires today, you need to benchmark what the role will require over the next 12 to 24 months given known product, market, or technology shifts. A practical way to do this is to write what some frameworks call a “12 month execution sentence” for the role, a short statement of what success looks like a year out, then reverse engineer the 3 to 5 skills that sentence depends on. Looking at concrete examples of what a task actually looks like for a given role is a useful gut check here, since a benchmark disconnected from real day to day tasks tends to drift into generic competency language that is hard to measure against later.

3. Market and industry skill trend data

Internal data alone will always be a lagging indicator, since it only reflects skills your organization has already had reason to notice. External market data catches shifts before they show up in your own performance reviews. Glider AI’s own 2025 Skills Report is a useful example of this kind of input in practice: it found that nearly 60 percent of employers reported significant skill changes in existing roles over a two year period, driven mostly by generative AI, and that more than 70 percent of employers believe a lack of skills clarity is already creating a measurable cost or burden on the business. Pairing a data source like that with your own role benchmarks keeps the analysis honest about where the wider market is moving, not just where your team happens to be today.

How to Run a Skills Gap Analysis, Step by Step

1. Define the scope. Pick the team, department, or role family you are analyzing, and state the business objective driving it, a new product launch, a restructuring, or a growth target. A skills gap analysis run without a defined scope tends to produce a list too broad to act on.
2. Build the skills inventory. Gather the current employee skills input described above across the scoped team, using a consistent proficiency scale, typically a 1 to 5 rating, so results are comparable across people and roles.
3. Set the benchmark. Define the target proficiency level for each required skill per role, informed by both the role benchmarking exercise and the external market data input.
4. Quantify each gap. Subtract current proficiency from target proficiency for every skill and role combination. A gap of negative 3 is critical, negative 2 is moderate, negative 1 is manageable and often closable through short term coaching rather than a new hire.
5. Prioritize by business impact. Rank the gaps that touch revenue, delivery timelines, or customer facing quality above gaps that are real but lower stakes. Not every gap deserves the same urgency.
6. Choose the closing strategy for each priority gap. A widely referenced way to frame this decision is the “four Bs”: build the skill internally through training for moderate, closable gaps; buy it externally through hiring when the gap is deep and time sensitive; borrow it through contract or freelance talent for short term or one off needs; or automate, sometimes called “bot,” the task itself when the gap is really about repetitive low value work rather than a durable skill need.

Only after step 6 does it make sense to open a requisition, and only for the gaps the analysis actually routes to “buy.” That is the practical payoff of doing this work up front: it keeps hiring targeted at real, evidenced gaps instead of a generic sense that the team needs more people.

Skills Gap Analysis vs a Skills Assessment vs an ROI Calculation

These three terms get used almost interchangeably in casual conversation, but they answer different questions and happen at different points in the process. A skills gap analysis is the diagnostic step: it tells you which skills are missing and how large each gap is, across a team or role family, before anyone has decided what to do about it. A skills assessment is the measurement instrument used inside that diagnosis, the actual test or exercise that produces a current proficiency score for one person against one skill. And an ROI calculation is a downstream financial question, whether the assessment tooling or training program you eventually choose is worth what it costs. Confusing the three tends to produce projects that jump straight to buying assessment software before anyone has actually mapped out which skills, for which roles, are worth measuring in the first place.

How Often Should You Run a Skills Gap Analysis?

Treat a skills gap analysis as a living dataset rather than an annual snapshot. An annual cadence is a reasonable baseline for a stable team, but rerun the analysis whenever a major trigger occurs: a new product line, a reorganization, a wave of attrition on a specialized team, or an external shift like the kind tracked in industry skills reports. Organizations that only revisit their skills data once a year tend to discover gaps months after they have already affected delivery, which defeats the purpose of running the analysis at all.

FAQs

Once the diagnosis is done and you know exactly which gaps belong to training and which belong to hiring, the next practical step is choosing how to measure proficiency consistently, whether that is through structured skills assessments, evaluating assessment tools built for hiring managers, or working from Glider AI’s own skill assessment software to keep the inventory current as roles keep changing.