Day 17: Analyse Engagement Survey Results and Write a Leadership Report
The Concept
Every year, thousands of organisations run employee engagement surveys. Employees take 20 minutes out of their day to tell the organisation what is working and what is not. The data is collected, processed, and handed to HR. And then, in most organisations, one of two things happens. Either a 40-page report lands in leadership's inbox and everyone agrees it is very interesting and nothing changes. Or HR produces an action plan, works hard on it for three months, and then wonders why engagement scores look exactly the same the following year.
The survey is not the problem. The reporting is. Engagement data fails to drive change not because leaders do not care, but because the data is presented in a way that makes it easy to receive passively and hard to act on actively. When the report is structured around scores and benchmarks, leaders can absorb it without feeling that anything is required of them. When the themes are described in HR language rather than business language, the CFO mentally files it as an HR issue. When HR arrives with the action plan already written, leaders feel like observers of a process that does not require their judgment.
The Problem at the Reporting Stage
The gap between data collection and behaviour change almost always happens at the reporting stage. The issue is not a lack of insight — most engagement surveys surface the same patterns that experienced HR professionals already suspected. The issue is translation: turning scores into a story that leaders recognise as describing their business, and turning themes into actions that leaders feel personally responsible for taking.
This is harder than it sounds. It requires moving from "our management quality score is 49%" to "half your employees are not getting the conversations they need to perform and stay." It requires framing the cost of inaction in terms a CFO tracks — turnover cost, productivity drag, hiring cost, time-to-competence — rather than in terms of employee experience. And it requires structuring the presentation so that leadership leaves with ownership of the response, not a list of things HR is going to do.
How AI Synthesises Qualitative Data at Scale
One of the most time-consuming parts of engagement report writing is making sense of the open-text comments. A 300-person survey might generate 600 comments. Reading them all, identifying recurring themes, and deciding which themes are significant enough to surface and which are outliers takes hours of careful work. And the themes that emerge from that process are only as useful as the language you find to describe them — language that captures what employees meant, not just what they said.
AI can process a large volume of comments and identify recurring patterns faster than any human analyst. More usefully, it can describe those patterns in language you can test against the raw data — "the dominant theme across 38 comments about management is not dissatisfaction with managers as people, but a specific absence of development conversations and career direction" is a more useful finding than "management quality is a concern." When you give AI a representative sample of comments alongside the scores, it can produce that level of description and connect it back to the quantitative picture.
Framing Findings So Leaders Feel Ownership, Not Blame
The most important design decision in any engagement report is who the audience feels responsible for the findings. If the report is framed as "here is what is wrong with how this organisation treats its people," leaders will listen politely and wait for HR to fix it. If it is framed as "here is what the data tells us about the business decisions and leadership behaviours that are driving these results — and here is what each of you can do about it in your part of the organisation," the conversation changes.
Today's prompt produces a leadership discussion guide specifically for this reason. The five questions are not comprehension questions. They are activation questions designed to move leaders from passive reception to active response. Combined with the risk section — which frames the cost of inaction in business terms, not HR terms — they change the dynamic of the presentation from a report-and-receive session to a genuine leadership conversation. That shift, more than any action plan HR produces on its own, is what moves the needle on engagement.
Prompt of the day
Copy this into your AI tool and replace any bracketed placeholders.
Prompt
You are an organisational effectiveness consultant who specialises in making employee engagement data meaningful to senior leaders. You are skilled at identifying patterns in survey results, synthesising open-text comments into named themes, and framing findings in a way that motivates leadership action rather than triggering defensiveness. My situation: - Organisation or team size and type: [e.g. 320-person professional services firm, four business units, survey conducted annually] - Overall engagement score and benchmark: [e.g. overall engagement score 62%, down from 67% last year, below our industry benchmark of 71%] - Scores to highlight (paste the key metric scores): [e.g. 'I feel proud to work here' 78% / 'I have the resources to do my job well' 54% / 'My manager gives me useful feedback' 49% / 'I see a clear future for myself here' 41%] - Open-text themes (paste a sample of 10-15 anonymised comments, or summarise the recurring themes you noticed): [e.g. recurring themes include: unclear career paths, inconsistent management quality, feeling overloaded since the restructure, and appreciation for the collaborative culture] - The audience for this report: [e.g. the senior leadership team — CEO, CFO, and four divisional directors — who want to understand what the data means and what they should do, not just the numbers] - One thing you want leaders to take ownership of (not HR to fix): [e.g. the management quality scores — we need leaders to hold their direct reports accountable for development conversations, not expect HR to train their way out of it] Please produce: 1. An executive summary — 300 words maximum. Headline finding, two or three supporting themes, one clear ask of leadership. Written in the kind of language a board paper uses, not an HR report. 2. A structured report body — theme by theme, each with: the relevant score(s), what the qualitative comments add to the picture, and one recommended action that is within the gift of leadership to take. 3. A risk section — two or three things that will happen if this data is presented, discussed, and then nothing changes. Frame these as business risks, not HR concerns. 4. A leadership discussion guide — five questions to put to the leadership team during the presentation that will move them from passive recipients to active owners of the response.
Your 15-minute task
Gather your most recent engagement survey results — even if they are six months old and the report has already been presented. Paste in the key scores and a sample of the open-text comments, or summarise the themes you identified at the time. Run the prompt and read the executive summary first: does it tell the story you would want a CEO to hear in 60 seconds? Then read the risk section — are the business risks framed in language your CFO would recognise, or do they still sound like HR concerns? Use the gap between what AI produces and what you would have written to identify where your own reporting instincts could be sharpened.
Expected win
A leadership-ready engagement report with an executive summary that gets to the point, theme-by-theme analysis with recommended actions, a business-risk framing of the cost of inaction, and a discussion guide that turns the presentation into a conversation — produced in the time it usually takes to format a slide deck.
Power user tip
The discussion guide is the most underused part of this output. Most engagement presentations end with leaders nodding, agreeing it is important, and waiting for HR to come back with a plan. The five questions in the guide are designed to interrupt that pattern by asking leaders what they will do differently — in their teams, with their direct reports, in the next 90 days. After the meeting, run a follow-up prompt: 'Based on the commitments made in the leadership discussion, write a one-page action summary that assigns each commitment to a named owner, sets a 90-day review date, and defines what success looks like. Format it as a decision record, not a project plan.' Send it to the leadership team within 24 hours of the meeting, while the conversation is still fresh.