Change adoption rarely becomes sustainable while it is owned only by a project team, transformation office, or communications function. Employees experience change through their daily work, and line managers sit closest to that work. Prosci identifies people managers as key change agents because they communicate local impact, advocate, liaise with project teams, manage resistance, and coach employees through new ways of working [Prosci, 2025]. (prosci.com) CIPD similarly describes line managers as responsible for day-to-day operations, people management, policy implementation, and team development [CIPD, 2025]. (cipd.org)

Establishing a plan to migrate change leadership to operational managers is a governance, planning, and operating model intervention. It clarifies how adoption leadership moves from “project-led” to “business-led” while maintaining sponsorship, feedback, and accountability. This matters because transition to operations should be planned, ownership should be transferred, and ongoing operational responsibilities should be accepted rather than assumed [Government Project Delivery, 2026]. (projectdelivery.gov.uk)

This action creates a documented handover plan for adoption leadership. It defines what operational managers will lead, what the change team will continue to support, what decisions managers can make locally, how resistance and adoption data will be escalated, and when operational leaders formally accept ownership.

Use it when a change is moving from design or implementation into adoption, pilot, rollout, hypercare, or sustainment. It is especially useful when the change affects daily routines, performance expectations, customer service, compliance behavior, workflow, technology use, or team norms. It should not be used as a way to offload accountability onto managers who lack time, authority, or training. CIPD’s research on devolving responsibilities to managers highlights that capacity, training, support, and power are common barriers when responsibilities are pushed down without sufficient enablement [CIPD, 2024]. (cipd.org)

Before facilitating the plan, gather the change impact assessment, adoption outcomes, stakeholder map, readiness data, manager population list, training plan, communications plan, issue log, benefits map, and future-state operating model. Government project delivery guidance defines a target operating model as the future organization, working practices, processes, information, and technology supporting operations [Government Project Delivery, 2026]. (projectdelivery.gov.uk)

The core stakeholders are the executive sponsor, operational leader, impacted managers, change manager, project or product owner, HR or L&D partner, communications partner, and benefit owner. PMI emphasizes that benefits realization requires cooperation, roles, responsibilities, ownership, and accountability [PMI, 2016]. (pmi.org)

Time the session after the future state and impacted groups are clear, but before managers are expected to lead adoption. If you wait until go-live, managers will be asked to lead conversations they did not help shape.

A company implementing a new CRM initially uses the change team to run communications, training, and readiness surveys. Four weeks before pilot, the change manager facilitates a migration session with sales directors and frontline sales managers. The group agrees that sales managers will lead weekly pipeline-quality reviews, coach representatives on new account-entry behaviors, identify resistance themes, and confirm whether old spreadsheets have been retired.

The change team supplies adoption dashboards, objection-handling guides, and a feedback route to the product owner. The sales director chairs the adoption forum, not the change manager. After two release cycles, CRM usage, data quality, and forecast accuracy become part of the sales operating rhythm. This is the point of migration: adoption becomes how the business runs, not a side project.

The first mistake is treating migration as abdication. Operational managers should inherit leadership of adoption, not be abandoned with unresolved design issues. The second is handing over too late, after employees have already formed negative views of the change. The third is asking managers to “own adoption” without decision rights, time, or escalation routes. The fourth is measuring manager activity rather than adoption outcomes. McKinsey notes that leaders often receive activity-based progress reports rather than clear business results [McKinsey, 2025]. (mckinsey.com)

A subtler mistake is over-standardising the manager role. Consistency matters, but managers need space to adapt examples, objections, and reinforcement to their team context.

Use a balanced set of indicators. Leading indicators include manager attendance at adoption forums, completion of manager enablement, quality of local adoption plans, readiness scores, number and aging of unresolved barriers, and manager confidence. Adoption indicators include usage of the new process or system, reduction in workarounds, proficiency after training, quality measures, employee sentiment, and customer or operational performance. Sustainment indicators include whether old practices are retired, whether the new behavior appears in team routines, and whether benefits continue after central change support reduces. GovS 002 recommends tracking readiness, progress toward the future state, sustainability of behaviors, and performance indicators during use [Government Project Delivery, 2026]. (projectdelivery.gov.uk)