The People Ops AI domain map

The People Ops AI estate is not a shortlist of tools to buy. It is five domains of work, each with its own grain: talent acquisition, onboarding and lifecycle, performance and development, operations and compliance, and strategy and insight. This is the People Ops AI map, and the whole point of it is to see the estate before you build any one piece of it.

My rule of thumb is that a role is forty workflows in a coat. An eight-person People team is not eight jobs you can automate one at a time. It is closer to three hundred workflows, and no one can hold three hundred in their head while deciding where AI is worth the effort. So you zoom out. Five domains is a number you can actually reason about, and it is small enough to walk end to end in an afternoon.

Use the map as a wall. Anywhere a domain is empty in your function is a place to look. Anywhere it is crowded with half-finished pilots and overlapping licences is a place to consolidate before you add anything new.

The five domains, at a glance

Before the detail, the map in one grid. Maturity is how well-trodden the domain is, not how valuable it is. The two are often inverted: the most-explored domain is rarely the highest return.

Talent acquisition: scale the volume, protect the judgement

The most-explored domain, with the most mature patterns and the most over-claimed vendors. Talent acquisition is high-volume and high-judgement at the same time, which is exactly why AI helps and exactly why it goes wrong.

The play that pays off is clearing the top and bottom of the funnel so recruiters can spend their hours on the messy middle. A worked version: an inbound triage flow in n8n reads each application against the actual requirements list, not a generic template, tags it, and drops it into a ranked queue. The recruiter opens a queue, not an inbox of two hundred. The model never rejects anyone. It orders the pile and shows its reasoning, and a person makes every call. n8n runs about £20 per builder seat per month, is SOC 2 and ISO 27001 compliant, and can be self-hosted if the data cannot leave your estate.

Where it disappoints: end-to-end "AI sourcer" tools that promise to find candidates on their own, chatbots that replace a human touchpoint with a candidate, and anything claiming to predict performance from a CV. The grain here is that AI scales the volume work and protects the judgement work, but only if the team holds the line. The moment it starts making the hire, you have crossed from useful into liability.

Onboarding and lifecycle: keep the templates alive

Less explored, often higher return. The first month of someone's tenure is where the most can be improved with the least friction, because the work already runs on clear handoffs and templates. The templates just go stale and get skipped when a coordinator is busy.

AI's job is to keep them alive. First-week sequencing that nudges the right person at the right moment. Manager prompts for new-joiner check-ins, grounded on role, level and start date. A personalised learning path drafted from real context rather than a one-size PDF. Offboarding handover packs assembled from where the leaver's work actually lives, so the knowledge does not walk out with them. Most of this is a scheduled flow plus a Notion workspace, not a product you buy.

Where it disappoints: "AI buddy" chatbots that try to replace human connection in week one, and anything that automates a moment where the new joiner needed an actual person. The bar for adoption is low here because the alternative is usually "a coordinator forgot", but the failure mode is automating the warmth out of the one month that sets the tone for everything after.

Performance and development: the hardest call to get right

The hardest domain, because the consequence of a wrong call is the highest and the data is the messiest. This is where I see the most tempting and most damaging over-reach.

AI earns its place in preparation. Pre-read assembly for review cycles. Calibration preparation that surfaces where managers are using wildly different language for the same performance, before people are in the room arguing. Self-reflection scaffolding for employees writing their own reviews, grounded on prior conversation themes rather than a blank box. Learning recommendations tied to real project history. All of it prepares the table.

Where it disappoints, and where careers get damaged: anything that scores or rates a person directly, "AI coach" tools that stand in for a manager conversation, and bias-detection that produces a number instead of a conversation. The grain is that performance is a judgement domain. The model prepares what humans then decide. Teams that respect that line make their cycles better. Teams that cross it produce performance theatre the company eventually rejects, and they lose the trust that made the tools usable in the first place.

Operations and compliance: the quiet highest-return domain

Quietly the highest-return domain, and the most under-invested. It is high-volume, low-creativity and high-correctness, which is the profile AI handles best, and the profile People teams keep skipping in favour of shinier work.

The shape that fits is "draft, log, present for approval, never commit". Policy questions answered against the actual handbook through retrieval, so the answer is grounded and traceable rather than invented. Letters, contracts and references drafted with a human review step that is never optional. Reconciliation across HRIS, payroll and finance. Audit-trail assembly. Regulatory horizon-scanning summarised for a person to act on. Done well, this is the domain where a team gets back the most hours per week per build.

Those numbers came from one defence tech engagement, and they came from operations and compliance work, not from a clever recruiting tool. Where it disappoints: anything that signs, files or commits without a human step, generated legal advice, and anything that touches data the model was never meant to see. Correctness is the whole game here, so the review step is the feature, not the friction.

Strategy and insight: ground it or don't build it

The most talked about and the least built, which is reasonable, because the data-quality bar is highest here and the failure is the quietest.

AI genuinely helps with synthesis. Survey responses summarised at scale. Themes pulled from open-text feedback. Meeting notes turned into something a People exec sync can act on. Patterns surfaced across exit interviews. Rich qualitative data shaped into something that can inform a quantitative decision. The discipline that makes all of it useful is grounding every output in retrievable source: the quote, the transcript, the individual response. When we build extraction here, it is model-only, never a regex fallback, because a regex pattern will confidently produce garbage and call it a finding.

Where it disappoints: "AI dashboards" that predict attrition or engagement from thin data, insight the team cannot trace back to source, and anything claiming to have found a pattern nobody had already half-noticed. Insight is where AI hallucinates most confidently. Treat its output as a draft for a human to verify, never as truth, and it becomes one of the most useful things in the estate.

The pattern that repeats in every domain

Walk all five domains and the same line runs through them. The AI shape that works is the same everywhere, whatever the workflow. So is the shape that fails.

This is why the map matters more than any single build. If you know the winning shape, you can apply it in a domain you have never touched and be roughly right on the first attempt. The domains differ in their data and their stakes. The shape does not.

How to read the People Ops AI map

Three moves, in order. This is the part you can run on Monday, and the part most teams skip because building one thing feels more productive than choosing the right thing.

Before you commit a domain to that first quarter, run it through a filter. This is the same test I use on any workflow: does it survive first contact with reality, or was it wished into existence.

The other half of reading the map is spotting the crowded domains, the ones already full of overlapping tools nobody has questioned. Consolidation there usually beats a new build anywhere else.

To score the individual workflows inside your chosen domain, the workflow assessment framework gives you the rubric. To see task-level exposure across the whole estate at a glance, run the AI Exposure Map. And whichever domain you pick, every build in it sits on the same base: the team's AI workspace, and underneath that, an AI operating system shaped to People rather than bolted on from a vendor. The patterns that pay off repeat across the domains once you have the base right.

The function that has built across all five domains in eighteen months looks unrecognisable. The function that tried to build across all five at once looks unchanged. Same map. Different sequencing. That is the only difference that matters.