Skills Gap Analysis: A Template and Process for Small Teams

We hired a second person into delivery because projects were shipping late. Six months and one salary later, they were still shipping late. The constraint was never headcount. One person could turn a client request into a written scope, and everything queued behind her whether we had four people or five.

I had solved a capability problem by buying headcount, which is the most expensive way to be wrong about your own team. Nobody had ever written down what the role actually required, so nobody could see that the queue formed at a single skill held by a single person.

A skills gap analysis sounds like something that needs a competency framework and a consultant. In a small company it needs a grid, a four-point scale, an afternoon, and the willingness to write an honest number next to somebody you like. This is how I run it, including the parts that go wrong. I build the people and records tooling for businesses without an HR department at FirstHR. General guidance, not legal advice.

What a Skills Gap Analysis Is and What It Is For

A skills gap analysis compares the skill level a role requires against the level the people in it currently have, and turns each difference into a decision. The output is a grid with a number in every cell, not a report, and the numbers only matter because of the actions attached to them.

It answers three questions founders otherwise answer by instinct. Where is work slower or worse than it should be because of capability rather than effort? Which capabilities sit inside exactly one head, so a resignation or a two-week holiday stops something the business needs? And what will you need to do in twelve months that nobody can do today?

The third question is the one small companies skip. A grid with a second required column for where the business is going becomes a piece of workforce planning that tells you what to start teaching now.

Worth separating from two adjacent things. Individual measurement methods, including work samples and tests, belong to skills assessment. Deciding what training to deliver belongs to a training needs assessment. The gap analysis sits between them and stays open about whether training is the answer at all.

Defining the Skills That Actually Matter for a Role

Start from the work the role produces, not from a list of skills you found somewhere. A skill belongs on your grid only if you can name a specific piece of work that proves it and you would notice within a month if it disappeared.

Generic lists fail for a specific reason: you cannot rate them. Communication, attention to detail, and problem solving are real qualities and completely unratable, because two managers rating the same person produce different numbers and neither can say why. Rewrite each as a task and the rating becomes almost mechanical.

Cap the list at six to ten skills per role. My first attempt had twenty-two skills for one role, and by the fourth person I was rating from fatigue rather than evidence. Six skills that describe the work honestly beat twenty that describe the job description.

Three sources fill the list quickly. Name the capabilities behind the work the role actually delivered last quarter. Look at what gets escalated to you, because every escalation is a capability gap announcing itself. And check what the company turns down, since work you cannot take is a capability you do not have.

For a formal version, the US Office of Personnel Management publishes competency definitions and proficiency guidance used for federal roles. Built for a very different scale, but the discipline is the useful part: a competency is defined by observable behavior at each level, not by an adjective.

Use your job descriptions as raw material rather than as the answer. Most describe duties rather than capabilities, and a duty list never tells you what somebody needs to be able to do them.

Setting the Required Level Before You Rate Anyone

Decide what the role requires before you look at a single person. If you rate people first and set the bar afterwards, you will describe your current team and call it a standard, which guarantees the grid finds almost nothing.

The required level is a business decision, not a wish. Ask what happens if this skill sits one level lower: does a customer notice, does something get redone, does it land on your desk? If not, the required level is lower than you first wrote, and you just saved yourself a training plan.

Not every skill needs the top of the scale. Most tasks need level 2, meaning the person does it alone to standard without review. Level 3 belongs to a few skills per role, usually the ones where somebody has to teach the next person or notice when the method itself is wrong.

Then set a second number most templates leave out: how many people need to reach that level. This is coverage, and it is where small companies find their real exposure. A skill where exactly one person meets the bar is a risk however well that person performs, which is the logic behind cross-training and any honest succession planning. My rule is two for anything that stops work or money within a week.

Assessing Current Level Without Fooling Yourself

Use three inputs in a fixed order of weight: demonstrated work first, manager assessment second, self-assessment last and never alone. The rating is a claim about what somebody has actually done, so it should be built from what somebody has actually done.

Demonstrated work means recent, real output: the last five scopes she wrote, the reports that shipped without correction, the escalations that were handled and the ones that came to you. This is the strongest input and it is sitting in your systems already, which is why the assessment is far easier at a small company than the enterprise literature suggests.

Manager assessment fills in what output cannot show, mainly consistency and independence. The question is not whether the person can do it, but whether they do it without a second person answering questions. That distinction is exactly the line between level 1 and level 2.

Self-assessment is the input people reach for first because it scales, and it is the one that should carry the least weight. Research on self-awareness reported by Harvard Business Review in January 2018 found that while about 95 percent of people believe they are self-aware, only 10 to 15 percent genuinely are. Skill ratings inherit that gap directly.

The error runs in both directions, which is why no blanket adjustment fixes it. People early in a skill rate themselves high, because they cannot yet see what good looks like. Careful, senior people rate themselves low, because they compare against an expert rather than the requirement. A grid built only on self-ratings ends up inverted in places.

What self-assessment is genuinely good for is different information: what somebody wants to learn and which parts of their job they quietly dread. Use it when you write the plan, not when you set the number.

Every rating gets one line of evidence. Not a paragraph. Quoted eleven non-standard configurations last quarter, two needed correcting is a rating. Seems solid on quoting is an impression, and impressions are what make this exercise argue with itself six months later.

Keep this separate from your performance review cycle. The moment people believe a skill rating feeds their raise, the honest answers stop, and a grid built from defensive answers is worse than no grid. Use a regular one-on-one to check ratings, and say out loud that this measures the role, not the person’s standing.

Scoring: Four Points, Not Ten

Use a zero to three scale where every level maps to something observable. Zero is cannot do it, one is can do it with help, two is can do it alone, three is can teach it and improve the method. The gap is required minus current, and only positive gaps go on the plan.

