Growth Starts With Capability: How to Identify the Skills Your Business Actually Needs

Most businesses can explain where they want to grow. Fewer can explain exactly what new capabilities that growth will demand from their people, and that gap is usually where the trouble starts. A new product, market, technology investment or transformation programme might look commercially sound on paper, but execution depends on whether the organisation has the people capable of making it happen. When that question is left too late, the response tends to be reactive: a team becomes stretched, a programme stalls, a new role is created and recruitment begins. A better approach starts earlier. Instead of asking, "Who do we need to hire?", ask "What must the business become capable of doing?" It sounds like a small change in wording, but it shifts the whole workforce conversation.

Start with the growth plan, not the skills list

It's easy to start with the skills attracting the most attention. AI. Data. Cybersecurity. Automation. Cloud. Product. All of them may be important. None of them automatically belong in your workforce plan simply because demand for them is rising elsewhere. The skills your organisation needs should come from the work your growth strategy creates. For example:

• Launching a new digital product could increase the need for product management, user research, software engineering and data capability.
• Entering a new market may require regulatory expertise, localisation, commercial partnerships and different leadership experience.
• Scaling enterprise sales might create demand for stronger solution architecture, value engineering and complex negotiation skills.
• Automating operations can increase the need for process design, systems integration, data and change capability.
• Increasing AI adoption may create requirements around data engineering, governance, security, product design and workflow redesign, not simply people with "AI" in their job title.

The important step is connecting the commercial ambition to the work required to deliver it. Think of it as: Growth objective → capability → work → skills → people When that chain is clear, workforce planning becomes much more precise.

Look beyond the job titles you already have

One of the easiest traps is using the existing organisational chart as the template for the future organisation. If growth changes the work, it may also change the roles required to perform it. A business planning significant AI-enabled automation, for example, should not automatically ask how many additional software engineers it requires. The more useful questions are what processes will change, where human judgement will remain important, what new technical capabilities will be necessary and which existing responsibilities may disappear. That could lead to very different hiring requirements. The same applies across technology: a transformation may not need more people everywhere. It might need a smaller number of people with stronger architecture, data, cyber or programme leadership capability. A product expansion may expose a shortage in commercial product experience rather than engineering capacity. Before creating vacancies, establish:

• What new work will exist?
• What existing work will increase?
• What work will reduce or disappear?
• Which capabilities become critical to delivery?
• What level of expertise will actually be required?
• When does that capability need to be available?

This prevents workforce planning from becoming an exercise in replicating yesterday's structure at a larger scale.

Find out what capability you already have

Once the future requirement is clearer, businesses can assess the gap. This is more difficult than comparing a future job description against current job titles, because skills rarely sit neatly inside organisational structures. Someone working in operations may have previous technical experience. An analyst may have automation capability that's underused in their current position. A technical employee may have developed strong commercial or leadership skills without changing title. Others may possess the right foundational skills to move into a new area relatively quickly. A useful review should therefore consider three groups. 1. Capability you already have Identify people already operating at the level the business will require. The priority here may be less about recruitment and more about retention, deployment and ensuring critical knowledge isn't concentrated in too few people. 2. Capability you could develop Look for people with adjacent skills who could reach the required level within an acceptable timeframe. A perfect match isn't always necessary if the underlying capability is strong and the remaining gap is trainable. 3. Capability you genuinely don't have This is where the external talent market becomes important. If the expertise is new to the organisation, required quickly or difficult to develop internally, external recruitment may be the most sensible route. It sounds like an obvious distinction to make, but it's the thing that stops every business problem being translated straight into additional headcount.

Not every skills gap is a recruitment problem

Identifying a gap tells you what is missing. It doesn't tell you how to solve it. Depending on the skill, the right answer could be to:

• Develop existing employees through targeted upskilling or reskilling.
• Move capability internally from another team or business area.
• Hire permanent expertise where the requirement is strategic and long term.
• Borrow capability through contractors, consultants or specialist partners where the need is immediate, niche or temporary.
• Redesign the work so that technology, automation or a different operating model reduces the requirement altogether.

Strong workforce planning uses several of these approaches at once. A business building a new data capability, for example, might hire an experienced leader externally, move analysts from elsewhere in the organisation, develop existing engineers and use contractors to cover specialist requirements during the build. That can be far more effective than trying to recruit an entirely new team from the external market.

Decide which skills actually deserve investment

A detailed skills review can uncover dozens, sometimes hundreds, of gaps. They're not all equally important. The useful question isn't simply "Are we missing this skill?" It's "What happens to the growth plan if we don't have it?" Prioritise capability against factors such as:

• Strategic importance: How directly does it affect a major growth objective?
• Size of the gap: Do you have some capability already, or virtually none?
• Urgency: Is it needed next quarter or in three years?
• Market scarcity: How difficult will the skill be to acquire externally?
• Developability: Can existing people realistically learn it?
• Transferability: Will the capability remain valuable if the strategy changes?

