Strategic Workforce Planning: why mapping skills is no longer enough

There is something paradoxical about the situation organisations currently find themselves in.

Never before have they had so many resources at their disposal to gain insight. To know who possesses which skills. To know where the gaps lie. To know which capabilities are threatened by obsolescence or automation. To know what is missing to drive transformation.

Solutions are multiplying. HR software providers promise dynamic skill maps, updated in real time and enhanced by AI. Skills repositories are becoming intelligent. Systems automatically detect skills in CVs, training courses completed and projects led. We can visualise, cross-reference and anticipate.

And yet.

When it comes to making decisions – recruit or train? focus on one role or another? invest heavily or test gradually? – organisations often find themselves in the same deadlock as before. Perhaps even with a stronger sense of helplessness, because they feel they have done the groundwork.

They have mapped things out. They have measured. They have dashboards. And yet, they still don’t really know what to do.

Visibility does not lead to a decision

What is at stake here is a disconnect between two promises that do not align.

The promise of the tools is visibility. Making visible what was unclear, objectifying what was intuitive, transforming the informal into actionable data. And in this respect, real progress has been made. It has become technically possible to map an organisation’s skills with a level of detail and speed that would have been unthinkable ten years ago.

But visibility does not automatically lead to clarity in decision-making.

Knowing that the organisation is short of 47 data scientists does not tell us whether to recruit them, train them in-house, or review the data strategy to reduce the need for them. Knowing that 30% of employees have skills threatened by AI does not tell us where to start, nor with what intensity, nor what support is required.

Mapping shows where we are. It does not tell us where to go, how to get there, or what we are willing to lose along the way.

And this is where many organisations find themselves stuck. They have invested in sophisticated tools, they have generated data, but when it comes to making decisions, they realise that the problem wasn’t really a lack of information. It was the lack of a framework to turn that information into decisions.

What Strategic Workforce Planning really changes

Strategic Workforce Planning could well be that framework. Not just another tool, not a miracle method, but a system that structures the way an organisation moves from “we know where we stand” to “we know what we’re deciding, and why”.

In practical terms, what difference does it make?

1. It forces us to connect what is usually separate

Most organisations operate in decision-making silos. Business strategy says “we’re heading in this direction”. HR maps out skills. Operations says “we need X profiles now”. Finance says “you have Y budget”.

These conversations rarely take place together, at the same time, with the same level of information.

The SWP creates a space where these approaches are brought together before decisions are made separately.

Let’s take an example:

An organisation decides to develop AI for its products. HR identifies that 40 data scientists are needed for this. Operations reports that it takes 18 months to recruit this type of profile, based on their experience in the field. Finance announces that the recruitment budget is frozen.

Without SWP, everyone manages their own part. HR launches a few recruitment drives. The strategy moves forward on paper, and 18 months later, it is discovered that only five people have been recruited and the project is stalled.

With an SWP framework, these tensions are brought to the table together, forcing a decision: should we revise our AI ambitions? Should we outsource temporarily? Should we train internally, accepting a delay? Should we reallocate budget from other priorities?

The SWP does not provide THE answer, but it forces the question to be asked at the right level, with the right people, before it is too late.

2. It makes implicit bets explicit

Organisations are constantly making assumptions about the future. “Sales roles will evolve, but not too quickly.” “We’ll always find developers on the market.” “Automation will affect production first, not support functions.”

These assumptions are not always stated explicitly. They are embedded in day-to-day decisions, in budgets, in priorities, but no one has validated them strategically, no one has checked whether they are consistent with one another.

The SWP requires these assumptions to be identified and validated – or invalidated – collectively.

Example:

An organisation decides not to invest in training its managers in AI “because it’s not their job”. Without SWP, this decision is implicit, driven by inertia, and never really debated.

With an SWP framework, the question is asked explicitly: are we betting that managers won’t need to understand AI? Or are we betting that they will learn on their own? Or are we accepting that we are taking a risk of managerial disconnect?

