An Employee Survey Cannot Do the Listening for You

An employee survey can collect dissatisfaction without changing the conditions that produced it. The organisation receives a score, managers prepare explanations and staff are asked to believe that being measured is evidence of being heard. The missing step is often a decision.

The CIPD's employee voice guidance treats voice as expression with the ability to influence matters at work. Its discussion includes formal and informal channels and the importance of leadership response. A survey is therefore one route into a wider process, rather than a substitute for that process.

For leaders, the useful question is what an employee can reasonably expect to happen after raising a problem. If nobody can describe the route from observation to decision, another questionnaire may produce more data without improving the organisation's ability to act.

Ask about an operational consequence

Broad questions about engagement can identify concerns, but managers also need specific evidence. Where does a promised customer response become impossible? Which approval causes avoidable delay? What information regularly arrives after it is needed? These questions connect employee experience with the work the business is trying to perform.

Consider an illustrative retail team reporting that a new campaign is difficult to deliver. A survey might classify the response as low confidence in change. A conversation could reveal that stock arrives after the promotional material, or that the returns process contradicts the promise made in the campaign. The appropriate response depends on what is actually wrong.

Leaders should resist converting every operational objection into a communication problem. Sometimes the team has understood the instruction perfectly and is describing a fault in its design. Listening requires enough curiosity to distinguish that possibility from unfamiliarity or reluctance.

Make the response visible, including a refusal

Employees do not need every suggestion accepted. They need a credible explanation of what was considered, what was decided and who will act. A well-explained refusal can be more respectful than a vague promise to explore an issue indefinitely.

Record a small set of material concerns with an accountable owner and a date for the next response. Where an issue crosses departments, appoint someone who can resolve the dependency rather than passing it between teams. Tell employees when the timetable changes and why.

Protect appropriate confidentiality, especially where an individual could be identified from a small team or a distinctive incident. Do not promise anonymity that the process cannot support. People need to understand the channel before deciding what they are comfortable sharing.

Check who is missing from the conversation

The people most available for consultation may have the least exposure to the difficult parts of the service. Night teams, part-time colleagues, temporary workers and employees moving between sites can encounter failures that the daytime leadership group rarely sees.

Offer ways to contribute that fit the work. A lengthy online exercise during a busy shift may exclude the very colleagues whose observations are most useful. Short conversations at appropriate times can complement formal methods, provided the findings reach someone able to respond.

The final test concerns changed practice. Revisit a resolved issue with the employees who raised it. Has the handover improved? Does the customer receive a clearer answer? Has the additional work simply moved to another team?

This is closely related to making leadership meetings useful. Employee voice should feed decisions and follow-through. The organisation demonstrates that it listens through what happens after the feedback, not through the elegance of the survey dashboard.