Most People functions, when they think about AI, think about tools. The next layer up thinks about workflows. The layer above that — the one almost nobody is at yet — thinks about org design. Not which AI do we buy, but what does the team look like when AI is infrastructure rather than a side project?
That is the shift this piece is about. It is the conversation a CPO needs to have once and then act on, because once AI is genuinely embedded, the old shape of the team stops fitting.
Three maturity levels, plainly
There are roughly three states a People function can be in. They are not stages on a roadmap — some teams skip — but they describe meaningfully different operating modes.
AI-Enabled. Individuals on the team use AI tools to be faster at their existing work. The org chart is unchanged. The capability lives in a few enthusiasts. When they leave, it leaves with them. Most People functions are here, whether they say so or not.
AI-Augmented. The team has shared workspaces, a few real automations, and named champions building things. The work has shifted: less drafting, more reviewing; less reporting, more interpreting. The org chart is mostly the same, but the time allocation inside roles has changed. A People Partner spends less time wrangling documents and more time on the conversations the documents enable.
AI-Native. The function has been redesigned around the new ratios. There are roles that did not exist three years ago. There are fewer of some roles that used to dominate. The leverage is structural, not heroic. New joiners learn to work this way from week one.
The question is not which one is "best." It is: which one matches the leverage you actually need? A 60-person company can run a great AI-Enabled team. A 600-person company that stays AI-Enabled is leaving an obscene amount on the table.
What changes inside roles before titles change
Before the org chart moves, the content of existing roles starts to shift. This is where most teams notice the change first.
A People Partner in an AI-Native team spends very little time writing comms, summarising survey data, or chasing managers for performance inputs. The system does the drafting and the chasing. They spend much more time on the high-context, judgment-heavy work that AI cannot do alone — calibration conversations, leader coaching, navigating ambiguous ER situations, designing interventions for specific teams.
A Talent Partner spends almost no time on initial CV review, scheduling, or rejection messages. The pipeline tooling does that. They spend much more time on assessment design, interviewer calibration, and the human side of closing senior hires.
A People Operations specialist is no longer the person who runs reports and reconciles spreadsheets. They are the person who owns the systems that produce the reports — the workflows, the integrations, the data quality. The work has moved up the stack from "generates outputs" to "operates the machine that generates outputs."
If you look at your team and these shifts have not started, you are not yet AI-Augmented, regardless of which tools you have bought.
The new roles that actually appear
Once the function tips into AI-Native, three roles tend to emerge. They do not always have these titles, but the work is unmistakable.
The People Systems Lead. Owns the workflow architecture across the function. Decides which work gets automated, in what order, with what guardrails. Holds the integrations between the HRIS, the ATS, the LMS, the survey tool, and the AI layer that ties them together. Reports to the Head of People Ops or, increasingly, directly to the CPO. This person used to be called a "People Ops Manager" but the job is genuinely different: less coordination, more design.
The People AI Champion(s). Three or four people, distributed across the team, who build things. Not a separate function. A practice woven through the existing one — a People Partner who builds, a Talent Partner who builds, an Ops specialist who builds. Twenty per cent of their week, protected. They are the difference between a team that uses AI and a team that makes things with it. (More on the model in the champion piece.)
The People Data Lead. Not a new role in title — analytics has existed in big functions for years — but the shape changes. Less time on dashboard maintenance, more time on signal design: deciding what to measure, what counts as a real shift, what to surface to whom. AI does the heavy lifting on the queries and the visualisations; the human work is in framing the questions and interpreting the answers.
Three roles. Maybe five FTE depending on your size. They do not replace your existing structure. They sit inside it and change what it is capable of.
What gets smaller
This is the part most CPOs find harder to say aloud, so we will say it. In an AI-Native People function, some categories of work shrink dramatically. That has implications.
The pure coordination layer shrinks. Scheduling, status-chasing, document-prep work that used to occupy a meaningful slice of a People Coordinator's week largely goes away. The role does not disappear — there is still real work in joining a team, in sensing how it is doing, in being the human face of the function — but the shape of it changes from administrator to relationship-builder.
The first-line content production shrinks. Internal comms drafts, FAQ answers, policy explanations, training material first drafts — the volume of human time going into these drops by an order of magnitude. The remaining human work is editorial: judgment, voice, knowing what not to send.
The reporting cottage industry shrinks. The weekly headcount slide, the monthly attrition deck, the quarterly DEI cut — these stop being human-assembled artefacts and become outputs of the system. Humans curate and interpret rather than build.
What this means in practice is that some teams will get smaller. Others will keep the same headcount but spend it on entirely different work. Either way, the conversation needs to be honest. Pretending nothing changes is the fastest route to a team that resents AI rather than uses it.
Ratios that actually shift
A useful diagnostic: count what your People function spends its time on, in rough percentages. Then ask what those percentages look like in an AI-Native version of itself.
A common starting profile in a 250-person scale-up:
- 35% transactional / coordination work
- 25% drafting and content production
- 15% reporting and analytics
- 15% partnering and judgment work (the work humans uniquely do)
- 10% strategy, design, and leadership
The AI-Native version of the same function tends toward something like:
- 10% transactional / coordination
- 5% drafting (mostly editorial review)
- 10% reporting (mostly interpretation)
- 50% partnering and judgment
- 25% strategy, design, and leadership
That is not a productivity uplift. That is a different job. The team is doing more of what people came into People to do — judgment, relationships, design — and less of what nobody enjoyed in the first place.
If the ratios in your head do not look something like this when you imagine three years out, you are still designing an AI-Enabled function and calling it transformed.
The CPO's actual job in this transition
Three things, in order, none of them about tools.
Decide the destination. Pick AI-Augmented or AI-Native explicitly, with a date. Most companies should aim for AI-Augmented in twelve months and AI-Native in twenty-four to thirty-six. Skipping the augmented stage rarely works — the team needs the muscle memory before the redesign sticks.
Protect the builders. Champions need cover. The People Systems Lead needs authority. The work of redesign is constantly under pressure from "real" work. The CPO is the only person senior enough to hold the line.
Be honest about the shape. When the ratios shift, when some roles shrink and others appear, the team needs to hear it from the CPO before they hear it from a leak or an org chart redesign deck. The teams that handle this well treat it as a multi-quarter change conversation, not a memo.
What this is not
It is not a justification for cutting headcount as the first move. Teams that lead with that get the worst possible outcome — fear, hoarding of work, no actual capability building, and eventually the same headcount because the systems were never built. The leverage comes from doing the redesign well, not from doing the redundancies first.
It is not a one-off project. The shape of an AI-Native People function will keep moving for years as the underlying tooling shifts. The point is to build a team that can keep redesigning itself, not to land on a final org chart.
And it is not optional. Within three to five years, the gap between an AI-Native People function and an AI-Enabled one will be the difference between a function the CEO leans on and one the CEO works around. The companies that have started already know this. The ones that have not are about to find out.
The work begins with one decision: what does our team actually look like, designed from scratch, knowing what we now know? Answer that honestly and the rest is execution.
What this connects to
Auto-recommended next reads in the People Ops cluster, ranked by shared concepts and headings:
- A workflow assessment framework for People Ops
- People debt: what GenAI exposes, and what to do about it
- AI workspace setup for People teams (Claude, ChatGPT, Copilot)
- AI governance for People teams
If this resonated, there's more.
Subscribe to receive new Intelligence pieces as they're published. No noise — just the work.
By subscribing you agree to our Privacy Policy. Unsubscribe any time.
