Run a Skills Gap Analysis Before You Buy Any Training
It is easy to book training before anyone has agreed what problem it should solve. The result is familiar: a well-reviewed course that everyone attends and nothing changes afterwards.
Silicon Lab Team30 Aug 20265 min read
It is easy to book training before anyone has agreed what problem it should solve. The result is familiar: a well-reviewed course that everyone attends and nothing changes afterwards. A skills gap analysis prevents this. It connects what the organisation needs to achieve with what its people can currently do, and shows exactly where training will help, and where it will not.
This guide takes you through the process in six steps.
Step 1: Start with what the business needs
Begin with goals, not skills. What does the organisation need to achieve over the next year or two? For example:
- Move customer records to a new system.
- Reduce the time it takes to resolve support requests.
- Start using data to plan stock or staffing.
- Adopt a new security standard.
For each goal, ask: which teams are involved, and what will they need to be able to do differently? This keeps the analysis focused on outcomes that matter rather than a general wish list.
Step 2: Map roles to skills
For each role involved, list the skills it requires to meet those goals. Be specific. "Computer skills" is not useful. "Builds and maintains spreadsheet reports using lookups and pivot tables" is.
Put this into a simple skills matrix: roles down the side, skills across the top. Then define a small number of levels for each skill so everyone assesses the same way. For example:
- Aware — understands what the skill is and when it is needed.
- Working — can do routine tasks with support.
- Independent — can do the task reliably without help.
- Expert — can handle unusual cases and teach others.
Write one sentence describing each level for each skill. It takes time, but it removes much of the guesswork later.
Step 3: Gather evidence of current ability
Now find out where people actually are. Use more than one source, because each has weaknesses:
- Self-assessment is quick, but people can over- or under-rate themselves.
- Manager assessment adds perspective, but managers do not always see the detail of the work.
- Work samples — real reports, code, tickets or documents — show what people produce.
- Short practical tasks give the clearest picture for specific technical skills.
Explain to staff why you are doing this. If people believe the assessment will be used to judge them, they will be less honest. Frame it as planning for support and development, and keep individual results confidential where you can.
Step 4: Rank the gaps
You may find more gaps than you can address at once. Rank them by asking four questions about each:
- Impact: How much does this gap hold back a business goal?
- Urgency: When does it need to be closed?
- Breadth: How many people or teams does it affect?
- Is training the answer? Some gaps are really about unclear processes, missing tools, poor documentation or too few people. Training will not fix those.
That last question is the most valuable part of the exercise. It stops you spending money on courses to solve problems that a clearer process or better tool would fix more cheaply.
Step 5: Write a training brief
A clear brief lets training providers propose something that fits, instead of offering whatever is in their catalogue. Include:
- Context: the business goal and why it matters now.
- Audience: which roles, how many people, and their current level.
- Target outcome: what participants should be able to do afterwards, described as tasks, not topics.
- Constraints: budget range, timing, on-site or online, hours per week people can realistically give.
- Tools and environment: the software or systems participants use, so exercises can be realistic.
- How success will be measured: see the next step.
Ask providers to explain how their proposal addresses the specific outcomes, and how they will adapt if participants start at different levels.
Step 6: Decide how you will measure success
Agree on this before training starts, not after. Useful measures connect to the original goal:
- Re-assess the same skills using the same levels a few weeks after training.
- Look at the work itself: are reports produced faster, are tickets resolved sooner, are fewer errors found?
- Ask managers whether people are applying what they learned.
Plan for application, too. Skills fade quickly if they are not used. Give participants a real task that uses the new skill soon after training, and make time for it.
Common pitfalls
- Training as a reward. Sending people on courses as a perk, without a clear link to their work, rarely changes much.
- One course for everyone. Mixed levels in a single session leave beginners lost and experienced staff bored.
- No follow-up. Without a chance to apply the skill, the effect of training can disappear.
- Skipping the "is training the answer?" question. It is often the most useful question in the whole analysis.
A quick checklist
- Business goals for the period are written down.
- Each relevant role has a list of specific skills.
- Skill levels are defined in plain language.
- Current ability is assessed from more than one source.
- Gaps are ranked by impact, urgency and breadth.
- Non-training gaps are separated out and assigned to someone.
- A written brief exists for each training need.
- Success measures and follow-up tasks are agreed in advance.
The takeaway
A skills gap analysis is not paperwork before the real work. It is the work that makes training worthwhile. By starting from business goals, gathering honest evidence and separating training problems from other problems, you spend less and get training that changes how people work.