The SWP does not tell us which bet to make, but it shifts the bets from the implicit to the explicit, which radically changes the nature of the decision. We stop being subjected to default choices; we start to take ownership of them.

3. It distinguishes the adjustable from the irreversible

Not all HR decisions have the same timeframe: recruiting a senior expert takes 12 to 18 months, massively upskilling a workforce takes 2 to 3 years, transforming a managerial culture takes 5 to 7 years, whilst recruiting a versatile junior can be done in 3 to 6 months.

But within organisations, these decisions are often treated with the same timeframe, the same sense of urgency, and the same logic. The result: we find ourselves urgently managing transformations that should have been anticipated, and over-investing in adjustments that could have waited.

The SWP prioritises decisions according to their degree of irreversibility and the time required to correct them.

If we misjudge the need for data analysts, we can correct this within six months through recruitment or outsourcing. If we misjudge the need for managers capable of steering complex transformations, we cannot correct it within six months; we pay for it for years.

The SWP helps identify where decisions must be made now – because correction will take time – and where we can afford to make adjustments along the way. It does not require us to foresee everything; it requires us to know what we will not be able to make up for.

4. It creates a common language for discussing the future

Today, every function has its own vocabulary for discussing the future. HR talks about “skills” and “roles”. Strategy talks about “markets” and “products”. Operations talks about “headcount” and “workload”. Finance talks about “payroll” and “productivity”.

These languages do not naturally speak to one another, and decisions are often vague because we are not really talking about the same thing.

The SWP builds a shared vocabulary that links strategic ambitions, the necessary human capabilities, operational and financial constraints, and the timelines for building these capabilities.

Instead of saying “we need more resources”, the SWP forces us to say: “To achieve this business objective in two years’ time, we need X profiles with Y skills, which we can obtain through Z means, within this timeframe and at this cost.”

This shift may seem trivial, but it is not. It creates a framework for discussion where everyone is talking about the same reality, using the same variables, and where disagreements become negotiable, because they concern concrete trade-offs, not abstract visions.

5. It transforms planning into a learning process

The classic pitfall of planning: drawing up a plan, getting it approved by a committee, then discovering 18 months later that it is completely obsolete.

A well-designed SWP does not produce ONE fixed plan: it creates a mechanism for periodic review that allows us to learn from the gap between what we anticipated and what is actually happening.

Example:

We had bet on a rise in AI skills within 12 months. After 6 months, we realise it is slower than expected. The SWP creates a structured moment where we ask ourselves: why? Is it a problem of resources, teaching methods, motivation, or priorities? Do we revise the objective, the resources, or the timing?

Without this mechanism, we carry on with the initial approach until failure is inevitable. With it, we can make adjustments before the cost of the mistake becomes irreversible.

The SWP transforms planning into a cycle of organisational learning, and in an uncertain context, this ability to learn quickly from one’s decisions is often worth more than the initial quality of the plan.

The limitation we must accept

But let’s be honest. The SWP only works if the organisation accepts four things.

1. Accepting the need to decide

Firstly, and this is undoubtedly the hardest part: the organisation must accept that it has to decide. Really decide.

If there is no willingness to make the final call, no courage to take a stand, no room to say “we’re making this choice and not that one”, then the SWP becomes just another exercise. A sophisticated map that ends up in a drawer. A strategic plan that is brought out once a year in committee, before returning to the daily emergencies.

Deciding, in this context, is not about rubber-stamping a plan. It is about accepting that we cannot do everything, that some skills will be developed whilst others will not, that some roles will be transformed whilst others will be phased out, that some teams will be supported in upskilling whilst others will be redeployed.

It also means accepting that these decisions have consequences: on individual career paths, on teams and on the organisation of work. And also that we cannot always spread these consequences out over time or sugar-coat them in our discourse.

The SWP does not create this capacity to decide; it structures it, it makes it possible, but it does not replace it.

2. Accept that this is not a one-off project

Next, we must accept that SWP is not a ‘one-off’.

You do not “carry out” Strategic Workforce Planning in the same way you roll out an HRIS or run a recruitment campaign. It is not a project with a start, a deliverable and an end.

