Workforce Planning for Next Year's Strategy — Start From the Bets, Not the Headcount

Most workforce plans we are shown are not plans. They are last year's headcount, adjusted for attrition, plus the sum of what every department asked for. That is a budget, and a perfectly reasonable one, but it answers the question "how many people will each team have?" when the question that matters is "what will this company need to be able to do next year that it cannot do today?" A workforce plan that starts from the strategy's bets finds different gaps from one that starts from department requests, and usually much more important ones.

We see this most clearly when the strategy changes direction. A company that intends to keep doing what it already does can plan from headcount without much harm. A company placing new bets, such as a new channel, a new market or a new kind of customer, cannot, because the capabilities those bets need are almost never the ones its managers think to ask for.

"The plan was fine. It was for a different strategy"

A retail group in Saudi Arabia set its strategy for the year around one central bet: moving from a store-led business to an omnichannel one, with e-commerce expected to carry a meaningful share of growth. The workforce plan went through the usual process. Each department submitted requests, HR consolidated them, finance trimmed them. The final plan added store staff for new locations and a handful of IT roles.

The launch slipped in the second quarter, and the reasons were all capabilities nobody had requested. There was no one who could run performance marketing at the scale online sales needed, no one who had negotiated last-mile delivery partnerships, and no one responsible for the product data that an online catalogue lives or dies on. None of these was a department's gap, so none of them appeared in a departmental request. The chief strategy officer summed it up in the review: "The workforce plan was fine. It was a good plan for a different strategy."

The Bet-to-Capability Map

We use a four-step map with leadership teams to connect the strategy to the workforce plan. It works best when it is done in the same room and the same month as the strategy itself.

1. Bets. List next year's three to five strategic bets, the ones the year will be judged on. If the list runs to fifteen, that is a strategy problem to solve first, and our piece on why strategy execution fails explains why.

2. Capabilities. For each bet, name the few capabilities it cannot succeed without, written as things the organization must be able to do rather than as job titles. "Acquire customers profitably online" is a capability; "digital marketing manager" is one possible way of getting it.

3. Coverage. Rate how well the organization covers each capability today on a simple scale: none, thin, resting on one person, or solid. The third rating deserves special attention, because a capability that lives in a single person is a capability you can lose in a month, which is the risk our piece on succession planning deals with.

4. Route. For every gap, choose how to close it, by comparing how long each route takes with when the bet needs the capability.

Only after the routes are chosen does headcount come in, and at that point it follows from the strategy instead of preceding it.

Here's the contrarian part

Workforce planning is normally treated as the step after strategy, a way of resourcing decisions already made. Sometimes its most valuable output is a change to the strategy. If a bet depends on a capability that cannot be built, bought or borrowed in time, the honest conclusion is that the bet is mistimed, and it is far cheaper to learn that in a planning meeting than in a second-quarter review. The Ansoff matrix makes the same point from the strategy side: every growth move asks the company to become something it is not yet, and the size of that distance is a capability question.

The second point is about skills catalogues. Many companies respond to this problem with a skills inventory, a large database of what each employee can do. It is useful, but it measures the wrong unit. Capabilities belong to organizations, not to people. A company can employ several skilled data analysts and still have no analytics capability if nobody owns the decisions their analysis is meant to inform, or if the analysts sit in a structure where nobody asks them anything. Closing a capability gap usually means changing structure and decision rights as well as adding skills.

Why it works

The distinction between individual skills and organizational capabilities is well established. Prahalad and Hamel's work on core competence in the early 1990s described competences as the collective learning of an organization, not the talents of individuals. Ulrich and Smallwood made the practical version of the argument in Capitalizing on Capabilities, describing capabilities such as speed, collaboration and customer connectivity as things an organization is known for and can do reliably, separate from any individual's skill.

Peter Cappelli's Talent on Demand supplied the planning logic. His argument was that traditional workforce planning failed because it tried to forecast years ahead in an uncertain world, and that companies should manage talent more like a supply chain: balancing making and buying, planning for uncertainty, and matching the timing of supply to the timing of demand. The Bet-to-Capability Map applies that idea at the level of strategic bets, which is where the uncertainty is concentrated.

It also connects to the broader argument we make about talent. A plan built from bets treats people as a strategic system rather than as a cost line, which is the case we make in people strategy is a business model and in our view of talent management as a loop rather than a pipeline.

A practical checklist

• Hold workforce planning in the same cycle as strategy, before the budget is fixed.
• Limit the input to three to five bets, and refuse to plan capabilities for anything that is not one of them.
• Write capabilities as verbs, as things the organization must be able to do, before anyone mentions a job title.
• Mark every capability that rests on one person and treat it as a gap, even if it is covered today.
• Choose a route for every gap by comparing time-to-capability with the date the bet needs it.
• Change structure and decision rights alongside hiring, so that bought or built skills have somewhere to become a capability.
• Revisit the map at the mid-year review, because bets change and gaps move with them.

Ask yourself

• If we removed every departmental request from our workforce plan, which strategic bet would be left without the capability it needs?
• Which of next year's bets depends on something nobody in the company has done before?
• Which of our critical capabilities would disappear if one person resigned?
• For our biggest gap, does the route we have chosen deliver the capability before the bet needs it?
• Is there a bet we should delay because the capability cannot arrive in time?

The takeaway

A workforce plan built from headcount will resource the company you already are. One built from next year's bets finds the capabilities the strategy actually depends on, rates how thin they are, and chooses deliberately between building, buying, borrowing and rethinking the bet. Start from the bets, write capabilities as things the organization must be able to do, and let headcount follow. Measured against OKRs a year later, that is the difference between a plan and a budget.