The People Ops diagnostic toolkit

Five diagnostics, three weeks, run off data you already own: that is the whole People Ops diagnostic toolkit, and it costs a fraction of the consulting audit most leaders reach for instead. You run it on a People function before you change anything. An underperformance early warning, a People-as-a-product structural read, a workflow heatmap, an AI readiness read, and a 90-day roadmap. Four of them tell you where you are. One sequences the fixes. The point is not any single artefact. It is the reconciliation between them, because the function looks different from every angle and the truth usually sits in the disagreement.

Why five diagnostics beat one audit

A single audit produces a single answer, usually the answer the auditor walked in holding. You hire someone to look at retention, they find a retention problem. You ask why onboarding is slow, you get an onboarding project. The shape of the question decides the shape of the finding, and the finding is rarely the thing that was actually costing you.

Five diagnostics force the function through five different lenses and make you reconcile what you see. The early warning shows you motion: what is slipping this week. The product checklist shows you structure: what has an owner and what is orphaned. The heatmap shows you where the manual cost lives. The readiness read shows you whether you could even fix it with AI if you wanted to. The roadmap shows you the order. When two lenses agree, you have a fact. When they disagree, you have found the thing worth looking at.

Most People leaders inherit a function shaped by whoever ran it last, sized for a company that no longer exists, and measured by numbers nobody asked for. The first job is not to fix it. The first job is to read it. This is where the read pays for itself, in cash, not in insight.

That number was not hiding. It sat in the finance system in plain sight for years. What was missing was a read that put the workflow, its manual cost, and its licence bill on the same page at the same time. A single audit into "our HR software stack" would have benchmarked the licences and renewed them. The toolkit asked a different question of the same facts, and the answer was worth forty thousand pounds a year. Here is what separates a function that has been read from one still running on inheritance.

The underperformance early warning

This is the only diagnostic on the list that runs every week, and the only one that costs five minutes. It is a read of five signals across the function, taken every Friday, in the same order, so you are comparing this week against last week rather than judging each signal cold.

• Missed 1-1s. Cancellations without a reschedule inside seven days. A manager who keeps dropping their team's 1-1s is telling you something before the engagement survey does.
• Slipping commitments. Tickets, hires and decisions that move their due date more than once. One slip is life. A second slip on the same item is a pattern.
• Stalled loops. Hiring loops sitting in the same stage for more than a week with no scheduled next action. Candidates feel this before your data does.
• Response latency. Median time-to-first-reply on internal Slack and shared inboxes. Not the average, which one holiday inbox will wreck; the median.
• Scope ambiguity. Tickets reopened or reclassified in the last week. A rising reopen rate means work is being done to the wrong spec.

None of these is decisive alone. Two together is yellow. Three is a conversation you owe someone inside the week. The whole point is timing. Catch a slip here and the fix costs a ten-minute conversation. Miss it, let it surface at the quarterly review, and the same slip costs you a quarter. The signals all run off data you already have: a calendar, a ticketing tool, Slack timestamps. If you are building a dashboard for this, you have already overbuilt it.

People as a product: the structural read

Treat each People offering as a product. Onboarding is a product. Performance is a product. Comp, learning, internal mobility, the reference-letter process: all products, whether or not anyone has ever called them that. A product has an owner, a user, a spec, a measurement rhythm and an end-of-life. Run each offering through the filter and watch how many pass cleanly.

Almost no People function passes this cleanly the first time, and the retire date is where they fail most. Nobody retires anything. The performance process from three org shapes ago still runs alongside the new one. The onboarding checklist has grown a section for every incident it ever caused. Half of what a stretched team ships has no defined user and no measurement rhythm, which is exactly why the team feels underwater while the company feels underserved. The structural read is how you find the things to stop doing, and stopping is usually a bigger win than starting.

The workflow heatmap: where AI actually goes

The heatmap is a grid: every recurring People workflow down one axis, and three properties across the other. Frequency, how often it runs. Manual pain, how much hand coordination it costs per run. AI fit, which steps could be safely automated today given your actual tooling and data, not a vendor's slide. The rank falls out of the multiplication. This is the same logic as the workflow assessment framework, compressed to one artefact a leadership team reads in two minutes.

Read the bottom row carefully, because it is the one people get wrong. Absence and payroll reconciliation is painful and frequent enough to feel like the obvious first build. Its AI fit is low: the data is messy, the rules are exception-heavy, and the cost of an error lands in someone's pay packet. Park it. The genuinely automatable wins are policy Q&A and scheduling, high frequency and high fit, boring and safe. The unglamorous cells are almost always where the return is. A heatmap keeps you from spending your first AI budget on the workflow that looked hardest instead of the one that pays.

The AI readiness read: can the team support it

The heatmap tells you what is worth building. The readiness read tells you whether you could survive building it. Score the six axes from the AI readiness diagnostic honestly, and the honesty is the hard part. Most teams overestimate readiness on tooling and underestimate it on data. Tooling comes back a 7 because everyone has a login. Data comes back a 3 because the records that would feed the tool are scattered, contradictory, and owned by nobody.

Nobody scores a clean read across all six axes on the first pass, and a clean score would make me suspicious anyway. What matters is not the total. It is the gap: why tooling is a 7 while data is a 3, and which of the two you can move first. Pair the readiness read with the heatmap and you have a defensible answer to the question every CFO asks, of all the things we could build with AI, why this one first. A hot heatmap cell next to a weak readiness axis is not a no. It is a sequence: fix the axis, then build. If you want a fast version of this read before you commit anyone's week to it, the Readiness Assessment scores the function across four capability layers in about ten minutes.

The 90-day roadmap: sequencing the fixes

The other four diagnostics tell you where you are. This one is the only thing that tells you what to do first, and doing things in the wrong order is how good diagnoses die on the shelf.

Three priorities for the first 30 days. Three for days 31 to 60. Three for days 61 to 90. Nine items, no more. Each priority gets a single owner, a single weekly check-in, and a single visible scorecard. The discipline is the cap: the moment you have twelve priorities you have zero, because the team cannot tell which four to drop when the week goes sideways. Nine forces the trade-offs to happen on paper, where they are cheap, instead of in the moment, where they are not.

The roadmap does not run instead of the early warning. It runs alongside it. The roadmap sets the nine priorities in week one; the weekly signals tell you in week three whether priority four needs to jump the queue because the thing it was going to fix is already on fire. Skip that link and you will spend day 60 defending a plan that stopped matching reality around day 40. This is also the artefact you show the CEO in week two and the team in week three, because it says as much about what you are not doing as what you are.

Running the People Ops diagnostic toolkit in three weeks

The whole toolkit is three weeks of work, and it is worth being strict about the order, because each read feeds the next.

The output is a single page. Five sections, one per diagnostic, written in present tense, kept live. That page is the artefact you reference in every prioritisation conversation for the next six months, and the one you re-run each quarter so the reads stay comparable. It is cheap to produce and expensive to skip, which is the wrong way round from how most functions treat it.

Get the read right and every later decision, the AI ones included, has a defensible foundation under it. Skip it and you spend the next year defending choices nobody can connect to an honest read of the function. The toolkit is not a deliverable that gets filed. It is a habit, and it belongs in the AI workspace for People Ops alongside the tools it tells you when to buy. Reading the function is not the boring precursor to the interesting AI work. It is the work that makes the AI work worth doing. For the fuller picture of how the reads connect to what you build next, measuring AI value in People Ops picks up where the roadmap leaves off, and people debt names what GenAI exposes when you finally look.