Day 20: Create an HR Metrics Dashboard Narrative
The Concept
HR teams work hard to produce metrics. Headcount, turnover, time-to-hire, absenteeism, engagement scores — these numbers take time to gather, clean, and format. They are often presented in dashboards, spreadsheets, or slides that are dutifully distributed to leadership each month. And in most organisations, they are looked at briefly, noted, and filed, without any decision being made or any action being taken.
The problem is not that executives do not care about people data. It is that most HR reporting is structured as a data summary rather than a business story. A data summary tells you what happened. A business story tells you what it means, why it matters, and what needs to happen next. Executives are trained to respond to stories with implications and asks. They are not well-equipped to draw their own conclusions from a page of metrics without interpretation — particularly when those metrics are not their primary professional vocabulary.
The Difference Between Reporting and Insight
Reporting and insight look similar on the surface but are fundamentally different things. Reporting says: "Voluntary turnover is 18%, up from 14% last year." Insight says: "We are losing people at a rate that is costing us roughly three months' salary per departure in replacement costs, concentrated in two departments where we made a decision four months ago that we should revisit." The first statement is receivable as information. The second statement demands a response.
Most HR dashboards are built around reporting because data is easier to gather than interpretation, and because interpretation requires the analyst to make an argument — to claim that the numbers mean something specific, and to take some responsibility for being right. That requires both the contextual knowledge to know what is driving the numbers and the confidence to say so clearly to a senior audience. Both are harder than producing the numbers themselves.
Why Executives Switch Off from HR Data
Executives switch off from HR data for two reasons. The first is volume: a monthly dashboard with 12 metrics, all presented with equal prominence, trains the reader to scan rather than engage. When everything is reported, nothing is prioritised, and the implicit message is that all 12 metrics are equally important and equally actionable — which they are not.
The second reason is the absence of a clear ask. Data without a recommended action puts the cognitive burden on the reader to decide what to do with it. Executives who are already making dozens of decisions a week will set that burden aside until something forces them to pick it up — usually a crisis, by which point the data was telling the story three months ago. When the HR narrative ends with a specific, framed ask — "we are recommending an expedited pay review for operations and customer service, with a projected cost of X and a projected retention benefit of Y" — it gives leadership something to decide, not just something to know.
How AI Frames Metrics as a Coherent Story
AI is well-suited to the translation task in HR reporting: taking numbers, adding the context you provide, and producing a narrative that connects them into a coherent argument. The critical input you bring — and that AI cannot supply — is the contextual knowledge that explains what is actually driving the numbers. AI does not know that your turnover spike is concentrated in two departments. It does not know that your time-to-hire increase is driven by three outlier roles. It does not know what your leadership team has already decided or debated in the last quarter.
When you supply that context, AI can build the story around it — connecting cause to consequence, metric to implication, data to decision. The output is a draft that reflects both the numbers and the interpretation, written in language calibrated for a non-HR executive audience. Your role is to verify that the interpretation is accurate, that the ask is appropriate given what you know about the organisation, and that the risk flag points at the thing that genuinely keeps you up at night — not just the metric that is furthest from target.
Prompt of the day
Copy this into your AI tool and replace any bracketed placeholders.
Prompt
You are a strategic HR analyst who specialises in presenting people data to non-HR executive audiences. You understand that executives are not indifferent to HR data — they are overwhelmed by data in general and need HR's data to be translated into a story with a clear so-what before they can engage with it. You write narratives that turn numbers into insight, and insight into decisions. My situation: - Audience: [e.g. the Executive Committee — CEO, CFO, COO, and three divisional MDs — who see a monthly HR dashboard but rarely discuss it in any depth] - Period: [e.g. Q1 this year vs Q1 last year, and vs our internal targets] - Key metrics to include (paste your actual numbers or use these as a guide): - Headcount: [e.g. 412 at end of Q1, target was 420, net growth of 8 vs 22 in Q1 last year] - Voluntary turnover: [e.g. 18% annualised, up from 14% last year, industry benchmark 12%] - Time to hire: [e.g. average 47 days, target 35, up from 39 days last year] - Absenteeism: [e.g. 4.2% absence rate, up from 3.1% last year, CIPD benchmark 3.4%] - Any additional metric that matters to your organisation: [e.g. internal promotion rate, offer acceptance rate, manager NPS] - Known context behind the numbers: [e.g. turnover spike is concentrated in two departments — customer service and operations — and is linked to a pay review that was delayed by four months. The time-to-hire increase reflects three specialist roles that took significantly longer than average] - What you want executives to do with this information: [e.g. approve an expedited pay review for the two affected departments, and discuss whether our hiring process for specialist roles needs a different approach] Please produce: 1. An executive narrative — a 400-word story that moves logically from headline finding to supporting evidence to implication to recommended action. Written in business language, not HR language. No bullet points — this is prose that could be read aloud at an ExCo meeting. 2. A 'what this means' plain-language translation for each metric — one sentence per metric that explains what the number means in business terms, not what it measures. 3. A 'what we need from leadership' section — two or three specific asks of the executive team, framed as decisions rather than reports. Each ask should take no more than two sentences. 4. A risk flag — one paragraph on the single metric that, if it continues trending in its current direction for another quarter, will have a material business consequence. Name the consequence specifically.
Your 15-minute task
Pull up your most recent HR dashboard or data pack — the one you sent to leadership last month or last quarter. Do not use hypothetical numbers. Fill the prompt with your actual metrics and, critically, the context behind the numbers that does not appear in the dashboard itself. That context is the most valuable thing you bring to this exercise, because AI does not have it. Run the prompt. Read the executive narrative out loud: does it sound like something you would be confident presenting at a senior leadership meeting, or does it still sound like an HR report? If it does not pass that test, add more context to the prompt and run it again.
Expected win
A boardroom-ready HR metrics narrative, a plain-language translation of each metric for non-HR executives, a clear set of leadership asks framed as decisions, and a risk flag that quantifies the business consequence of a continuing trend — all from the data you already have.
Power user tip
The most powerful shift you can make in HR reporting is moving from a monthly data pack to a quarterly narrative with a monthly exception report. Run a follow-up prompt: 'Based on this quarter's narrative, write a one-page exception report format for monthly use. The exception report should flag only the metrics that have moved significantly since last month, explain in one sentence what drove the movement, and note whether any action is required or whether it is within expected variation. Everything else stays off the page.' Exception reporting trains executives to engage with HR data as a signal, not a summary — and it saves you the time of explaining 12 metrics every month when only two of them actually warrant discussion.