Employee listening
How to close the employee feedback loop.
After employees share feedback, they need to know what happened to it. Turn the findings into a decision record, tell people what they can expect and check what happened after the first change.
- Document the decision
- Record the evidence, the owner and why the proposed response fits what people described.
- Communicate a next step
- Say what you will change, what needs more checking and when employees will hear again.
- Check what changed
- Pair a simple process observation with a question to the people affected.
In practice
How the work comes together
Capture the decision
For each theme, record the evidence, a decision status, an owner and a review date.
Publish a short update
Tell employees what can be shared, what will happen next and how they can respond.
Return with the result
Check delivery and the experience of the people affected. Explain the decision to continue, adapt or stop.
Turn the findings into decisions
Bring the relevant owner a small set of findings. For each one, write what happened, who could observe it, what is uncertain and what options are available. Record the next decision as act, investigate further or defer with a reason. One team can own several actions, but each action needs a named role with authority to deliver it.
If a proposed action depends on another team, ask that team to confirm the dependency before announcing a date. Keep a separate line for issues that need an established individual reporting route. Discuss those through the appropriate process with the people authorized to handle them.
Write an update employees can act on
A brief update can answer four questions. What did we hear? What are we going to do? What is still open? When will we share an update? Include how people can add context. Use broad descriptions where a distinctive quote, location or role could identify a participant.
For example, “Several people described having to ask for updates after submitting a request. Operations will test a visible status field in the next two weekly cycles. The team is also checking whether access differs by role. We’ll share what we learn at the next team briefing.” Use a scope and date your actual owner can commit to.
Decide how to follow up before the test starts
Pick a measure that sits close to the change. For the status-field example, count requests in the test period that had a visible status at a defined point and write down how many requests were eligible. Ask a few requestors to explain how they found the status. The count shows whether the process ran as expected. The follow-up can explain where people still got stuck.
Check who is missing from the follow-up. Compare the same group and process where possible. If the rollout changed during the test or the sample is small, keep those limits next to the conclusion. Use the evidence to decide whether to keep, adapt or end the change.
Explain why a change is being deferred
Some issues need a longer investigation or depend on a decision your team cannot make. Give the reason and say what would change the decision. If you have a responsible owner or a review date, share it. Where details are confidential, explain the route through which the issue will be handled at a level appropriate for the audience.
CIPD’s employee voice guidance describes how complementary channels can support two-way communication. The follow-up is one of those channels. Choose a format the people who contributed can access, whether that is an all-shift briefing, a written update or a discussion with employee representatives.
Frequently asked questions
Questions that come up
When should I update employees?
Give a first update when you can summarize the process or set a realistic decision date. Give a second when the decision is made or the agreed check-in arrives.
Can I share quotes from the campaign?
Follow the collection and disclosure arrangements you explained. If the role, event or wording could identify someone, use an aggregated or generalized description where that is appropriate.
What if employees disagree with the planned change?
Keep a clear way to add a counterexample or propose a different response. Ask the owner to explain their decision and which observations might change it.
Talk to Lontra HR
Bring one real HR question.
See how a first campaign could work for your team.