How to identify skills gaps in your team

To identify skill gaps, write down the capabilities your goals require over the next 12 to 24 months, audit what your team can actually do today, overlay the two, then rank what is missing by impact and difficulty. The step most teams skip is the last one before acting: checking whether what you found is a skill gap at all, rather than a performance problem, a resourcing shortfall or an unclear expectation. Those four look identical on a dashboard and need completely different responses.

Last reviewed September 2026.

How to identify skill gaps in four steps

Skill gaps rarely announce themselves. What you notice is a project running long, a handover that keeps bouncing back, or one person being pulled into every second escalation. By the time the gap is obvious in a report, it has usually been visible in a roster for months.

Step 1: Define the work the business is heading towards

You cannot see what is missing until you have described the destination. Take your next 12 to 24 months of objectives and translate each one into work that has to get done. Entering a new market and bringing a manual process in-house call for quite different capabilities, and the translation is the hard part. "Improve retention" is a goal. "Analyse churn data monthly and run difficult conversations with unhappy accounts" is work, and work can be assessed.

Do this with department heads in the room. The executive view of what a team does and the on-the-ground reality diverge more than most leaders expect, and the gap between those two versions is itself useful information.

Step 2: Audit what your team can do today

Auditing honestly is harder than it sounds, because roles hide capability. Someone may be excellent with data and spend their week on work that never touches a spreadsheet. Use more than one source: self-assessment picks up hidden strengths, peer input corrects for over-confidence, and performance data grounds both.

Record the result as a skills matrix with proficiency levels rather than ticks. "Can do it unsupervised", "can do it with support" and "has never done it" are different states, and a matrix that collapses them into a yes or no will hide your real exposure. Behaviour belongs in the audit too. Compono's work personality framework describes eight ways people prefer to work, being Doer, Auditor, Helper, Advisor, Pioneer, Campaigner, Evaluator and Coordinator, and a team can hold every technical skill it needs while still lacking anyone who naturally drives a decision to a close.

Step 3: Overlay the two and find what is missing

Put the required capabilities down one axis and your people across the other. Gaps show up in four shapes: capabilities nobody holds, capabilities only one person holds, capabilities plenty of people hold at a level below what the work needs, and capabilities the team has but cannot evidence when someone asks. The single-holder gaps are the ones that hurt first, because they look fine until that person takes leave. If you want a quick read on the size of the exposure before you build the full matrix, the skills gap analysis calculator gives you a rough number to take into a planning conversation.

Step 4: Rank the gaps before you act on any of them

Not every gap is worth closing. Score each one on how directly it blocks a stated objective and on how hard it is to fill. A gap that blocks a key objective and is easy to train sits at the top of the list. A gap that is hard to fill and only matters to a project that may not proceed can wait, and saying so out loud is what stops a skills plan turning into a wish list. Our step-by-step guide to conducting a skills gap analysis works through the scoring in more detail.

How to tell a skill gap from a performance gap

This is where most analyses go wrong, and it is why training budgets get spent on problems training cannot fix. A skill gap means the person does not know how. A performance gap means the output is below standard, and the cause might be skill, or might be something else entirely.

Four questions separate them quickly. Has this person ever done the task to standard? If yes, the skill exists and something has changed around them. Can they describe what good looks like? If not, the gap is expectation rather than capability. Do they have the time, tools and authority to do it? If not, no amount of training will help. And does the problem follow the person, or follow the role? A problem that stays when a new person arrives is a design problem in the role.

Running those questions before you book a course saves money and, more importantly, saves the relationship. Telling someone they need training when they actually need a decision from their manager is a fast way to lose them.

Skill gap, competency gap, performance gap or talent gap

The four terms get used interchangeably in job ads and vendor decks, which is unhelpful when each one points at a different fix.

Where the skills data lives matters here too. Learning systems track completion, core HR systems track roles and headcount, and neither is designed to answer "who can do this to standard". The difference between an LMS and an HRIS is worth understanding before you assume your current stack can produce the matrix.

How to run a competency gap analysis

A competency gap analysis is the more formal cousin of a skills audit, and it is the right tool when the work is regulated, safety-critical or licensed, because it produces evidence rather than opinion.

Start with a competency framework that defines each capability and, for each one, what it looks like at each proficiency level. The levels are the whole point. Without them you get a list of words everyone agrees with and nobody can assess against.

Then set the required level per role, assess each person against it using evidence rather than recall, and report the distance between the two. The output is a distribution rather than a score: how many people sit at or above the required level, how many sit one level below, and which capabilities have nobody at the top level at all. That last column is your succession risk, visible a year before it becomes an emergency.

Reassessment is what makes it defensible. A framework assessed once is a snapshot. A framework reassessed on a cycle shows movement, which is the only thing that proves development worked.

What to do once you know which gap you have

Build or buy is the decision, and the honest answer usually depends on how far the gap sits from where the team is now. A capability adjacent to what people already do is almost always cheaper to build. A capability with no foothold in the team, needed soon, is usually a hire.

Here is an illustrative worked example, using made-up numbers rather than client data. A support team of 12 needs 9 people able to run churn analysis unsupervised. The audit finds 4. The gap is 5 people. An internal six-week program at an illustrative $1,200 a head would cost $6,000 to take those 5 to the required level, and would take most of a quarter. A single external hire, at an illustrative $18,000 in recruitment cost, closes one of the 5 immediately and leaves 4 still open. On those illustrative numbers the build option is better value for a gap this close to the team's existing work, and the hire only makes sense if you also need capability the team has no foothold in at all.

Whichever way you go, write down how you will know it worked before you start. Course completions are not evidence. Reassessment against the same standard, a task moving off the escalation list, or a second person able to cover the work when the first is away are all things you can actually check. Compono Develop maps skills and work preferences across a team so the matrix updates as people develop, rather than sitting in a spreadsheet that is accurate on the day it is built and slowly wrong after that.

Then run it again. A skills audit has a shelf life of about a year in a stable team and a lot less in one that is growing.

Frequently asked questions

How do I identify performance gaps rather than skill gaps?

Ask whether the person has ever done the task to standard, whether they can describe what good looks like, and whether they have the time, tools and authority to deliver it. If the capability has been demonstrated before, the cause sits in the conditions around the work rather than in the person's skills.

What is the difference between a skills gap and a talent gap?

A skills gap is a missing capability among the people you already have. A talent gap is not having enough people, or the right mix of strengths, to cover the work at all. One points to development, the other to recruitment or workforce planning.

How often should we run a skills gap analysis?

A full analysis once a year suits most teams, with a lighter check every six months or whenever the strategy or the team structure shifts. Growing teams need it more often, because the audit ages faster than the matrix suggests.

What is a competency gap analysis?

It is an assessment of people against a competency framework that defines proficiency levels for each capability. Rather than asking whether someone has a skill, it asks what level they hold it at and how far that sits from the level the role requires.

Can behaviour and soft skills be part of a skills gap analysis?

Yes, and they are often where the real gap sits. A team can hold every technical skill it needs and still have nobody who naturally closes out a decision or pushes back on a weak plan.

How do I get my team on board with a skills audit?

Be direct about the purpose and share the results with the people in them. An audit run to target development and spread single-person dependencies is something people will engage with. One that feels like a performance file being built quietly will get you careful, useless answers.