That creates a more useful portfolio, with each skill falling into one of four categories:

• Protect the skills you already have and can't afford to lose.
• Scale the ones that exist but there isn't enough of.
• Acquire the ones the organisation can't build quickly enough internally.
• Explore the rest until the business case becomes clearer.

This matters particularly with fast-moving technologies. Committing substantial hiring budget to every emerging capability can be just as risky as ignoring them completely.

Use the external talent market before you need to hire

External recruitment intelligence can be useful even when no vacancy is open. If a future growth plan depends on a particular capability, understanding the external market early can expose problems while there's still time to respond. You want to know:

• How large is the realistic candidate pool?
• Where is that talent located?
• Which employers currently compete for it?
• What job titles does the market actually use?
• What compensation does the capability command?
• Which adjacent backgrounds could work?
• Are your location or working-pattern requirements restricting the market?
• How long is a credible search likely to take?

That information can influence the workforce strategy itself. If the talent pool is extremely small and expensive, building internal capability may become more attractive. If the skill is available but concentrated outside your normal geography, flexibility could broaden the market. If candidates with an exact background are scarce, hiring around adjacent capabilities may produce a better result. This is where a specialist recruiter should be doing more than responding to vacancies. Good market intelligence can help determine whether the original brief is realistic before a search begins.

Be careful of the "unicorn" role

Skills planning can also improve individual job briefs. When teams begin listing everything they need, there's a tendency to bundle several capability gaps into one person. The result is the familiar vacancy seeking someone who can set strategy, remain deeply hands-on, lead a team, manage stakeholders, understand a particular sector, own transformation and possess detailed knowledge across an extensive technical stack. Sometimes that person exists. Often the business has accidentally written a description of the entire team. For every requirement, separate it into: Must have on day one. Experience or capability that can't realistically be developed after appointment. Can develop. Skills where someone with the right foundation could reach proficiency after joining. Useful, but not essential. Experience that would add value but shouldn't eliminate otherwise strong candidates. That creates a more realistic search and opens the market to people whose skills transfer, rather than only candidates who have previously performed an almost identical role.

Your growth plan should tell you when to hire

The best time to identify future talent requirements isn't when a vacancy becomes urgent. There can be a substantial gap between recognising a need and having productive capability in the business. Recruitment takes time. Notice periods take time. Onboarding and reaching full effectiveness take time. Developing someone internally takes time too. For each important capability, look across several horizons:

• Now: What is required to deliver commitments already made?
• Next: What capability will become important as current growth plans mature?
• Later: Which skills are worth developing now because several possible futures may depend on them?

This is particularly valuable in technology, where capability requirements can change faster than traditional annual workforce plans, so the goal isn't a perfect five-year prediction. It's having enough visibility to avoid discovering a critical capability gap at the exact moment the business depends on it.

Measure capability, not recruitment activity

There's also a difference between filling roles and solving a skills problem. Hiring five people doesn't prove the capability gap has closed. Neither does putting twenty employees through a training programme. What matters is whether the organisation can now perform the work the growth strategy requires. Useful measures might include:

• Coverage of business-critical skills across the organisation.
• Time to competency for people moving into priority roles.
• Internal mobility into the areas that matter most.
• Retention of scarce or hard-to-replace capability.
• Quality and performance of new hires against the roles they were brought in to fill.
• Reliance on contractors, and whether it's falling as internal capability builds.
• Delivery speed or productivity in the areas the capability was meant to support.
• Whether the growth objective the capability underpins remains on track.

The closer workforce measures get to business outcomes, the more useful they become.

The skills question should come before the hiring question

Growth creates new capability requirements. But the answer is rarely as simple as adding more people. The businesses that handle this well start with the strategy, work backwards into the capabilities required, understand what they already have and only then decide how to close the gap. Sometimes the answer will be recruitment. Sometimes it will be development, redeployment, contractors or redesigning the work entirely. Usually, it will be a combination. For technology leaders and hiring teams, that's the real value of looking at skills earlier. You're no longer recruiting because a gap has become painful. You're building the capability the business will need before that gap starts restricting growth. And when external hiring is part of that plan, going to market with a clearly defined capability requirement makes it far easier to find the right person than starting with a job title and hoping the market does the rest.

FAQs

How do you identify the skills a business needs for future growth? Start with the organisation's growth objectives and determine what new capabilities and work they'll require. Compare those requirements against existing and developable internal capability, then identify the gaps that remain. Should businesses hire externally to close every skills gap? No. Depending on urgency, scarcity and the capabilities already available internally, the better option may be upskilling, internal mobility, contractors, specialist partners, automation or a combination of approaches. When should future skills planning begin? Ideally, before the capability becomes an immediate operational requirement. Working ahead gives businesses more options, particularly where specialist talent is scarce or employees require time to develop into new areas.