It is an iterative process, designed to be long-term with regular cycles of review, adjustment and decision-making. Because assumptions change, because the market evolves, because certain transformations take longer than expected, or because a new strategic priority reshuffles the deck.

This requires organising for regularity: dedicated time slots, governance bodies, and update rituals. Not to “redraft the plan”, but to check that the decisions taken remain relevant and to adjust them when they no longer do.

Some organisations discover this aspect as they go along. They launch a major SWP project, produce an ambitious plan… and realise six months later that they haven’t planned how to keep it alive, how to revisit it, or how to integrate it into the rhythm of management.

3. Accept that this goes beyond the scope of HR

Thirdly, we must accept that the SWP does not remain within the remit of HR.

Yes, it is often the HR department that takes the lead on the subject, structures the process and drives the initial iterations. But if the SWP remains an “HR project”, it never really takes off.

Because it affects far more than just skills management. It affects culture: how we talk about the future, how we deal with change, how we address the gaps between rhetoric and reality. It affects the organisation: who decides what, with whom, and according to what criteria. It affects financial management: how budgets are allocated between skills development, recruitment, and support for departures. It affects change management: how teams are engaged, how choices are explained, and how the legitimacy of decisions is established.

This is not a plan produced by HR for others to consult. It is a new way of managing collectively, and this requires changing ingrained habits: who calls whom, who has control over what, and who has the final say.

4. Embracing shared governance

Finally, and this is perhaps the most fundamental aspect: the SWP requires shared governance between business, finance, operations and HR.

Not a superficial form of governance, where everyone gives their opinion and HR then consolidates them, but genuine governance, where these four perspectives are brought together, make joint decisions and prioritise objectives.

Because these functions do not align spontaneously. Business wants flexibility and responsiveness. Finance wants cost control and predictability. Operations want stability and continuity. HR wants skills development and fairness in career paths.

The SWP only works if it becomes a forum where these tensions are expressed, not to resolve them magically, but to clarify them, document them, and build on accepted trade-offs.

This requires dedicated bodies. Organised opportunities for discussion. And above all, a commitment from the Executive Committee or Management Board to make the SWP a forum for strategic decision-making, not just another item on the agenda.

What this reveals

This is perhaps why the SWP is difficult to implement.

Not for technical or methodological reasons, not because of a lack of tools or skills, but because it reveals – and sometimes highlights in an uncomfortable way – the areas where the organisation is unable to make decisions. Where it prefers ambiguity to conflict, where it waits for things to sort themselves out.

The SWP acts as a litmus test. It shows where governance is unclear, where different approaches are at odds, where decisions are postponed or watered down, where trade-offs are sidestepped rather than faced up to.

And that is also why it is powerful.

Because by structuring the way questions are asked, it opens up the possibility of constructing new answers. Not perfect answers, but explicit, well-documented, shared answers.

Without these four elements, the SWP remains a fine planning exercise. With them, it becomes a lever for strategic transformation.

Deciding in the fog, not dispelling the fog

What is changing, perhaps, is the way organisations understand their own relationship with uncertainty.

For a long time, the obsession was to reduce uncertainty, to forecast better, to build more refined models, to accumulate more data. As if the problem were a lack of information.

But what we are discovering today – and ultra-sophisticated mapping tools paradoxically reveal this – is that uncertainty cannot be reduced. It must be managed. It must be integrated. We are learning to make decisions with it, not by waiting until it has been dispelled.

The organisations that fare best are not those that forecast best. They are those that know how to make decisions regardless, that have created spaces where difficult decisions can be raised, debated and resolved. They are those that have learnt to distinguish between what is irreversible and what is adjustable, and that know how to name their bets, not disguise them as certainties.

Strategic Workforce Planning could be one such space. Provided it is not turned into yet another forecasting tool, and provided we accept that its purpose is not to dispel the fog, but to learn to make decisions within it.

Perhaps the real question is not: “How can we map our skills more accurately?”

But rather: “Now that we can see more clearly, what do we decide?”

---