See what's new

Testlify
Guestpost
Last updated on: 19 September 202612 min read

Not every skills gap needs a headcount

Discover how upskilling, reskilling, and smarter workforce planning can close skills gaps without adding new headcount.

Not every skills gap needs a headcount

Most skills gaps do not need a new employee. A gap means a capability is missing, and hiring is only one of four ways to get it: train someone, hire someone, contract it out, or remove the task.

Most skills gap analyses still end the same way. A gap gets identified, and someone drafts a job description.

That reflex is expensive. It is also often wrong. A gap tells you a capability is missing. It does not tell you that a person is missing. Those are different problems with different fixes, and confusing them is one of the costliest habits in workforce planning.

Here is how to tell them apart, and what to check before a gap becomes a requisition.

Summarise this post with:ChatGPTGeminiClaudeGrokPerplexity

TL;DR

  • A skills gap is a diagnosis, not a prescription. It says a capability is missing, not that a hire is missing.
  • Four options close a gap: build (train), buy (hire), borrow (contract), or remove the task. They answer different questions and they are not ranked.
  • Split the gap before you price it. A capability gap means nobody can do the work. A capacity gap means people can, but have no hours. Only one of those reliably needs a new employee.
  • Hiring is the only option that commits you to a salary that keeps running after the workload drops, so it should be the option you justify, not the one you default to.
  • Before opening a requisition, check whether the skill is core, whether you need it for 12 months or more, whether someone internally is already close, and whether any manager can judge the work.
  • If the answer really is a hire, measure the skill before the offer instead of discovering it afterward.
Build your dream team — Book a product demo

Why does every skills gap turn into a job posting?

Because hiring is the most visible response available. A requisition is easy to approve, easy to report on, and easy to defend. Training plans are slower. Vendor decisions sit with procurement. Redistributing work makes managers uncomfortable. So the gap becomes headcount by default, not by analysis.

The underlying problem is real. In the Future of Jobs Report 2025, 63% of employers call skill gaps the biggest barrier to business transformation between 2025 and 2030, and workers can expect 39% of their existing skill sets to be transformed or outdated over the same period.

Now look at what those employers say they will actually do. 85% plan to prioritize upskilling their workforce, 70% expect to hire staff with new skills, and 50% plan to move people out of declining roles into growing ones. Those numbers add up to well past 100% because they are not alternatives. Gaps get closed with a mix, and hiring is one input to that mix rather than the plan itself.

Is it a capability gap or a capacity gap?

A capability gap means nobody in the building can do the work. A capacity gap means people can do it but have no hours left. The two look identical on a spreadsheet and need opposite fixes. Capability needs new skill. Capacity needs more time or fewer priorities. Only capability sometimes needs a hire.

This is the split most gap analyses skip, and it changes the answer completely. A team that is drowning does not need a specialist. It needs work taken off it, which a contractor or an honest cut to the priority list can do in days. A hire does it in months, and only once the role is filled, onboarded and up to speed.

Pro Tip: ask the hiring manager to name the work that would stop if the new person never arrived. If they list tasks, it is a capacity gap. If they name a skill nobody has, it is a capability gap. The answer usually arrives in under a minute, and it often kills the requisition.

How do you choose between build, buy, and borrow?

Build means training existing employees into the gap. Buy means hiring someone who already has the skill. Borrow means contracting a provider or freelancer. Removing the task is the fourth option nobody writes down. None of these ranks above the others. Each answers a different question about how long you need the skill and how core it is.

Option

What it means

Best when

Watch out for

Build

Train existing employees into the gap

The skill is adjacent to what people already do, and you need it long term

Training takes months, and the practice time has to come from somewhere

Buy

Hire someone who already has the skill

The skill is core to how you compete and needed continuously

Cost per hire, time to fill, and the risk of a mis-hire

Borrow

Contract an external provider or freelancer

The work is well defined, recurring, and not a source of competitive advantage

Less context, less control, and dependency on one vendor

Remove

Automate, simplify, or stop doing the task

The work is repetitive, low-judgment, or was never worth the hours

Automating a bad process just makes the bad process faster

The economics usually favor building when the skill sits next to something an employee already does well. Korn Ferry estimates a saving of around $20,000 per employee from building skills internally instead of hiring for them, and reads the direction of travel as a workforce of roughly 70% permanent and 30% flexible hires, with the flexible share possibly reaching 40% within a decade.

Building has a failure mode worth naming. Training only closes a gap if the person uses the skill on live work soon after, with someone around who can coach it. Send an employee on a course, drop them back into the same queue, and the skill fades before it is ever applied. Budget the practice time, not just the course fee. A targeted training plan tied to specific competencies survives that test better than a generic course allowance.

What should you check before opening a requisition?

Six questions settle most requisitions before they are written. They test how core the skill is, how long you need it, how close someone internal already is, and whether anyone can judge the work once it is done. Answer them honestly and the right option usually picks itself.

Question

If yes

If no

Is this skill core to how we compete?

Lean toward hiring

Consider borrowing

