Diagnosing AI readiness in People Ops

A Head of People I sat with last year had already bought the tools. Two licences, a pilot underway, and a request: help us roll this out. We spent the morning walking the team's actual week instead. AI readiness in People Ops is not a model problem, and it is almost never a tooling problem. It is a question of whether the data, the processes, the people and the sponsor can absorb what you are about to build. Hers could not, not yet. So we parked the rollout and read the function first.

That order matters more than any tool choice. Read first. Build second. Every time.

Why AI readiness is not a model problem

The model is the part that already works. Whatever you are trying to do inside the People function, drafting, summarising, screening, answering the same policy question for the fortieth time, a frontier model can almost certainly do the task in isolation. That is the wrong test. AI readiness in People Ops is the answer to a harder question: can the organisation around the model absorb what happens when you point it at real work?

Readiness is the gap between "the model can do this task" and "our function can run this workflow, on Monday-morning data, without a person quietly holding it together." Diagnosing readiness is measuring that gap before you spend on closing it.

That gap has almost nothing to do with which model you licence and almost everything to do with the state of the function underneath it. The five pillars of AI readiness cover the surfaces at company scale. What follows is the People-specific version: the read I actually run before letting a team build.

Two axes before six

Before the six-axis diagnostic, run a faster read. Score the team on two axes, 0 to 10, and then ignore the numbers.

Tooling. What can your team physically do with AI today? At zero, they have heard of ChatGPT. At three, they paste in context and use Custom GPTs. At five, they are building light automations in n8n, Zapier or Make. At seven, they can debug API calls and stand up a self-updating dashboard. At nine, they are deploying small internal agents wired into your stack. At ten, they probably should not be in HR any more.

Strategy. What is the AI actually doing inside the function? At zero, nothing. At two, low-stakes time savers like rewording job ads. At five, use is encouraged, a champion has written playbooks, KPIs are starting to attach. At seven, AI is the default in some core areas: performance, onboarding, internal comms. At nine, your People workflows are shaping how other departments work. At ten, AI is how the function delivers.

Forget the two numbers. Look at the gap between them. The mismatch is the diagnosis, and it comes in two shapes.

Tooling at six and strategy at two means the team can build but is building the wrong things: point the effort at a process that matters. Strategy at five and tooling at two means leadership has bought the story but the team cannot ship: invest in capability before you invest in more intent. Get this read wrong and you spend a quarter fixing the problem you do not have.

A financial-data business we read, roughly six hundred people, scored high on tooling and low on strategy. Engineers everywhere, automations half-built, none of them pointed at a workflow the People team actually owned. The read did one thing. It aimed the capability that already existed at the processes that mattered. Seven weeks later they had five production tools running against real volume, built by their own people, because the constraint was never the building. It was knowing what to build, and in what order. That is the entire return on reading before you buy, and it is why the two-axis mismatch is worth naming out loud before anyone opens a vendor tab.

The six axes that decide readiness

Once you know roughly where the two axes sit, the six-axis diagnostic tells you what to do about it. For a People function, six axes decide readiness. None of them is about the model. All of them are about the team and the work. The fastest way to use them is as a filter you run against your own function, out loud, in a room.

Two of the six carry more weight than the rest, and they are not the two most people watch.

Data hygiene sets the ceiling. A function with one clean source of truth can build retrieval-grounded workflows that actually work. A function with three sources cannot. Until the data is unified, AI will produce confidently wrong answers, which is worse than no answer, because someone acts on them. Fix the source before you touch the workflow.

Sponsor presence sets the survival rate. The presence of a real sponsor is the single best predictor of whether anything gets built. Better than budget, better than tooling, better than the team's raw capability. Without a named leader who will publicly say "this is how we work now," every workflow you build is the first thing dropped when a quarter gets hot. With one, the work survives the first crisis. That is what buys you a second.

What the read looks like when it is honest

The diagnostic does not produce a maturity badge. It produces six lines you could read out loud in a stand-up. A real one, lightly anonymised, reads like this:

Data: one HRIS, mostly clean. Process: TA and onboarding clear, performance murky. Tools: nine in active use, three obsolete. Curiosity: four people leaning in, two in TA, one HRBP, one Ops. Sponsor: CPO engaged, board curious. Risk: cautious culture, EU AI Act exposure.

From that, the build order writes itself. Start with TA workflows where the data is good and the process is clear. Use the four curious people as your first champions, which is exactly how the champion model gets its footing. Stand up governance early, because the risk posture demands it. Leave performance for phase two, after the process gets mapped. This read is the entry point to the wider AI workspace for People Ops: get the diagnosis right and every build after it has somewhere to land.

That is the whole trick. The diagnostic does not grade the team. It makes the next three moves obvious.

Where People sits against the rest of the business

A useful side effect of the read: it lets you place People against the rest of the company. Most businesses have wildly uneven AI capability across functions. Engineering adaptive, Marketing capable, People unacceptable. If you do not know where you sit relative to your peers inside the business, you will either over-promise in the board meeting or get out-flanked in the budget one.

A simple frame, borrowed from capability maturity work in adjacent fields, gives you the vocabulary and, more usefully, the right next step for each level.

You do not need every function at transformative. You need to know where each one is, and to set the right next step for each, this quarter. For the cross-function vocabulary that maps this ladder onto the named industry models, see AI maturity frameworks for G&A leaders.

The honest part is that most functions score lower than their leaders think.

The cost of skipping the read

Skipping the diagnostic feels like speed. It is the most expensive form of slow. Every workflow you build without reading the function first carries a quiet bet: that the data is good enough, that the process is clear enough, that the team will adopt, that a sponsor will hold the line. Most of those bets lose, and they lose in month four, when the budget and the attention have both moved on.

Read first, and the building is faster afterwards, every time. In almost every engagement, the first concrete build is setting up the team's AI workspace, so the workflows that follow have somewhere to live. Everything after that is a question of order, and the read gives you the order.

If you want to run the read on your own function before you spend a penny on tooling, the Readiness Assessment is the sixteen-question version of this diagnostic, scored across four capability layers in about ten minutes. Grading the team was never the point. Knowing what to build next always was.