Changes are adopted locally. A sponsor can explain the business case, and a project team can deliver the solution, but team managers shape what employees hear, believe, try, repeat, and abandon. Prosci identifies people managers as critical change actors because of their proximity to impacted employees, and Gallup describes manager conversations as the “last mile” of change communication [Prosci, 2021; Gallup, 2024]. This action reinforces managers’ involvement after the initial launch, when resistance often becomes visible through workarounds, slow uptake, complaints, avoidance, or uneven performance [Prosci, 2022].

Reinforcing manager involvement means reminding managers of the specific behaviors expected of them, supporting them to handle resistance constructively, and recognizing progress when their teams adopt the new way of working. It sits in the reinforcement, recognition, and sustainment category of change management. It is not another announcement; it is a targeted intervention to keep managers active as communicators, advocates, liaisons, coaches, and resistance managers [Prosci, 2021].

Use it when adoption is uneven, managers are avoiding difficult conversations, employees are reverting to old processes, or the project is moving from go-live into stabilization. It is also useful before high-resistance moments such as role redesign, performance-policy changes, technology cutovers, restructuring, or workflow standardization. McKinsey’s influence model supports this logic: behavior change is more likely when people understand the change, see role modeling, have capability, and experience aligned reinforcement mechanisms [McKinsey, 2016].

Start with evidence, not anecdotes. Review adoption data, help-desk themes, training attendance, process compliance, employee feedback, manager sentiment, and sponsor observations. CIPD emphasizes that performance management requires clear expectations, regular discussion, feedback, and accountability; the same applies to adoption behaviors during change [CIPD, 2026].

The key stakeholders are the sponsor, change lead, HR or people partner, project owner, impacted team managers, and any change champions. Before meeting managers, decide which behaviors matter most. For example: “hold weekly adoption check-ins,” “log resistance themes,” “coach employees on the new workflow,” “escalate barriers within 48 hours,” and “recognize correct use of the new process.” Also decide what support managers will receive, because perceived organizational support and readiness are associated with lower resistance [Yu and Lee, 2015].

A customer service organization launches a new case-management workflow. After go-live, system usage is high, but quality audits show many employees still keep side spreadsheets. The change manager discovers that supervisors are reminding teams to use the tool but are not asking why spreadsheets remain useful.

The change lead runs a 30-minute supervisor reinforcement session. Supervisors receive a resistance log, a five-question coaching script, and a weekly recognition prompt. In week one, they ask employees what the spreadsheet does that the new system does not. The project team learns that one report is missing. In week two, supervisors explain the workaround retirement date, recognize employees who close cases fully in the system, and escalate the missing report. Adoption improves because managers are no longer only communicating; they are diagnosing, coaching, and reinforcing.

The change manager designs the reinforcement approach, provides prompts and tools, reviews adoption evidence, and coaches managers. The sponsor confirms expectations, removes cross-functional barriers, and reinforces that adoption is a business priority. Team managers hold resistance conversations, model the new behaviors, recognize progress, and escalate barriers. HR or people partners help align objectives, feedback, recognition, and performance discussions. Project leads respond quickly to valid process or system issues so managers do not lose credibility.

Avoid treating resistance as attitude rather than data. Avoid asking managers to “drive adoption” without giving them time, scripts, decision rights, or escalation paths. Avoid generic recognition such as “thanks for supporting the change”; recognize the specific manager behavior that improved adoption. Avoid over-relying on dashboards while ignoring employee voice, because CIPD highlights the value of listening channels and qualitative insight alongside measurement [CIPD, 2025]. Avoid waiting until go-live; managers need involvement before resistance hardens.

Use a mix of manager activity, employee response, and business outcome indicators. Track whether managers are holding adoption check-ins, logging barriers, recognizing desired behaviors, and escalating issues. Track employee indicators such as confidence, clarity, sentiment, training-to-usage conversion, and reduction in recurring objections. Track adoption indicators such as process compliance, system usage quality, reduced workarounds, cycle time, error rates, customer outcomes, or benefits realization. Gallup’s change research also suggests monitoring trust, communication, engagement, burnout, and intent to leave during disruptive change [Gallup, 2024].

“I want to understand what is making this change difficult in day-to-day work. What part of the new process is unclear, impractical, or slowing you down? Here is what is not optional and why it matters. Here is where we still have room to improve the how. Let’s agree one action you will try this week, one barrier I will escalate, and one point we will review in our next check-in.”