Short answer: a skill gap analysis is three columns – the skills the work demands, the level the team has, the level the role requires – plus one multiplication: gap × importance. That last step is what most DIY attempts skip, and it’s the difference between a wall of red cells and a ranked list you can budget against. The full method below takes about an hour for a team of 5-15 and needs nothing more than a spreadsheet – or the free Skill Gap Estimator, which runs the same math with the weighting built in.
Step 1 – List the skills the work demands (15 min)
Not the skills the team has – the skills the next 12 months of work requires. Pull from three sources:
- The team’s actual deliverables (“ship the mobile app” → React Native, app-store ops, mobile QA)
- Recurring failure points (where do delays, rework, and escalations cluster?)
- The strategy doc (whatever leadership committed to that the team hasn’t done before)
Keep it to 6-10 skills. Twenty-line skill matrices die of their own weight; if everything is listed, nothing is prioritised. Mix hard and soft skills – “runs client meetings without a senior present” is as assessable as “SQL.”
Step 2 – Rate current vs required on a 0-5 scale (20 min)
The scale (define it in writing, or every rating means something different per rater):
| Level | Meaning |
|---|---|
| 0 | No ability |
| 1 | Beginner – needs supervision on everything |
| 2 | Basic – routine tasks with support |
| 3 | Intermediate – works independently on standard work |
| 4 | Advanced – handles complex/novel cases, coaches others |
| 5 | Expert – the person others across the company come to |
Two rules that keep the ratings honest. Rate the team’s working level, not its best member – one expert plus four beginners is not a level-3 team; it’s a bus-factor problem wearing an average. And required means “for effective performance,” not “ideal” – if you set required = 5 everywhere, you’ve written a wish list, and the analysis will tell you to train everyone on everything, which is the same as no answer.
Step 3 – Weight each skill by importance (5 min)
Rate business importance 1-5: how much does this skill block revenue, delivery, or compliance this year? This is the step that turns ratings into decisions, because a 2-point gap on a weight-5 skill matters more than a 3-point gap on a weight-2 skill – and without weights you’ll train the biggest gap instead of the most expensive one.
Step 4 – Compute the weighted gap (worked example)
A 6-person support-engineering team, eight skills scored, showing four here:
| Skill | Current | Required | Gap | Weight | Weighted gap (gap × weight) | Max weighted (required × weight) |
|---|---|---|---|---|---|---|
| Core product debugging | 4 | 4 | 0 | 5 | 0 | 20 |
| SQL / data analysis | 2 | 4 | 2 | 4 | 8 | 16 |
| Customer communication | 3 | 4 | 1 | 5 | 5 | 20 |
| Scripting/automation | 1 | 3 | 2 | 3 | 6 | 9 |
| (4 more skills, no gap) | – | – | 0 | 12 | 0 | 37 |
| Totals | 19 | 102 |
Weighted gap % = 19 ÷ 102 ≈ 18.6%. Readiness score = 100 – 18.6 ≈ 81.4.
Read it against the bands the Skill Gap Estimator uses: 85+ Ready · 65-84 Nearly Ready · 40-64 Needs Development · below 40 Significant Gap. This team is Nearly Ready – functional today, but the ranked list says exactly where it’s thin: SQL (weighted gap 8) first, automation (6) second, communication (5) third. Note that automation outranks nothing here despite having the equal-largest raw gap – its weight of 3 pulls it below SQL. That reordering is the whole point of step 3.
Step 5 – Cost the fix (15 min)
For the priority gaps only (top 2-3, not all eight), estimate:
Training cost = team training hours × (average loaded hourly wage + direct training cost per hour)
The first term is the one budgets forget: employee time is the dominant cost of training. For the SQL gap above – say 6 people × 20 hours, at a ₹600/hr loaded wage plus ₹200/hr of course cost – that’s 120 hours × ₹800 = ₹96,000. Now the gap has a price, and the decision becomes comparable to its alternatives: hire a data analyst, buy a BI tool that removes the need, or accept the gap. Run the numbers in the Training Budget Calculator and sanity-check total hours against team capacity with the Learning Hours Calculator.
Then close the loop: for a gap you chose to train, define before starting what “closed” looks like (re-rate in 90 days; SQL moves 2→3.5+) – that re-rating is also the input your Training ROI case needs.
Train, hire, or restructure?
The weighted list also tells you which fix fits which gap:
- Train when the gap is 1-2 levels and the base exists (SQL 2→4: trainable in a quarter).
- Hire or contract when the gap is 3+ levels on a high-weight skill – training someone 0→4 takes longer than your roadmap has (that’s a requisition, and the Cost Per Hire math applies).
- Restructure the work when the gap exists only because the work is misassigned – sometimes the “skill gap” is one expert hoarding a task that a level-3 process could distribute.
- Watch the bus factor separately: a skill where the team scores 4 because one person is a 5 is a risk the averages hide. Flag any skill held by a single person regardless of its gap score.
FAQ
Self-rating or manager rating? Both, then discuss the deltas – the conversation where an employee self-rates 4 and the manager says 2 is the most valuable output of the whole exercise. For teams that trust each other, calibration in a group session is faster and fairer.
How often should we redo it? Twice a year, or after any strategy change that alters the skill list. The re-rating is also your training-effectiveness measurement – free ROI data.
Does this work for a 3-person company? Yes – smaller teams need it more, because every gap is uncovered by definition. The bus-factor column is the one to watch at that size.
Is this connected to performance reviews? Keep them separate. Skill gap analysis rates the team against the work; reviews rate individuals against expectations. Mixing them makes people defend their ratings instead of reporting them honestly – the same trust rule as stay interviews.
Calculators referenced: Skill Gap Estimator · Training Budget · Learning Hours · Training ROI · Cost Per Hire. The 0-5 scale and weighted-gap method match the estimator, so you can move between the article and the tool without translation.