Ten-point scales fail in a specific way. Everybody lands between six and eight, the differences are undefendable, and the first time somebody asks why they got a seven instead of an eight you discover that you cannot answer. Four levels force a real judgment: either she does it alone or somebody helps.

Level 3 is the level people under-record, and it is the most commercially useful cell in the grid. Every person at level 3 is a teacher already on the payroll, which converts a training budget question into a scheduling question. That is the mechanism behind most realistic small business training: structured on-the-job training from somebody who already does the task well.

The Gap Matrix Template

Copy the structure below into a spreadsheet. Skills go down the side written as tasks, the required level sits in the second column, one column holds each person, and the last three columns hold coverage, the chosen response, and the owner. That is the whole template.

Read it two ways and the findings appear without analysis. Down a person’s column is their development plan for the year, in priority order. Across a skill row is the organizational picture: a row of zeros with one three on it is concentration risk, and a row where everybody sits one level below the requirement is almost never five individual skill problems.

That last pattern deserves a rule of its own. When every person fails the same skill in the same way, the cause is usually a missing standard rather than missing ability, and the fix is one written procedure rather than five training plans. Writing the thing down as a standard operating procedure closes a surprising share of what presents as a skills gap.

Keep the evidence somewhere. A note on the cell or a second tab is enough. If you drop it, the grid degrades into opinion within one cycle, and the second run becomes an argument instead of an update.

A Worked Example for a Small Team

Here is the grid filled in for the four-person delivery team at a 26-person B2B services firm. Required levels were set first, in a separate sitting, before anybody was rated. The scale is the zero to three above.

The bottom row is the finding that pays for the whole exercise. Only Priya can process a renewal, and renewals are how this business gets paid. That is not a training need in the ordinary sense, it is a concentration risk on incoming revenue, and it is cheap to close because the expert is sitting right there.

The first row is the constraint on growth. One person can scope work, so the firm can only sell as fast as Priya can write scopes, which is exactly the trap that made me hire a fifth person instead of teaching the fourth. Dana at level 2 is one level away, so the response is Priya walking Dana through the next four scopes rather than a job posting.

Row four is the pattern that looks like a people problem and is not. Three of four people sit at level 2 against a required 3 on the data quality check. When the same gap appears across the whole team, the cause is usually that nobody wrote down what the check is. One page fixes it, and no training budget is involved.

Row three is the mirror image of row six: Marcus is the only person at the required level on the technical build. Two single points of failure on the same four-person team, and neither was visible from performance conversations, because both people are performing well.

Row two is worth noticing because nothing is wrong with it. Coverage is complete, and the value of the row is that it stops you spending attention there.

Train, Hire, Contract, or Redesign the Role

Every gap that matters gets exactly one of four responses, chosen deliberately rather than by default. Most small business gaps are one level wide with a teacher already on the payroll, which makes training the right answer far more often than founders assume.

Hiring is the option that feels fastest and rarely is. It carries a search, a notice period, a ramp, and a permanent cost against a gap that may be temporary, and the market is not obliging. Before you post the role, check whether the same money spent on two months of a contractor plus internal teaching closes the gap permanently.

Contracting is underused at small scale. Quarterly tax filings, a one-off technical build, a specialist review: gaps you can buy out of this month without a permanent role, and cover for the months while somebody trains into the work. Classification rules matter, so read the boundary between an employee and an independent contractor first.

Redesigning the role is the option nobody lists and the one I have used most. If the same gap shows up on every person you put in a seat, the seat is the problem: you combined three unrelated skills into one job that no realistic candidate holds. Splitting it or moving one task elsewhere is cheaper than a third failed hire.

When the gap is real and the hire is right, hire for the capability rather than the resume. That is the practical argument for skills-based hiring, and a gap analysis gives you exactly the input it needs: a specific level on a specific task, which is far easier to test for than a job title.

Turning the Matrix Into a Plan With Owners and Dates

Pick three gaps, not nine. A grid becomes a plan only when each action has a named owner, a date, and a defined piece of evidence that closes it. Everything else is a description of the world.

Two things make the plan hold: the actions are mostly internal, which removes budget approval as a reason for delay, and people can see their own column.

That visibility has a payoff. Gallup research published in October 2025, from a survey of 15,968 US employees, found 57 percent had participated in on-the-job training and 45 percent had received training to develop new skills, while one in four reported no opportunities for advancement at all (Gallup). Three dated actions is a cheap way to be on the right side of that number.

Each person’s column, read top to bottom, is most of an employee development plan already written. Add what they told you they wanted to learn during the self-assessment, and you have something worth putting in front of them.

Where This Goes Wrong at Small Scale

The most common failure is scope: running the analysis on every role at once, producing a grid nobody finishes and a list of gaps nobody acts on. Two or three constrained roles produce a usable answer in an afternoon.

The second failure is rating without evidence. It feels faster and it costs you the second run, because a grid built from impressions cannot be defended, updated, or discussed with the person it describes. One line per cell is the whole discipline.

The third is treating every gap as a training need. Some gaps are missing procedures, some are missing tools, and some are people doing work the role should never have contained. Running training on a broken process produces a team that executes it more confidently.

The fourth is confusing a low score with a bad employee. A level 1 on a skill the person has never been taught is a finding about your onboarding, not about them. This is exactly why a new hire’s column looks alarming and means almost nothing: gaps everywhere on somebody in month two is an upskilling schedule, not a performance signal.

The fifth is the quiet one: running the analysis, finding real gaps, and doing nothing. That is not neutral, because you have told your team you know exactly where they are weak and chose not to help.

The sixth is building the grid around the people you have rather than the work you sell. Required levels reverse-engineered from your current team come back clean every time, right up until the work changes and nobody can do it.

Frequently Asked Questions