For many organisations, workforce planning still starts with the question of how many people we will need, and that is an important place to begin, because headcount determines capacity and cost, and sometimes the financial envelope is the constraint we have to work within.
I think strategic workforce planning should answer two questions. What work the business will need to get done and what capability that requires, and what we should be deciding now because of it.
When workforce planning moves beyond forecasting jobs and employee numbers towards thinking about work, capability, different sources of talent and technology, it becomes better at translating business strategy into choices about the future workforce, and without that it tends to project the present forward.
The missing step
There is often a missing step between business strategy and workforce numbers. If the strategy changes, the work may change too, and technology may remove parts of a process while creating new work around judgement and oversight.
So before asking how many people we need, it is worth asking:
- What work will need to be done?
- What should stop or move elsewhere?
- Where could technology help?
- Where will human judgement or expertise become more important?
Only then does it make sense to translate that into roles, skills, capacity and cost.
This is particularly relevant with AI, where I would be cautious about taking the percentage of a role that could theoretically be automated and converting that directly into a workforce reduction. Time released by AI may be absorbed by new work, better service, growth or redeployment. The job itself may need to be redesigned before we know what the workforce implication is. That makes workforce planning harder, but it also makes it more useful.
The output should be decisions
A workforce forecast can be analytically impressive and still have little impact. The more useful test is whether it informs a decision, so it is helpful to ask:
- Do we need to start developing a capability internally because it will take several years to build?
- Should we recruit externally because speed matters more?
- Is there work we should redesign before hiring more people?
- Do we need stronger succession around a small group of roles where losing expertise would create real business risk?
- Should we wait before making an irreversible workforce decision because one of the assumptions is still too uncertain?
The research makes a useful distinction between forecasting and planning. Forecasting describes what the workforce might look like under a set of assumptions, while planning is what management decides to do with that information. That is where strategic workforce planning connects to business strategy, by influencing hiring, development, organisation design, technology investment and the choices Finance and business leaders make about where to put resources. If it sits in HR as a workforce spreadsheet after those decisions have already been made, it is probably happening too late.
Where getting it wrong matters
I do not think every part of an organisation needs the same depth of workforce planning. For stable work, where skills are readily available and demand is predictable, normal capacity planning may be enough. The deeper work is more valuable where the business has less room to be wrong. That might be a capability that takes years to develop, a small number of technical experts with significant institutional knowledge, a leadership pipeline that is needed to support growth, a part of the workforce exposed to technology change or a skill set the external market cannot supply quickly enough.
One point from the research that stays with me is the importance of lead time. A gap does not have to be large today to be strategically important. If a capability will be needed in three years and takes four years to develop, the issue is already with us. I have come to think of it as time-to-need versus time-to-close. It is also one reason succession planning and workforce planning belong together, because the value comes from seeing the risk early enough to have choices.
Planning for uncertainty
The further out we look, the less certainty we have. AI is probably the clearest current example. We can see that work will change, but in many organisations we do not yet know how quickly it will happen. Scenario planning can help, because the aim is to understand which assumptions matter most and which decisions make sense across most plausible futures. Some investments can start early because they are useful under several scenarios. Other decisions can remain open until there is stronger evidence or a clear trigger to act.
There is a temptation to respond to uncertainty by either predicting too confidently or waiting until we know more. Good workforce planning gives us something in between, as it helps the business understand where it needs to act early and where it can afford to wait.
Starting with the business
Strategic workforce planning should start with the same question as any good people strategy. Where is the business trying to go?
From there we can ask what work needs to happen, which capabilities matter most, where the workforce risks sit and what will take time to build. The answer will vary across businesses, and often across parts of the same organisation.
That is why I would hesitate to treat strategic workforce planning as a large enterprise-wide modelling exercise. The most useful process may be much more focused: take a material business challenge, understand the work and capability implications, test the risks and make the decisions early enough for them to matter, with the effort going where the decision has real business consequence.
Headcount still matters, but if the most interesting thing workforce planning gives us is a number, we have probably stopped before the useful part.