Guides
Learn how to conduct a skills gap analysis to identify missing competencies and build a targeted development plan.
A skills gap analysis is the process of comparing your current capabilities to the capabilities required for a specific goal — a target role, a promotion, a career transition, or a team objective. The gap between where you are and where you need to be is the "skills gap," and closing it is the core of strategic career development.
Most professionals have an intuitive sense of what they are missing, but intuition is unreliable. A structured gap analysis replaces guesswork with data:
Choose a specific, concrete target:
The more specific the target, the more actionable the analysis.
Document your current skills with honest depth levels. Use a consistent scale (exposure → working → proficient → expert) and attach evidence where possible.
If you already have a skill graph, this step is done — your graph is your current-state map.
For your target, list every skill mentioned in the job description, competency framework, or role expectations. Assign the minimum depth level required for each.
Example — Target: Senior Backend Engineer
| Skill | Required Level |
|---|---|
| System design | Proficient |
| API design | Proficient |
| Database optimisation | Proficient |
| CI/CD | Working |
| Observability | Working |
| Technical writing | Working |
| Mentoring | Working |
Overlay your current skills on the target. Gaps fall into three categories:
Not every gap needs immediate attention. Prioritise by:
A common prioritisation framework:
| Priority | Criteria | Action |
|---|---|---|
| P0 | Blocks the goal entirely | Close within 30 days |
| P1 | Significantly improves candidacy | Close within 90 days |
| P2 | Nice-to-have, not a blocker | Schedule for next quarter |
For each prioritised gap, define specific actions:
See the How to Build a Skill Graph guide for a 30-day planning template.
At the team level, a skills gap analysis reveals which capabilities are under-represented and where single points of failure exist, that is, when only one person can handle a critical function.
| Skill | Alice | Bob | Carol | Coverage |
|---|---|---|---|---|
| React | Proficient | Working | — | ⚠️ 2/3 |
| System design | Expert | — | Working | ⚠️ 2/3 |
| Observability | — | — | Proficient | 🔴 1/3 |
| Technical writing | Working | — | — | 🔴 1/3 |
In this example, observability and technical writing are fragile — if Carol or Alice leave, those capabilities are lost.
For individuals: once per quarter, or whenever your career goals change. For teams: once per quarter, aligned with planning cycles.
Yes. Skill Graph's AI coach can compare your current graph to a target role and highlight gaps automatically, including recommending learning paths to close them.
A training needs assessment focuses on what training to provide. A skills gap analysis is broader — it identifies the gaps first, then the solution might be training, project work, hiring, or reorganisation.