Survey findings become useful when someone discusses them and owns the next step. You do not need to promise a solution to every issue. Explain what the organisation will do and what it cannot currently do.
Check the evidence first
Before presenting results, review participation, response counts and comparable wording. Separate observations from hypotheses. Low communication ratings do not establish that more meetings are the answer. Read interpreting survey results.
Comments can add context, but do not publish identifiable accounts. Treat AI summaries as drafts to check: look for omitted minority perspectives and unsupported causal claims.
Select a small number of actions
Prioritise relevance to work, ability to influence the issue and available resources. Two or three actions can be a practical starting point, not a methodological requirement.
| Plan element | Illustrative example |
|---|---|
| Observation | Some people report unclear priorities |
| Hypothesis | Two task sources may set conflicting expectations |
| Action | Agree one owner of project priorities |
| Owner | Project manager |
| Evidence of completion | Publish and discuss the decision process |
| Outcome information | Examples of priority conflicts and later pulse responses |
| Review date | After an agreed period of practice |
Tell the team what happens next
Example message:
Thank you for your responses. Clarity of priorities is a recurring theme. Over the next month we will agree how conflicting tasks are resolved. The project manager owns this action. At next month’s meeting we will explain what has changed. Other themes need further discussion; we will explain which can be addressed later.
For distributed teams, make the update available in the working languages and provide an asynchronous way to ask questions. Confidentiality rules still apply when presenting findings.
Review completion and outcomes separately
First check whether the action happened. Then investigate what changed at work. Another pulse can add information, but a higher score alone does not establish causation.
Create an account and organise your survey and follow-up. For individual development, use the IDP template.
A comment requiring action is not just a quotation
Before launch, decide who can safely receive concerns about violence, discrimination, unlawful conduct or urgent danger. A sentiment survey does not replace a reporting channel or urgent support. Do not promise individual follow-up if responses are genuinely anonymous.
Do not copy a full comment into slides or an external AI tool. Limit access and details to what the appropriate process requires; do not circulate allegations about named people. See access, retention and AI safeguards.
Sources and scope
These sources support the principles discussed here. Examples and schedules are starting points to adapt, not standards or evidence that our templates have been validated.
