Manager feedback is one of the fastest ways to learn whether a change is being adopted in real work, not just announced. Managers hear the questions employees ask after town halls, see the workarounds people create, and notice whether new behaviors are becoming routine. Prosci describes people managers as critical change roles because they communicate local impacts, liaise with project teams, identify resistance, and coach employees through change [Prosci, 2025]. (prosci.com)

This action matters because resistance is often a signal. It may point to unclear reasons for change, poor process design, competing priorities, missing skills, low trust, or real operational risk. Research on resistance to change shows that resistance can be treated as useful information as well as a barrier, especially when leaders use participatory strategies such as listening, transparent communication, and involving employees in change development [Schweiger et al., 2018]. (onlinelibrary.wiley.com)

This action is a structured feedback-and-response loop with managers and team leaders. It gathers what managers are hearing and seeing about employee understanding, commitment, capability, adoption behaviors, and resistance. It can use short interviews, pulse surveys, manager listening sessions, structured team-lead huddles, or a shared feedback log.

Use it before launch to test readiness, during training to identify capability gaps, at go-live to remove blockers, and after implementation to reinforce adoption. It is especially valuable when a change affects role design, workload, customer interactions, systems, compliance, or performance expectations. It should complement, not replace, direct employee voice. CIPD notes that employee voice can be formal or informal and that a single mechanism is rarely sufficient [CIPD, 2026]. (cipd.org)

Start with the change impact assessment, stakeholder map, adoption goals, training plan, communications plan, and known risks. Decide which manager groups are closest to the impacted work and where feedback may be filtered or politically sensitive. ACMP’s Standard frames change management as a set of generally accepted practices across stakeholder engagement, communication, sponsorship, and resistance management, so the feedback loop should connect to those plans rather than sit outside them [ACMP, 2025]. (acmpglobal.org)

Prepare a short manager briefing, a feedback guide, a simple capture form, and a response tracker. Make three decisions before collecting input: what information is confidential, who can see raw comments, and how quickly the change team will respond. As practical guidance, aim to review feedback within 24–48 hours during high-impact phases and publish a “you said / we did / we cannot yet do” update within the next manager cadence. CIPD emphasizes that managers need to listen and act on feedback, and Gallup notes that trust is built when leaders follow through and respond to feedback [CIPD, 2026; Gallup, 2024]. (cipd.org)

A company is replacing a legacy CRM with a new sales platform. Two weeks before launch, the change manager asks regional sales managers to run 20-minute team check-ins and submit feedback using a standard form. Managers report that employees understand the business reason but fear losing customer notes, do not know which reports will replace old dashboards, and believe the new process will add time before customer calls.

The change manager synthesizes the feedback overnight. The project team confirms a data migration issue for one region, the training lead creates a five-minute reporting demo, and the sponsor clarifies that call preparation time will be adjusted for the first month. In the next manager huddle, the change manager shares what changed because of the feedback and what will not change. This turns “resistance” into design fixes, expectation setting, and targeted support.

Do not ask managers for feedback if leaders are not prepared to respond. Do not treat negative feedback as disloyalty. Do not rely only on the loudest or most supportive managers. Do not collect vague sentiment without examples of behavior, workflow impact, or adoption barriers. Do not expose individual employee comments unnecessarily. Finally, do not confuse communication reach with adoption; employees may have heard the message and still lack time, skill, confidence, or system readiness to change.

Useful indicators include manager participation rate, feedback cycle time, number of barriers resolved, recurrence of themes, employee confidence, trust in leadership, training completion, help-desk trends, usage data, process compliance, and observable behavior change. Gallup argues that engagement is important to watch during disruptive change because it reflects capacity for change, and PMI highlights employee morale or retention as relevant change outcome measures [Gallup, 2024; PMI, 2014]. (gallup.com)

Opening script for managers:
“We are collecting feedback to understand what is helping or slowing adoption. This is not about blaming individuals. Please share what employees are asking, where work is getting harder, and what would help the team use the change successfully.”

Feedback fields:
Change area:
Team or location:
What employees understand well:
Main questions or concerns:
Observed adoption behaviors:
Observed workarounds or avoidance:
Root cause guess: awareness / desire / knowledge / ability / reinforcement / workload / system / leadership / other
Impact if unresolved:
Suggested support or decision needed:
Urgency: low / medium / high
Owner assigned:
Response shared back on: