Strategic Workforce Planning in 2027

Strategic workforce planning (SWP) is the process of working out which people, with which skills, an organisation will need to deliver its strategy, and how it will get them through hiring, development, redeployment or automation. It differs from headcount planning, which asks how many people each team needs next year. For 2027 the practical shift is from a yearly spreadsheet to a plan that is revisited often and built around skills and scenarios.

Most writing on the subject covers the internal half: your own employees, skills inventory and attrition. This article adds the external half, meaning the supply of talent in the market and the way competitors are organised, because a plan that ignores both is a forecast of demand with no view of whether the supply exists.

McKinsey's State of Organizations 2026, which draws on responses from more than 10,000 senior executives, found that 39% of organisations run strategic workforce planning only every two to three years, another 39% yearly, and just 14% have more flexible planning in place. Gartner research cited by Deloitte reports that only 29% of chief human resources officers are confident in their ability to deliver on strategic workforce planning goals.

The mismatch is with the pace of change. The World Economic Forum's Future of Jobs Report 2025 found that employers expect 39% of workers' core skills to change by 2030, that 63% name skill gaps as the biggest barrier to business transformation, and that only 29% expect talent availability to improve over the period while 42% expect it to decline. A plan refreshed every few years cannot respond to a market moving at that rate.

Deloitte's analysis of 87 organisations running skills-based programs found that the ones achieving value start with the business outcome they want and then apply specific skills practices, rather than attempting a wholesale move to a skills-based organisation. Only 2% of HR leaders in a Gartner poll said their organisations had adopted skills-based approaches across all processes. For organisations pursuing innovation and growth, the same research names skills-based workforce planning as the most important practice, since it replaces a count of roles with a view of capability.

In practice this means writing the plan around questions such as: which three capabilities does the 2027 strategy depend on, how many people hold them today, and where else in the market do they work. The first two questions are internal. The third needs outside data.

Public professional profile data supports three supply-side questions well. How many people hold a given skill or title in a region. How competitors structure the same function. And which employers and schools feed the talent you want. Each of these can be answered with a filtered search that returns a total, so you can read the size of a pool without paging through it.

The same pattern works for competitor structure and feeder employers. A seniority breakdown shows whether a rival builds its data function as many individual contributors under a few leaders or with a heavier management layer, and a past-employee list shows which companies its people came from.

McKinsey's 2026 report argues that scenario-based planning will be a must-do, because the pace of AI adoption makes any single forecast fragile. For the supply side, a scenario is a pool size under different assumptions: the same search with a different seniority, a wider set of countries, or a shorter tenure requirement. Re-running those searches each quarter gives a trend line, and a pool that shrinks quarter on quarter is a risk you can see before a requisition opens.

Keep the output as ranges with the date of each run. A pool of "roughly 400 to 600 people across two countries" supports a decision. A precise figure from a dataset that does not cover every professional gives a false sense of accuracy.

Internal HR systems and external profile data are complements, and each is weak where the other is strong.

Three limits matter. Compensation is not in public profiles, so any pay figure attached to a market analysis is modelled, not measured. Attrition rate cannot be computed reliably, because indexed counts are not true headcount and departures surface at whatever lag the dataset refreshes at. And listed skills are cumulative across a career, not scoped to the current job, so a skill count tells you who has ever claimed a skill, not who uses it today.

Coverage is also uneven. Technology and professional services staff are indexed more completely than workers in sectors where profiles are rare, so a comparison across industries partly measures visibility. Ratios within one company or one market are more robust than absolute counts across them.

A planning team does not need a new platform to move from yearly to quarterly. This routine works with a spreadsheet and a script.

External data is not a substitute for knowing your own organisation. If your skills inventory is out of date, fix that first, because the supply numbers have nothing to be compared against. The approach also does not suit regulated or small-scale workforces where the relevant people are not on public profiles. And when you act on individuals found this way, you are the controller for that use. Record your lawful basis and honour removal requests: a lookup that returns HTTP 451 means the person asked to be withdrawn.