Leading the AI transformation in People

A board member leans across the table at the offsite and asks the CPO the question directly: "What is our AI plan for People, and how much headcount does it take out?" It is the wrong question, but it is the one that gets asked, and the answer you give in that room sets up everything that follows.

Here is the honest answer. Leading the AI transformation in People is a change problem wearing a technology costume. The tools work. The workflows are sound. The capability can be built. What breaks, almost every time, is the human side: a fear nobody named, a sequence that asked too much too soon, a leader who confused announcing the change with running it. So the answer to the headcount question is not a number. It is a sequence, run in order, at a pace the team can sustain on a Tuesday morning.

Start by naming the fear the team already has

The most common opening mistake is treating AI as a pure productivity story. "This frees us up to do more strategic work." The team hears that sentence and the next private thought is: or to do the same work with fewer of us. They are not wrong to think it, and a leader who pretends the thought is not in the room has already lost the first battle of the change.

The leaders who get the next twelve months right open differently. They put the fear on the table before anyone else has to. Something close to this, said with the lights on and no slide behind it:

I want to be straight with you. AI is going to change what this team does. Some of the work we do now will be done by systems within a year or two. Some roles will look meaningfully different. I do not have a complete map. What I can tell you is that we build this together, the team grows capability faster than the work shrinks, and nobody here is surprised by a change to their own role. We talk about it openly as we go.

That paragraph does more for adoption than any tool rollout. It lets the team have the real conversation instead of working out, in private, what management is "really" planning. And the fear is not only theirs. CPOs who pretend they have it figured out lose credibility inside a quarter. The teams that stay most engaged are the ones whose leader said early, I am learning this in public, same as you.

There is a hard line running through this, and it is the difference between leading the change and merely announcing it.

The sequence that works, run in order

Nothing about the sequence is novel. It is the same shape as any serious change. It just has to be done properly and in order, and most functions skip a phase and pay for it two phases later.

Phase 1 is the one everyone wants to skip, and skipping it produces the most expensive failures. A leader who cannot describe what they have personally built with AI has no standing to lead this change, and the team can smell the gap in the first town hall. Phase 2 exists because proof beats promise: one shipped workflow inside our team, with our tools, on our problems, converts more sceptics than a year of strategy decks. Skip Phase 3 and you build hero capability that dies with the first departure. That is not a hypothetical, and it is worth reading why AI pilots stall at production alongside this, because the same absorption problem sinks both.

The phases overlap. They are not crisp gates with sign-off meetings. But the order is load-bearing, and the pace is set by how fast the team can absorb, not by how ambitious the CPO is feeling in January.

The four resistance patterns, and the move for each

Resistance is information, not a problem to stamp out. Four patterns recur across every rollout, and the mistake is treating all four with the same intervention. They need different things, and reading which one you are talking to is half the job.

The Worrier row is worth sitting with. Treated as an obstacle, they become the person who kills the rollout in a governance review. Treated as a stress-tester, they hand you a stronger build, which is exactly why the governance work for People teams belongs early in the sequence and not bolted on at the end. The Worrier has already written half your policy in the form of questions.

What actually stops the transformation

A short list, in rough order of frequency. None of it is exotic. All of it is boring, and boring is what kills change programmes.

No protected time. Champions are expected to do the new work on top of a full existing load. Within six weeks the new work evaporates, because it always loses to the thing with a deadline. Twenty per cent of the week, written down, defended by the CPO when budgets get squeezed, or it does not happen. This is the failure I see most, and it is entirely a leadership choice, not a resourcing accident.

Tool-shopping instead of building. Months spent evaluating platforms are months not spent building with the platform you already have. Pick something good enough and start. The cost of the wrong tool is small and reversible: a workflow automation seat on something like n8n runs around £20 per builder per month, it is SOC 2 and ISO 27001 compliant, and you can self-host it if procurement gets nervous. The cost of a year of evaluation is a year. Switch later if you must.

Communication that outpaces reality. Announcing an "AI-first People function" before anyone has shipped anything teaches the team that the words and the work are not connected, and they stop trusting both. Build first, talk after. The story you tell in Phase 2 is only worth telling because it is true.

Delegating the change itself. "I have asked Sarah to lead our AI work." Sarah, however capable, cannot redesign roles, protect time across the function, or hold the line when the CFO comes for the budget. Those are the CPO's powers, and they are exactly the powers the transformation needs. Lead it personally with Sarah as a partner, never as a proxy.

Framing it as a project with an end date. AI in the People function is not a programme that finishes in Q3. It is the new shape of the work. Anything framed as having a finish line stops getting attention the moment the next shiny thing arrives.

Before you sign off on a function-wide rollout, it is worth running your own leadership through a short filter. If any answer is a wish rather than a design, the rollout is not ready.

What to measure, and what to ignore

Resist the urge to measure usage. Number of prompts, number of active users, hours of training delivered: these are vanity numbers. They tell you who is busy, not who is faster because of the work. A team can log a thousand prompts a week and have redesigned nothing.

Three things are worth measuring, and all of them lean qualitative. Workflow count and depth: how many workflows does the team run end to end on AI infrastructure today, and how many survived their original builder leaving? That second half is the real adoption number, because it separates capability that lives in the system from capability that lives in one person's head. Time reallocation: has the share of time spent on coordination and drafting actually fallen, and has the share spent on judgement and partnering actually risen? If the time profile has not moved after twelve months, the transformation has not happened, however many tools got bought. Confidence: ask the team twice a year whether they could teach a new joiner how this team uses AI. The shift from "no, but" to "yes, and" is the signal.

The board wants a return number, and that is a fair ask: give them the value piece for measuring AI in People Ops rather than a usage dashboard. But the truest measure I know is quieter than any of these. On one engagement, two months after the build, the champions had shipped five more agents we never scoped, workflows the team invented because it finally could. That is the test. Not what ships while you are in the room, but what the team ships after you leave. The whole arc of Read, Craft, Scale is built to produce exactly that outcome, and the champions and the shared AI workspace for People Ops are what make it survive.

The hardest part of leading the AI transformation

The hardest part of leading this transformation is not the launch. It is staying with it when the headlines move on. AI is the loudest topic in every leadership conversation right now, and in eighteen months it will be background noise, replaced by whatever is next. The leaders who keep building through that quiet stretch are the ones whose teams end up genuinely different in shape. The ones who treated it as a campaign find their work quietly undone inside a year, the manual processes creeping back in one exception at a time.

This is the same lesson as every deep change in operating practice, which is why the redesign of the AI-native People team sits at the end of the sequence and not the start: you earn the right to change the shape by first proving the work. The headlines fade. The grain of how the team actually works remains. Lead with that in mind from day one, and the transformation has a real chance of becoming the new shape of the function rather than a chapter in a strategy deck nobody opens any more.