CHROs don’t need convincing that artificial intelligence has reshaped their job. The evidence of that conviction is already in: ninety-one out of a hundred CHROs now rank AI as their single greatest concern, well ahead of engagement, culture, or anything else competing for a place on the list.
Gartner’s own research backs this up, ranking “HR Tech and AI Strategy” as the second-highest CHRO priority heading into next year.
What’s missing isn’t awareness. It’s a plan for what to actually do with it.
Most companies still talk about AI the way they’d talk about any other piece of software: which platform to buy, which team gets trained first, how the rollout gets sequenced. That instinct, understandable as it is, asks the wrong question.
The more useful starting point for HR is not “How will AI affect our people?”
It’s “What work will exist here eighteen months from now, and what people will that work require?”
AI is already shaping who gets hired, who gets promoted, who gets quietly flagged as underperforming, and who gets let go. This often happens well before HR even learns that a manager has started leaning on it. HR doesn’t get to opt out of those consequences simply because HR didn’t choose the tool.
So the real question heading into 2027 planning isn’t whether to adopt AI. It’s whether your job descriptions, your skill maps, and your assumptions about how work actually gets done have kept pace with how AI is already changing that work underneath you.
For most organizations, if we’re honest, the answer is no. This is not because anyone was careless, but because roles evolve faster than the paperwork that describes them.
Plan the work before you plan the workforce
Underneath this sits a second tension that makes the first one harder to solve cleanly. Companies are trying to do two things at once right now: keep growing, and get leaner.
Workforce planning is where that tension actually gets resolved, one role at a time, whether anyone names it that way or not.
But headcount is often too blunt a place to start.
Before deciding how many people the organization needs, leaders need to understand what is happening to the work itself. What work is disappearing? What work is becoming easier? What new work is being created? And what work becomes considerably more valuable when AI can handle everything surrounding it?
A position that made complete sense under last year’s headcount plan may no longer make sense at all inside this year’s AI-shaped version of the business. Before asking who should fill a role, it’s worth asking honestly whether the role, as written, still needs to exist in its current form.
We see this pattern constantly from the search side of the table. When a client asks us to backfill a role, the first thing we do, through our Role Visioning process, is challenge whether the old job description actually survived the last eighteen months of change inside that company.
More often than not, it hasn’t. The title stayed the same while the substance underneath it quietly moved on.
Three habits are worth building into the next planning cycle, and none of them require a bigger budget, only a sharper question:
- Which work has AI eliminated, changed, created, or made more valuable? Start there before translating the answer into roles or headcount.
- Which roles on your org chart are still being planned as though it were last year, even though the day-to-day work behind them has visibly shifted?
- Where has “efficiency” become a convenient stand-in for genuine redesign? This is often a headcount number trimmed without anyone reconsidering what the remaining roles are actually being asked to accomplish.
None of this will make the tension between growth, AI, and efficiency disappear; that tension is likely to be a permanent feature of the next several years, not a problem to be solved once and filed away.
What it can do is change the sequence of the conversation.
Instead of starting with how many people the company can afford and working backward, start with the work the business will actually need done. Then determine the roles, capabilities, and people required to do it.
For CHROs, that may be the more useful definition of AI workforce planning: plan the work first, then plan the workforce around it.
