People Management
Your Team's Engagement Survey Results Are In: Choose One Action and Close the Loop
A fictional manager discusses aggregate engagement findings, selects one priority-communication action, and reports four weeks of mixed follow-through without claiming a score improvement.
When your team’s engagement survey results arrive, share the authorized findings, explain what they cannot establish, and involve employees in choosing one problem you can act on. Record the action, accountable owner, limits, review date, and how you will report progress back. Closing the loop means telling people what happened, including delays and work outside your authority; it does not mean declaring the survey problem solved after one meeting.
This LandOffer.ai guide contains a completed results discussion and a four-week action record with mixed results. The team, survey items, figures, and comments are entirely fictional editorial examples. They are not a real employee dataset or evidence of improved engagement. Primary guidance was checked October 27, 2026. No survey was launched, employee identified, reporting setting changed, or workplace message sent.

Read the report within its actual limits
Before showing a report, check who may see it, what population and period it covers, and how its scores are calculated. Confirm whether an item’s percentage describes favorable responses, an average rating, or something else. Participation and item-response counts may differ. Do not compare two figures until you know whether they use the same question, scale, population, and treatment of missing answers.
Use a low score to open a question about work; it cannot by itself identify a cause or a responsible person. It may reflect different experiences across the team. Nonrespondents’ views remain unknown. A comment can suggest a useful question without showing how common that experience is. Avoid turning the most memorable sentence into the whole team’s diagnosis.
Check confidentiality with the survey administrator before filtering or sharing. Culture Amp’s August 2026 documentation, for example, distinguishes confidential surveys from anonymous ones and describes configurable reporting and comment-group minimums plus protections against indirect identification. Its example minimum is not a universal safe group size. Your actual settings and notice govern what is available; do not try to reconstruct suppressed results or identify a writer from a phrase.
If you only have a higher-level report, say so. Do not invent a team-specific breakdown from an organization score. If a comment contains identifying information, ask the authorized survey owner how it should be handled rather than displaying it in a team meeting. Discuss the work using the authorized report instead of seeking unrestricted raw responses.
Share the findings before defending or fixing them
The University of Minnesota’s HR guidance recommends sharing results and involving employees in discussing feedback and deciding what action to take. It distinguishes the survey itself from the work that follows. That supports a conversation with the team rather than a manager privately choosing a convenient improvement and presenting it as what respondents requested.
Start by thanking people without asking anyone to disclose how they answered. Explain the report’s boundaries and acknowledge a concern you can see in the aggregate findings. Then invite discussion about work experiences and possible explanations. People may disagree with your interpretation; that is useful information, not a reason to demand that they prove their survey answer in public.
Separate what the team can change from what needs another owner. A manager might control how local priorities are communicated but not the company’s pay structure. Even when you start with a smaller action, keep the larger concern visible, identify its decision owner, and request an update without promising a decision you cannot make.
Gallup’s historical 2006 action-planning article describes explaining results, discussing meaning, assigning owners, and following up regularly. Those are useful process ideas; its research claims do not establish what a four-week trial will do for your team. The single-action approach below is an editorial choice to make one bounded commitment reviewable, not a claim that every survey requires exactly one action.
Completed results discussion: choose clarity when priorities change
Elena manages the fictional 18-person engineering operations team at Northline Tools. The survey administrator provides an approved team-level report for a September survey. Fifteen people responded. In this synthetic example, all 15 answered each of the three items shown, and “favorable” has a defined meaning in that fictional report. No demographic breakdown or raw comments are provided to Elena.
| Invented survey item, paraphrased for the example | Favorable responses | What Elena can responsibly say |
|---|---|---|
| Reasons for changed priorities are clear | 6 of 15, or 40% | Clarity about changes is a concern among these respondents; the cause is not established |
| Workload is manageable | 8 of 15, rounded to 53% | Workload deserves discussion; this does not measure actual hours or identify an individual’s workload |
| Contributions are recognized | 11 of 15, rounded to 73% | More respondents were favorable here; that does not mean everyone receives fair recognition |
These items and counts are original teaching material, not a licensed survey copied into the article. The 15 responses out of 18 invitations give approximately 83% participation. Elena does not identify the three nonrespondents or treat the response group as unanimous. She also has no comparable prior team report, so she does not announce a year-over-year decline.
Her completed September 25 discussion opening reads:
Thank you for the time you gave this survey. I have the approved team-level results, not individual answers or raw comments. We will not guess who responded or ask anyone to explain their survey answer. Six of the 15 responses were favorable on clarity about priority changes. That tells us this experience needs attention, not why each person answered that way.
I want to understand a work situation we can improve. When priorities change, what information would help you decide what to do next? You can discuss the process without describing your own survey response. If you prefer another channel, use the existing private route. We will keep workload and recognition in view even if our first trial focuses on priority explanations.
In the fictional discussion, participants describe two possible problems: work is added without identifying what moves, and changes arrive in several places without a clear reference. These are voluntary discussion observations, not decoded survey comments or a count of how many respondents held each view. One colleague notes that urgent incidents cannot wait for a polished announcement. Elena accepts that constraint.
The team considers a new weekly meeting, a shared priority-change note, and a request for more headcount. Elena can change her own team’s communication practice; she cannot approve hiring. Participants choose the note as the first trial because it addresses a specific experience without adding another recurring meeting. The staffing concern is logged for her director, with an update requested rather than funding promised.
Define the action so it can fail visibly
The completed action agreement sets a four-week trial from September 28 through October 23, 2026. Its purpose is to make the reason and trade-off behind a changed priority visible. It does not attempt to measure overall engagement or eliminate all workload pressure.
Action: When Elena changes an already agreed team priority, she will add a short note to the existing planning record stating the change, reason, work displaced or deferred, responsible owner, and effective date. She will link it from the normal team channel before the changed work begins where practical, and otherwise within the same business day.
Urgent exception: Incident response continues through the existing incident process. Where immediate action prevents a timely note, Elena will add the explanation by the next business day after stabilization. The note does not replace incident command or authorize people to ignore urgent work.
Responsibility and capacity: Elena owns writing and linking the notes. Engineers are not assigned a new reporting duty or asked to document their survey opinions. She will use a short existing record rather than creating a new approval system.
Review: At each Friday update, Elena will report eligible priority changes, notes completed within the agreed window, late or missing notes, and a concrete problem to repair. The October 23 review will decide whether to keep, revise, or stop the practice. Staff may offer feedback through existing channels without identifying survey answers.
Other concern: Elena will ask her director about the staffing issue and report the response she actually receives. No new position or budget is approved by this agreement.
They count only Elena’s changes to previously agreed priorities, excluding routine ticket edits and ordinary task completions so unrelated updates cannot inflate the trial’s completion rate. An urgent incident is not automatically a failure; the relevant check is whether its explanation meets the stated exception window.
The definition is intentionally narrow. Notes written on time are evidence that the agreed practice happened. They do not show that the explanation was useful, that people had enough capacity, or that survey scores improved. Those questions need separate feedback and, where appropriate, a later comparable assessment.
Four-week record: what happened and what stayed open
The following record is completed within the fictional case. It concerns changes and manager notes, not tracking individual employees or inferring respondents. The raw survey remains outside the trial record.
| Trial week and review date | Eligible changes and notes within the agreed window | Follow-up recorded |
|---|---|---|
| Week 1, October 2 | 3 changes; 3 timely notes | Process followed; a colleague asks for links to the displaced work, not only its title |
| Week 2, October 9 | 4 changes; 2 timely notes, 2 late | An urgent incident explanation and a separate vendor-related change missed their applicable windows; both notes later added |
| Week 3, October 16 | 4 changes; 4 timely notes | Elena adds links to deferred items; staff still raise uncertainty about who can authorize a new request |
| Week 4, October 23 | 4 changes; 3 timely notes, 1 still missing | Missing explanation remains Elena’s action; no claim that every change is documented |
Across the four weeks, 12 of 15 eligible changes had notes within the agreed window: 80%. Two notes were late and one remained missing at the final review. The timely count applies the agreed incident-exception window; the late incident note missed that window too. This is synthetic process arithmetic, not a measured increase in engagement or a causal productivity result.
Elena also records that her director acknowledged the staffing concern but had not authorized a new position. She has completed the request for review, while the resource decision remains open. She does not use a communication trial to declare the workload concern resolved. The missing note and unclear authorization route likewise remain visible.
Her completed closing message to the team reads:
We tried a priority-change note because the survey discussion identified missing reasons and trade-offs. Over four weeks, 12 of 15 changes had notes within the agreed window; two were late and one is still missing. I own completing the missing explanation. We added links to deferred work after your feedback. We have not established that workload or engagement improved.
I propose keeping the note for another two weeks, with the existing planning record showing who authorized each change. We agreed at today’s review to try that revision and recheck November 6. The staffing request has been acknowledged by the director, but no position is approved. I will report any actual decision through the normal channel. You do not need to disclose survey answers to comment on whether this practice helps.
The four-week loop closes with an honest account, an accepted revision, and unresolved work. The November 6 review has not occurred in this example. Do not report an outcome for a review that has not happened.

Keep reporting back without turning the score into the goal
Set the next update while people still know who owns it. Report a delay even when there is no favorable announcement. If the selected action is outside your authority, identify the decision owner and what you have requested; do not assign that person a commitment they have not accepted. If the action proves unhelpful, explain what you learned and choose a revision with the team.
Avoid pressuring people for more favorable answers or asking who wrote a difficult comment. A later score change can reflect a different response group, organizational events, or other factors. Preserve the survey administrator’s interpretation rules and confidentiality boundaries. An action log should make management follow-through visible, not become another source of employee surveillance.
Adapt the discussion and four-week record, name the action you can own, and schedule an update that reports both completion and remaining gaps. LandOffer.ai publishes this management guide; it does not administer your survey or promise improved engagement scores.



