A skills gap analysis compares the skills each role needs with the skills your people have today, scores the difference, and ranks it so you know what to fix first. The method below uses five steps and a 0-4 rating scale, and the table you can copy into a spreadsheet is the template.
The reason leadership keeps asking for one is simple. In the World Economic Forum’s Future of Jobs Report 2025, 63% of employers named skills gaps as a major barrier to business transformation through 2030, and employers expect 39% of existing skill sets to be transformed or become outdated.
This guide is written for an L&D manager or HR business partner who has to put a defensible analysis in front of leadership this quarter. It ends with a worked example for a mid-size company’s L&D and operations team. The numbers in that example are illustrative, not real data.
What is a skills gap analysis, and what is it not?
A skills gap analysis measures the distance between the proficiency a role requires and the proficiency people currently show, skill by skill. It does not explain why a gap exists or whether training is the right fix. It produces a ranked list of gaps that you can act on.
That last point separates it from a needs analysis. A training needs analysis asks why a performance problem exists and whether training will solve it. A skills gap analysis supplies the measured gaps that a needs analysis then investigates. If the difference between the two terms still blurs for you, this comparison of training needs analysis vs training needs assessment sorts it out.
It also differs from a labor market skills shortage. The OECD’s October 2026 report Mapping Skill Shortages in OECD Countries uses its Skills for Jobs database to measure skill imbalances across 38 countries, with shortages most acute in high-skilled occupations such as ICT and health. Your analysis is the company-level version of that picture: it covers the people you already employ, not the hiring market.
What do you need in place before you start?
You need three things before you rate a single skill: a named sponsor, a short list of roles, and a decision date. Without a sponsor, nobody owns the required levels. Without a decision date, the results become a report that sits in a folder.
The sponsor is usually the business leader whose team is being analyzed, not HR. They set the required proficiency, because only they know what the work demands. In LinkedIn’s 2025 Workplace Learning Report, which surveyed 937 L&D and HR professionals, 49% said their executives worry employees lack the skills to execute business strategy. Your sponsor probably already shares that worry, so frame the work as an answer to it.
Limit the first pass to three to five roles. A narrow, finished analysis beats a company-wide one that stalls at step three.
How do you run a skills gap analysis in five steps?
Run the analysis in this order: define the target roles, build the skills list from a taxonomy, rate current against required proficiency, score each gap by business criticality, then decide whether to build, buy or borrow. Each step feeds the next, so do not skip ahead.
Step 1: Which target roles do you define first?
Pick roles where a skills shortfall would hurt a business outcome within the next 12 months. Revenue roles, compliance-critical roles and roles tied to a planned change such as a new system are the usual starting points.
For each role, write one sentence on what a fully competent person delivers. This sentence keeps the skills list honest. If a skill does not help that person deliver the outcome, it does not belong on the list.
Step 2: How do you build a skills list from a taxonomy?
Start from an existing taxonomy rather than a blank page, then trim to six to twelve skills per role. Fewer than six usually misses something. More than twelve makes the rating exercise tedious, and the quality of ratings drops.
Public sources save weeks. O*NET, the US occupational database, lists 25 transferable skills across five categories: complex problem solving, resource management, social, systems and technical skills. Use these for broad capabilities, then add the technical skills specific to your tools and processes. Our guide to designing a skills taxonomy covers granularity and maintenance, including the test of whether you could assign a learning activity to a skill. If you cannot, the skill is too vague to close.
Write each skill as something observable. “LMS reporting configuration” can be rated. “Technical aptitude” cannot.
Step 3: How do you rate current against required proficiency on a 0-4 scale?
Rate every skill twice: the level the role requires and the level each person shows today. Use the same five anchors for both ratings so the numbers compare cleanly. The anchors below describe behavior, not seniority.
| Level | Label | What you can observe |
|---|---|---|
| 0 | No exposure | Has not used the skill and cannot describe it. |
| 1 | Awareness | Knows the terms and the basic idea. Needs step-by-step help to do the task. |
| 2 | Working | Completes routine tasks alone. Asks for help with exceptions. |
| 3 | Proficient | Handles exceptions independently and produces work others rely on. |
| 4 | Expert | Sets the standard, coaches others and fixes problems the team cannot. |
Collect ratings from the person and their manager, then reconcile any difference of two or more levels in a short calibration conversation. Where possible, anchor the rating to evidence: a work sample, an assessment result, a certification or a documented project.
Calculate the gap as required level minus current level, and floor it at zero. A person at level 4 in a skill that needs level 2 does not cancel out a colleague at level 1. Surplus skill in one person does not close a gap in another.
Cap Unproven Ratings at 2
Add one rule to your calibration meeting: a rating of 3 or 4 needs a named piece of evidence, otherwise it is recorded as 2. This single rule removes most of the inflation that self-ratings and friendly manager ratings introduce, and it costs nothing.
Step 4: How do you score each gap by business criticality?
Multiply the average shortfall for each skill by a criticality weight from 1 to 3. The weight is the sponsor’s call and reflects consequence, not difficulty. This step is what turns a list of gaps into a ranking leadership can accept.
Define the three weights before anyone rates anything:
- 3, business critical: a shortfall causes lost revenue, a compliance failure, a safety risk or a missed commitment.
- 2, important: a shortfall slows delivery or lowers quality, but work still ships.
- 1, useful: a shortfall is an inconvenience or a future preference.
Average shortfall is the mean of each person’s gap, counting only people below the requirement. Track a second number beside it: how many people sit below the required level. A skill with a small average gap that affects most of the team is a different problem from one concentrated in a single person.
The priority score is average shortfall times criticality. Set your own band cut-offs after you see the spread. In the example below, 2.5 or higher means act this quarter, 1.5 to 2.4 means plan this year, and below 1.5 means monitor.
Step 5: How do you decide to build, buy or borrow?
Choose build, buy or borrow for each high-priority gap using the decision rules in the section after the worked example. Build means developing current employees, buy means hiring, and borrow means using contractors, vendors or partners for a defined period.
What does a skills gap analysis template look like?
The template is one sheet with a row per skill. Copy the column headers below into a spreadsheet, add one row per skill, and add one rating column per person. The formulas calculate everything else.
| Column | What to enter |
|---|---|
| A: Skill | One observable skill from your taxonomy. Analyze one role at a time. |
| B: Required level | 0-4, set by the sponsor using the anchors above. |
| C to H: Person ratings | Current level 0-4 for each person, after calibration. Fill every cell. |
| I: Average shortfall | Formula. Mean of each person’s gap, counting only gaps above zero. |
| J: People below | Formula. Count of people rated under the required level. |
| K: Criticality | 1, 2 or 3, set by the sponsor. |
| L: Priority score | Formula. Average shortfall times criticality. |
| M: Band | Formula. Act this quarter, plan this year or monitor. |
| N: Decision | Build, buy, borrow or monitor. |
| O: Action, owner, date | One concrete next step with a name and a date. |
Paste these formulas into row 2, then copy them down. They assume six people in columns C to H and work in both Excel and Google Sheets:
I2: =SUMPRODUCT((B2>C2:H2)*(B2-C2:H2))/COUNT(C2:H2) J2: =COUNTIF(C2:H2,"<"&B2) L2: =I2*K2 M2: =IF(L2>=2.5,"Act this quarter",IF(L2>=1.5,"Plan this year","Monitor"))
What does a worked skills gap analysis look like for a mid-size L&D team?
The example below analyzes a six-person learning and operations team at a mid-size company against one shared role profile. All ratings, weights and decisions are illustrative, not real data. In practice you would run one profile per role.
| Skill | Req. | P1 | P2 | P3 | P4 | P5 | P6 | Avg shortfall | People below | Crit. | Score | Band |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Learning data analysis | 3 | 2 | 1 | 2 | 1 | 2 | 3 | 1.17 | 5 of 6 | 3 | 3.5 | Act this quarter |
| AI-assisted content production with review | 3 | 3 | 2 | 2 | 3 | 1 | 2 | 0.83 | 4 of 6 | 3 | 2.5 | Act this quarter |
| Evaluation design (Kirkpatrick levels 3 and 4) | 3 | 2 | 2 | 1 | 2 | 3 | 2 | 1.00 | 5 of 6 | 2 | 2.0 | Plan this year |
| Skills taxonomy and mapping | 2 | 1 | 1 | 2 | 0 | 1 | 1 | 1.00 | 5 of 6 | 2 | 2.0 | Plan this year |
| LMS administration and reporting setup | 3 | 4 | 3 | 3 | 2 | 3 | 1 | 0.50 | 2 of 6 | 3 | 1.5 | Plan this year |
| Instructional design, storyboard to build | 3 | 3 | 3 | 4 | 3 | 2 | 2 | 0.33 | 2 of 6 | 3 | 1.0 | Monitor |
Two things stand out. First, weighting changes the order. AI-assisted content production has a smaller raw gap than evaluation design or taxonomy work, but its criticality of 3 lifts it to second place. In this fictional company, leadership wants AI-drafted content reviewed before it reaches learners, so a shortfall carries real consequence.
Second, the averages hide the shape of the problem. Instructional design has an average rating of 2.8, which looks fine, yet two people sit below the requirement. Always read the average shortfall and the people-below count together.
Now the decisions. Each row applies the rules in the next section.
| Skill (by score) | Decision | Reasoning and first action |
|---|---|---|
| Learning data analysis | Borrow, then build | Five of six are below target and leadership wants dashboards in 90 days. Contract an analyst for one dashboard, with P6 (the only person at level 3) as the internal lead and a handover session as a deliverable. |
| AI-assisted content production | Build | P1 and P4 already rate 3. Have them write the team’s review checklist and pair with P2, P3, P5 and P6 on live projects. |
| Evaluation design | Build | P5 is the only person at 3. Run one Level 3 evaluation as a shared project with P5 as mentor. |
| Skills taxonomy and mapping | Borrow | This is a one-off setup task needing level 2 only. Use an external expert or a vendor-supplied taxonomy, then train the team to maintain it. |
| LMS administration | Build | Only P4 and P6 are below target, and P1 rates 4. Pair them with P1 on the next configuration change. |
| Instructional design | Monitor | Score is below the cut-off. Cover P5 and P6 through normal project feedback and re-rate at the next cycle. |
No row says buy. That is deliberate: for every skill, at least one person on the team already holds the required level, so the buy rule below does not trigger.
How do you choose between building, buying and borrowing skills?
Build when someone on the team already holds the required level and can teach it. Buy when nobody does, or when the need is permanent and growing. Borrow when the need is short, urgent or uncertain. Check these three tests in order and take the first one that fits.
| Option | Choose it when | Watch out for |
|---|---|---|
| Build (train current employees) | At least one person is at the required level, the gap is one or two levels, several people are affected and the deadline is longer than a quarter. | Mentors with no protected time. Name the hours, not just the person. |
| Buy (hire) | Nobody internal is at the required level, the skill is core and ongoing, and there is headcount or an open role. | Hiring slowly into a gap that is urgent. Pair it with a borrow in the meantime. |
| Borrow (contractor, vendor, partner, secondment) | The need is one-off, the deadline is under about three months, or the skill is changing too fast to build depth yet. | Knowledge walking out the door. Make a handover and documentation part of the contract. |
The World Economic Forum’s 2025 survey reports two employer responses that map to the first two options: 85% of employers plan to prioritize upskilling their workforce (build) and 70% plan to hire staff with new skills (buy). Borrowing is a third route that those two figures do not cover, yet it is often the fastest way to cover a gap while a build effort ramps up. For the build route, our guide to upskilling vs reskilling vs cross-skilling explains which type of development fits which gap.
Borrow to Build
When you borrow capability, write the knowledge transfer into the contract: a named internal counterpart, a documented method and a session where the contractor teaches the team. Otherwise you pay for the output once and again for the next gap.
How do you present a skills gap analysis to leadership?
Give leadership one page: the top three gaps, what each costs the business if left alone, the decision you recommend for each, and the date you will re-measure. Keep the full sheet as an appendix. Executives need decisions, not 60 rows.
Lead with the consequence in business terms, using the sponsor’s own criticality definitions. State the decision you need from them, such as approving a 90-day contractor or protecting mentor hours. Then show the date you will re-rate the same skills so they can see progress against the same scale.
Once leadership agrees, the next question is how the decisions become a program. Our guide to workforce development programs and L&D strategy picks up from there, so this analysis stops at the decision.
What mistakes make a skills gap analysis useless?
Most failed analyses share five mistakes. Avoid these and your results will survive scrutiny:
- Too many skills: more than twelve per role produces rushed, inflated ratings.
- Required levels set by HR alone: the business leader must own them, or the gaps are opinion.
- Rating without evidence: unchecked self-ratings drift upward and hide the gaps you need to see.
- Offsetting gaps with surplus: a strong colleague does not cover a weak one, so floor each gap at zero.
- No decision or date: a ranking with no owner or re-measure date is a report, not a plan.
What should you do next?
Pick one role family and one sponsor this week. Copy the template, load six to ten skills from your taxonomy, and book a single calibration session to agree the ratings. That is a realistic scope for one quarter.
Set the sponsor’s criticality weights before anyone sees the scores, and write the re-measure date on the first slide. When you re-rate in six months, use the same anchors so the change in average shortfall is a fair measure of whether your build, buy and borrow decisions worked.
FAQ
Q1. What is a skills gap analysis?
A skills gap analysis compares the proficiency each role requires with the proficiency people currently show, skill by skill, and scores the difference. The output is a ranked list of gaps. It tells you where the distance is largest and most costly, so you can decide where to build, buy or borrow capability.
Q2. How is a skills gap analysis different from a training needs analysis?
A skills gap analysis measures the distance between required and current skills. A training needs analysis goes further and asks why the gap exists and whether training is the right fix, or whether a process, tool or management issue is the real cause. Run the gap analysis first, then investigate the largest gaps.
Q3. How many skills should you assess per role?
Six to twelve is a practical range, based on keeping ratings careful rather than on any published standard. Fewer than six tends to miss something important. More than twelve makes the rating exercise tedious, and people start rating quickly and generously. Start from a taxonomy, then cut anything you could not assign a learning activity to.
Q4. What rating scale works best for a skills gap analysis?
A 0-4 scale with behavioral anchors works well: no exposure, awareness, working, proficient and expert. Including zero lets you separate people who have never used a skill from those with basic awareness. Use identical anchors for required and current levels, and require evidence for any rating of 3 or 4.
Q5. Can you run a skills gap analysis in Excel or Google Sheets?
Yes. One sheet is enough: a row per skill, a required level, one rating column per person, and formulas for average shortfall, people below target, priority score and band. The template in this article lists the columns and the four formulas. Analyze one role at a time so the required levels stay meaningful.
Q6. How often should you repeat a skills gap analysis?
Run a full analysis for core roles once a year, and again after a major change such as a new system or strategy shift. Re-rate your top-priority skills about every six months using the same anchors, so the change in average shortfall shows whether your build, buy and borrow decisions are working.