Will we need it continuously for 12+ months?

Lean toward hiring

Consider a contract or project scope

Does someone internally have 70% of it already?

Consider training

Hiring or outsourcing

Is the output well defined and repeatable?

Outsourcing works well

Hiring may fit better

Can we assess this skill reliably before hiring?

Hiring risk is lower

Hiring risk is high

Would the role sit alone, with no manager who knows the work?

Hiring is risky

Hiring is safer

That last row deserves more attention than it gets. Hiring a specialist into a team where nobody can evaluate the work is one of the most common failure patterns in small companies. You cannot coach what you cannot assess. If the first marketing hire reports to a founder with no marketing background, underperformance can run for a year before anyone names it. An external provider does not fix that entirely, but a monthly deliverable is easier to judge than a person's calendar.

When does borrowing beat hiring?

Borrowing wins when the work is well defined, recurring, and not the source of your competitive edge. A provider gives you several disciplines at once and a cost you can stop. A hire gives you one person's skill set, institutional knowledge, and a salary that keeps running whether the workload holds up or not.

Communications is the clearest worked example, because the gap is usually real and the headcount usually premature. A company decides its external communications are weak, and the gap analysis confirms it: nobody internally writes well, pitches media, or runs a content calendar.

The instinct is to hire a specialist. US public relations specialists earned a median of $74,750 a year in May 2025 according to BLS wage data, before payroll taxes, benefits, tools, or the search itself. The same data projects 2% employment growth for the role from 2025 to 2035, so the skill will not get dramatically harder to buy if you wait a quarter.

Then ask what that salary buys. One person's skill set. Communications work usually needs writing, design, video and paid distribution, and those four disciplines rarely sit in one candidate. You will hire someone strong in one, adequate in two, and weak in the fourth.

Contracting the same scope buys coverage rather than hours, and it is a mainstream arrangement rather than an exotic one: 7.4% of US workers were independent contractors on their main job in July 2023. The trade runs both ways. You lose institutional knowledge, instant availability, and a voice in strategy calls. You gain multi-discipline coverage, no ramp time, and a commitment you can end. For a lean marketing function that trade often favors the provider. Where communications drives revenue, it usually does not.

Where does assessment fit once you decide to hire?

Once the analysis lands on hiring, the risk shifts from whether to hire to whether you picked the right person. That is where structured assessment beats resumes, especially for creative and marketing roles, where a portfolio rarely makes clear which parts the candidate personally produced.

The Testlify Competency-to-Evidence Matrix is the useful discipline here: do not start with a test, start with the role. Map the role to the competencies that matter, then connect each competency to evidence you can measure through assessments, work simulations, structured interviews and reviewer feedback. It is the same logic as a structured skills gap analysis, applied to one candidate instead of a whole team.

With Testlify, teams can measure role-specific skills, cognitive ability, personality and situational judgment before the final interview rather than after the offer. For a marketing hire, that might mean testing writing, campaign judgment or analytics reasoning through work simulations instead of trivia questions. Scoring runs at question, test and overall assessment level, so the shortlist is ranked on the competencies you named at the start, not on who interviewed most confidently. The same assessments identify which skills are missing in the team you already have, which is where the question started. The point is not to add a step. It is to make sure that if you accept the cost of a hire, you get the capability you paid for.

Hire only when the gap genuinely needs it

If the analysis does land on a hire, make the shortlist earn it. Book a demo to see how role-specific assessments score candidates on the competencies you defined, before the first interview rather than after the offer.

Key Takeaways

  • A gap is a diagnosis, not a prescription. It tells you a capability is missing, not that a person is. Treating those as the same thing turns analysis into an automatic requisition, so name the missing capability before you name a role.
  • Separate capability from capacity first. Capability means nobody can do the work; capacity means nobody has the hours. They look identical in a planning spreadsheet and need opposite fixes, so the wrong call buys a salary to solve a scheduling problem.
  • Building is cheaper but conditional. The saving only holds if the trained person applies the skill on real work with someone to coach them. Budget the practice time, or the training money gets spent twice.
  • Borrowing buys coverage, hiring buys commitment. One hire gives you one skill set, while a defined scope can cover four disciplines and be stopped. Use borrowing where the output is well defined and not your competitive edge.
  • The manageability test is the one teams skip. If no manager can evaluate the work, a specialist hire can underperform for a year unnoticed, so either fix the supervision or buy a deliverable you can actually judge.
  • If it really is a hire, measure before the offer. Once the cost is accepted, the remaining risk is candidate choice, and structured assessment on named competencies is how you avoid paying a salary for a capability you never verified.

FAQs

Yash Patel
Yash Patel

Wordpress Developer

Yash Patel is a Wordpress and SEO Specialist at Testlify with 3+ years of experience in technical SEO, on-page optimization, and content strategy. He works on improving Testlify's organic presence and produces content focused on hiring, talent assessment, and HR technology.

LinkedIn

Get started.

Hire on proof, not resumes.

Run your first skills-based assessment free — no credit card required.

We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies.