Skip to main content

How to gather employee feedback and act on it to support change adoption

Gather employee feedback as an adoption control loop: ask, listen, analyze, respond, and show changes. Use it before, during, and after rollout to spot resistance, workload, training, and process issues, then adjust plans and communicate what changed.

Introduction: why this action matters for adoption

Change adoption depends on whether impacted people can understand the change, believe it is workable, and fit it into real work. Employee feedback is therefore not a courtesy activity; it is an adoption-control mechanism. It helps the change team detect confusion, resistance, workload impacts, training gaps, process defects, and local constraints before they become non-compliance or workarounds. Employee voice matters because it allows people to express views, concerns, and suggestions that can influence decisions, and because effective voice requires managers to listen and act on feedback [CIPD, 2026]. (cipd.org)

What this action is and when to use it

This action is a structured feedback-gathering and response intervention. It can use interviews, pulse surveys, listening sessions, manager feedback, employee representatives, issue logs, floor walks, digital forums, or post-go-live support channels. The defining feature is not the channel; it is the loop: ask, listen, analyze, respond, and show what changed.

Use it during discovery to understand impacts, during design to test proposed ways of working, before go-live to assess readiness, during go-live to remove blockers, and after implementation to reinforce adoption. It is especially important when the change affects roles, workload, autonomy, job security, systems, customer interactions, or performance expectations. Prosci identifies common sources of resistance including lack of awareness, fear of the unknown, role changes, distrust, and exclusion from change-related decisions [Prosci, 2022/2025]. (prosci.com)

Preparation: inputs, stakeholders, materials, timing, and decisions needed

Start with the change impact assessment, stakeholder map, adoption risks, training plan, communications plan, manager readiness assessment, and known pain points. Decide which groups must be heard separately, especially frontline employees, people managers, high-impact roles, resistant groups, remote or shift-based teams, and employees represented by formal consultation channels.

Prepare a short question set, facilitation guide, confidentiality statement, issue log, triage categories, escalation rules, and a response cadence. Before collecting feedback, confirm who has authority to make decisions. Gallup warns that listening posts require a response team with the authority, capacity, and willingness to respond; collecting input without a plan to act can frustrate employees and damage trust [Gallup, 2023]. (gallup.com)

Step-by-step facilitation guide

  1. Clarify the purpose. Explain that the session is to identify adoption barriers and improve implementation, not to relitigate every strategic decision. Be transparent about what is open to influence and what is fixed.

  2. Create safety and relevance. Tell participants how input will be used, whether comments are anonymous or attributed, and when they will hear back. CIPD emphasizes that employees need safe ways to speak up and that senior leaders and line managers play key roles in encouraging voice [CIPD, 2026]. (cipd.org)

  3. Ask adoption-focused questions. Focus on work reality: “What will be harder on day one?”, “What would prevent your team from using the new process?”, “What support is missing?”, and “What decision would make this easier to adopt?”

  4. Listen without defending. Managers should test understanding before responding. Prosci recommends beginning resistance management by listening to and understanding objections rather than labeling people as resistant [Prosci, 2022/2025]. (prosci.com)

  5. Sort feedback quickly. Categorize issues as awareness, role impact, process design, system access, training, workload, policy, customer risk, leadership trust, or out of scope. Assign each item an owner, due date, severity, and response path.

  6. Respond visibly. Acknowledge feedback within 48 hours where possible. Provide a practical “you said / we did / we cannot do because” update within one to two weeks. PMI emphasizes measuring feedback and applying corrective measures where needed during change execution [PMI, 2015]. (pmi.org)

  7. Adjust the change plan. Translate patterns into action: revise training, add manager talking points, change sequencing, simplify job aids, modify cutover plans, escalate design defects, or add hypercare support.

Example: how this could be applied in a real change initiative

A company implementing a new field-service scheduling tool holds three listening sessions with dispatchers, technicians, and frontline supervisors. Technicians say the mobile workflow assumes stable connectivity, which is unrealistic at several sites. Supervisors report that productivity targets do not allow time for first-week learning. The change manager logs both as adoption risks, escalates the connectivity issue to the product owner, secures offline job-aid guidance, and works with the sponsor to relax targets for two weeks. The next update states what was heard, what changed, and what remains under review. This converts feedback into adoption support rather than treating feedback as sentiment data.

Roles and responsibilities

The change manager designs the listening approach, facilitates sessions, analyzes themes, maintains the issue log, and ensures feedback changes the plan. The sponsor removes barriers, makes trade-off decisions, and communicates what has or has not changed. Middle managers and frontline supervisors create everyday voice channels, encourage candor, and coach employees through local impacts. Project, product, HR, IT, or process owners resolve issues within their domains. Employee representatives or HR partners should be involved where consultation, policy, employee relations, or legal obligations apply.

Common mistakes to avoid

The first mistake is asking for feedback when no one has authority to act. The second is using only a survey when the issue requires conversation; Gallup notes that surveys cannot replace relationships and everyday listening [Gallup, 2023]. (gallup.com) The third is over-defending the solution, which teaches employees that speaking up is risky or pointless. The fourth is hiding unresolved issues. It is better to say, “We heard this, we cannot change it because of a regulatory constraint, and here is the support we will provide.”

Measures of success or adoption indicators

Track whether the loop is working, not just whether sessions occurred. Useful indicators include participation by impacted group, number and severity of adoption barriers raised, percentage of issues acknowledged and closed on time, repeated themes, manager confidence, comprehension scores, training completion, system usage, process compliance, help-desk volume, workaround frequency, and sentiment about whether feedback is acted on. McKinsey’s transformation research highlights the importance of lower-level involvement, line-manager briefings, communication, and role clarity in successful transformations [McKinsey, 2021]. (mckinsey.com)

Checklist for the change manager

  • The impacted groups and high-risk roles are identified.

  • The listening purpose, scope, and non-negotiables are clear.

  • Questions focus on adoption barriers and support needs.

  • Managers know how to listen without defending.

  • A feedback log, owner, severity rating, and due date are in place.

  • A response cadence has been agreed with sponsors and project owners.

  • Employees receive “you said / we did / we cannot do because” updates.

  • Plan changes are reflected in training, communications, cutover, and hypercare.

Optional reusable template: listening session agenda

Time

Segment

Facilitation prompt

5 min

Purpose and boundaries

“We are here to understand what will help or hinder adoption.”

10 min

Change impact check

“What will change most in your daily work?”

20 min

Barrier discussion

“What could stop people from using the new way?”

15 min

Support design

“What would make adoption easier in the first 30 days?”

10 min

Close the loop

“Here is what happens next, when you will hear back, and who owns responses.”

References

CIPD. “Employee voice.” CIPD Factsheet. 06 Apr 2026. https://www.cipd.org/en/knowledge/factsheets/voice-factsheet/

Gallup. “5 Ways to Make the Most of Employee Voice.” 03 Nov 2023; updated 08 Dec 2023. https://www.gallup.com/workplace/513554/ways-employee-voice.aspx

Prosci. “Prosci’s Top 10 Tactics for Managing Resistance to Change.” Published 08 Jun 2022; updated 14 Nov 2025. https://www.prosci.com/blog/prosci-top-10-tactics-for-managing-resistance-to-change

Project Management Institute. “Measure twice, change once.” 2015. https://www.pmi.org/learning/library/practical-strategies-for-change-management-9887

McKinsey & Company. “Losing from day one: Why even successful transformations fall short.” 07 Dec 2021. https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/successful-transformations

MIT Sloan Management Review. “When Employees Speak Up, Companies Win.” 17 Nov 2020. https://sloanreview.mit.edu/article/when-employees-speak-up-companies-win/

Did this answer your question?