How to Run a Skills Gap Analysis (Step-by-Step)

Most organizations have a rough sense that their teams are missing something. The marketing team struggles to use data. The engineering leads lack structured thinking on product decisions. Senior individual contributors can not quite make the leap to people management. The problem is rarely a mystery—what is missing is a disciplined way to measure the distance between where people are and where the role actually requires them to be.

A skills gap analysis closes that measurement problem. Done well, it gives you a concrete, role-specific picture of capability shortfalls, ranked by business impact, with a decision framework for how to close each one. This guide walks through the full process, with a worked example you can adapt immediately.

Step 1: Define Required Capabilities per Role

Start with the role, not the person. For each role you are analyzing, list the capabilities it genuinely requires at the level of performance you expect. Be specific: "communication" is too broad; "executive-level written communication including board-ready summaries" is actionable.

Good sources for this list include the role's job description (if it is current and honest), output standards from top performers in that seat, and the strategic direction your organization is heading. If the company is moving toward data-informed decisions in the next 18 months, analytical reasoning belongs on every manager-level capability list today.

Aim for eight to fifteen capabilities per role. Fewer and you miss important dimensions; more and the assessment becomes unwieldy.

Step 2: Assess Current Levels

For each capability, rate the current level of the individual or team. A clean five-point scale works well in practice:

• 1 – No exposure: little or no experience with this capability
• 2 – Developing: some exposure, inconsistent application
• 3 – Competent: reliable, independent performance in most situations
• 4 – Advanced: applies with nuance, coaches others
• 5 – Expert: sets the standard, recognized as a go-to resource

Assessment can come from multiple sources—manager observation, self-assessment, peer input, or work samples. Self-assessments tend to over-rate technical skills and under-rate interpersonal ones; triangulating with a manager view improves reliability.

Step 3: Quantify the Gap

Gap = Required level minus Current level. A negative number means the person exceeds the requirement for that capability, which is useful to know (it signals a retention risk or an opportunity to deploy that person differently). A positive number is your deficit to manage.

The table below shows a worked example for a mid-level Product Manager role at a company scaling toward enterprise sales:

In this example, customer discovery, SQL basics, and enterprise pricing are the largest gaps. Written specs and roadmap prioritization are already at par.

Step 4: Prioritize by Business Impact

Not every gap is equally urgent. A gap in a capability that is core to the company's growth priorities this quarter deserves more urgency than one that matters at a future stage. Score each gap on two dimensions: magnitude (how large is the gap?) and criticality (how much does this capability affect business outcomes right now?).

A simple 2×2 gives you four buckets:

• High gap, high criticality: address immediately—these are your development priorities
• Low gap, high criticality: monitor and maintain, targeted coaching often sufficient
• High gap, low criticality: schedule for a later development cycle, or re-examine whether the capability truly belongs on the required list
• Low gap, low criticality: deprioritize entirely

In the worked example above, enterprise pricing fundamentals sits in the top-left bucket for a company actively moving upmarket. That makes it the first closure target, even though the gap magnitude is the same as customer discovery.

Step 5: Build, Buy, or Borrow

For each priority gap, decide on the closure mechanism before writing a development plan:

• Build: invest in developing the current person through training, coaching, stretch assignments, or rotations. Best when the person has a reasonable learning trajectory and the organization has time.
• Buy: hire for the capability externally. Warranted when the gap is critical, the timeline is short, and internal development is unlikely to close it fast enough.
• Borrow: bring in the capability on a contract, advisory, or partnership basis while the core team develops. Often the most cost-effective bridge for highly specialized skills.

There is no universally right answer. The decision depends on how critical the capability is, how quickly the gap needs to close, what it will cost to develop vs hire, and whether the capability is a differentiator that belongs inside the organization long-term.

Step 6: Write the Closure Plan

A closure plan is not a list of courses. It is a time-bound, owner-assigned set of actions tied to measurable outcomes. For each priority gap, specify: the target level and by when, the specific activities and resources, who is responsible for the development, and how you will assess whether the gap has closed.

Example: Close the enterprise pricing gap from level 1 to level 3 within 90 days. Actions: two structured sessions with the Head of Revenue on deal mechanics; shadow three enterprise sales calls; complete the Pragmatic Institute pricing course; draft a pricing recommendation for one active deal for manager review by week 8. Success indicator: manager rates written pricing recommendations at level 3 by day 90.

Review progress at 30 and 60 days. Gaps that are not moving despite consistent effort are a signal to revisit the build/buy/borrow decision—not to simply continue the same approach.

Running This in Practice

The process above takes most teams four to six weeks when done by hand: aligning on capability definitions, coordinating assessment inputs, aggregating scores, and drafting plans. The friction is real, and it is the main reason skills gap analysis gets skipped or treated as an annual ritual rather than a working tool.

Treeng's Skills Gap engine runs the same diagnostic in under four minutes. You describe the role and current team against a structured prompt; the engine maps required vs current capabilities, scores and ranks gaps by business impact, and returns a prioritized closure plan with build/buy/borrow recommendations. Every finding carries an evidence grade—solid where the pattern is well-supported, indicative where the signal is present but needs validation, and needs data where a gap is suspected but not yet measurable. That grading discipline keeps the output honest: you can see exactly how much confidence to place in each recommendation before acting on it.