Skills gap analysis: finding out what your team cannot do yet

A skills gap analysis compares the skills a team needs to deliver its work with the skills it actually has, then quantifies the difference. It is the step most training plans skip: courses get chosen because they are available or fashionable, rather than because a specific gap was measured. A good skills gap analysis produces a short list of gaps that matter, each with a decision attached — train, hire, contract, redeploy or stop doing the work.

How to run a skills gap analysis

1. Define the skills that matter per role, in observable terms: "can configure and troubleshoot the CI pipeline", not "DevOps mindset".
2. Set the required level for each skill and role, using a simple scale — aware, capable, expert.
3. Assess current levels: self-assessment plus manager validation, and evidence such as certifications or recent work.
4. Add the demand side: which skills the next year of work requires, from the business plan and project pipeline.
5. Calculate the gap per skill — how many people at which level are missing, and where the single points of failure are.
6. Decide an action per gap, with owner, cost and date, and re-measure after the action.

Keep the assessment honest

The biggest risk is that people inflate or deflate their own levels. Two things help: separate the skills assessment from performance reviews and pay, and require evidence for the highest level rather than asking for a self-rating alone. Assess the skill, not the person — the question is whether the team can do the work, not who is good and who is bad. Expect a spread of levels; a team where everyone claims expert has told you nothing.

Pay particular attention to skills held by exactly one person. A single point of failure is a bigger operational risk than a skill nobody has, because the work is already depending on it.

From gap to decision

• Small gap, many people: group training or internal knowledge sharing.
• Large gap, strategic skill: hire deliberately, and pair the hire with people who should learn it.
• Single point of failure: cross-train at least one backup, and document the work.
• Short-term, specialist gap: contract it, with a knowledge transfer requirement written in.
• Gap in a skill the business is exiting: do nothing, and say so, so nobody wastes budget on it.

Ettex Sheets is enough to run this: a matrix of roles and skills with required and actual levels, a gap column that calculates itself, and a filter for single points of failure. The output feeds the training plan, the hiring plan and internal mobility decisions — and because it is a sheet rather than a survey tool, updating it each quarter takes an hour rather than a project.