Skip to main content

Measuring Manager Effectiveness During Change and Turning Gaps into Action Plans

Measure manager effectiveness by tracking a small set of adoption indicators, reviewing them regularly, and creating targeted action plans. Use it to see where change is sticking, where teams are blocked, and whether managers need coaching, support, or e…

Introduction: why this action matters for adoption

Change often succeeds or stalls at the manager layer. Employees usually look to their direct manager to interpret what the change means, whether it is safe to raise concerns, and what “doing it right” looks like in daily work. ACMP defines change management as a structured approach to moving an organization to a future state to achieve expected benefits, and those benefits depend on people adopting the change, not simply hearing about it [ACMP]. (acmpglobal.org)

Measuring manager effectiveness is therefore an adoption measurement and reporting intervention. It helps the change manager see where adoption is taking hold, where teams are stuck, and where managers need support. This matters because evidence reviews show that line and middle managers influence support for change, implementation effectiveness, and team performance [CIPD/CEBMa, 2023]. (cipd.org)

What this action is and when to use it

This action defines a simple set of indicators for how well managers are helping their teams adopt the change, reviews those indicators regularly, and creates targeted corrective action plans where gaps appear. It is not a popularity contest or a “name and shame” dashboard. It is a way to connect manager behavior, team adoption evidence, and decisions about reinforcement, coaching, training, or sponsor escalation.

Use it when managers are expected to translate the change into local practice, especially during pilots, phased rollouts, go-live, stabilization, or benefit realization. Prosci’s ADKAR model is useful here because it frames adoption as individual outcomes: Awareness, Desire, Knowledge, Ability, and Reinforcement [Prosci]. (prosci.com)

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

Before measuring managers, agree what “effective change management by a manager” means for this specific initiative. Prosci’s CLARC roles provide a practical starting point: communicator, liaison, advocate, resistance manager, and coach [Prosci, 2023]. (prosci.com)

Prepare four inputs: the expected behavior change, the manager role expectations, team-level adoption indicators, and available support options. Stakeholders should include the sponsor, change manager, impacted managers, HR or L&D, project/product owner, and whoever owns operational adoption data. Timing should match the change phase: lighter readiness measures before launch, closer weekly or biweekly reviews during rollout, and reinforcement checks after go-live. McKinsey recommends regular review of initiative progress, behavioral “health,” performance outcomes, and value, while keeping the metric set small enough to use [McKinsey, 2020]. (mckinsey.com)

Step-by-step facilitation guide

  1. Define adoption outcomes. Describe the few behaviors that prove the change is taking hold. For example: “supervisors use the new scheduling process for all shift changes” or “sales managers coach pipeline hygiene in weekly one-to-ones.”

  2. Translate outcomes into manager expectations. For each manager group, define observable actions: holding team huddles, answering impact questions, escalating blockers, coaching practice, addressing resistance, and recognizing early wins. Tie these to ADKAR or CLARC so the scorecard measures adoption support, not generic busyness [Prosci; Prosci, 2023]. (prosci.com)

  3. Select a small evidence set. Use a mix of leading and lagging indicators: manager completion of enablement, employee understanding, training practice, system/process usage, resistance themes, quality or cycle-time data, and manager escalation quality. Avoid dashboards with dozens of metrics; McKinsey notes that complex metric sets often become unused [McKinsey, 2020]. (mckinsey.com)

  4. Baseline and segment. Establish the starting point by team, location, role, or manager group. Compare like with like; a frontline supervisor with a high-volume operational team may need different indicators than a middle manager coordinating cross-functional adoption.

  5. Run a review conversation. Facilitate a short review with managers and sponsors: what is improving, what is stuck, what is within the manager’s control, and what must be escalated. Include direct manager feedback because managers act as a liaison between the project and the workforce [Prosci, 2023]. (prosci.com)

  6. Diagnose the cause before prescribing the fix. Low adoption may reflect manager resistance, unclear messages, lack of skill, poor system design, insufficient staffing, or conflicting incentives. McKinsey’s influence model suggests checking understanding, reinforcement, skills, and role modeling before assuming unwillingness [McKinsey, 2016]. (mckinsey.com.br)

  7. Create a corrective action plan. Keep it specific: gap, evidence, expected behavior, support provided, owner, date, review cadence, and decision point. SHRM’s guidance on improvement plans emphasizes specific examples, measurable expectations, reasonable time frames, and regular check-ins [SHRM, 2025]. (shrm.org)

  8. Review and adapt. Close actions when evidence improves. If gaps persist, decide whether the issue requires more coaching, sponsor intervention, workload relief, process redesign, or formal performance management.

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

A regional service organization rolls out a new field-service mobile app. The change team defines adoption as technicians closing work orders in the app within 24 hours, attaching required photos, and using new safety prompts.

Manager effectiveness is measured through five indicators: attendance at manager enablement, weekly team huddles completed, technician confidence pulse results, app usage by team, and quality exceptions. Two supervisors show low usage and high exception rates. The review finds different causes. One supervisor does not understand the new workflow, so the action plan includes shadowing, a refresher, and daily coaching for one week. The other supports the app but lacks replacement coverage for technicians in training, so the sponsor removes a scheduling constraint. Both plans are reviewed after two weeks.

Roles and responsibilities

Role

Responsibility

Sponsor

Set expectations that managers lead adoption, remove systemic blockers, and avoid punitive use of early data.

Change manager

Design the scorecard, facilitate reviews, diagnose patterns, and coordinate support.

People managers

Communicate local impacts, coach teams, surface feedback, manage resistance, and reinforce new behaviors [Prosci, 2023].

HR/L&D

Provide coaching, learning support, and fairness checks for corrective plans.

Project/product owner

Supply process, system, quality, and benefit data.

Data/BI partner

Maintain dashboard integrity and segmentation.

Common mistakes to avoid

  • Measuring communications sent instead of behavior changed.

  • Ranking managers publicly before validating context.

  • Using too many metrics or metrics no one acts on.

  • Treating all resistance as manager failure.

  • Creating an action plan without support, time, or sponsor decisions.

  • Ignoring workload, conflicting incentives, or system defects.

  • Waiting until go-live to define adoption evidence.

Measures of success or adoption indicators

The action is working when manager reviews lead to faster, better decisions. Useful indicators include improved ADKAR pulse scores, reduced variation between teams, increasing correct usage of the new process or system, fewer repeated resistance themes, faster blocker resolution, completed manager action plans, improved quality or cycle-time outcomes, and evidence that managers are coaching and reinforcing the change. Gallup’s finding that managers account for a large share of team engagement variance is not change-specific, but it supports the practical importance of manager behavior in the employee experience [Gallup, 2015]. (news.gallup.com)

Checklist for the change manager

  • Defined the required adoption behaviors.

  • Agreed manager role expectations with sponsors.

  • Selected a small set of leading and lagging indicators.

  • Established baseline by team or segment.

  • Confirmed data sources and reporting cadence.

  • Briefed managers before measuring them.

  • Created a review forum with decision-makers.

  • Diagnosed root causes before assigning corrective action.

  • Documented support, owners, dates, and decision points.

  • Reviewed whether the measurement process itself is improving adoption.

Optional reusable worksheet: Manager Change Effectiveness Review

Manager/team:
​Change phase: readiness / pilot / rollout / stabilization / sustainment
​Expected adoption behavior:
​Evidence reviewed: usage, pulse, observation, quality, feedback, blocker log
​What is working:
​Gap or risk:
​Likely cause: awareness / desire / knowledge / ability / reinforcement / system blocker / capacity issue
​Corrective action:
​Support provided: coaching / job aid / sponsor escalation / peer mentor / workload relief / process fix
​Owner:
​Review date:
​Success measure:
​Decision if not improved: continue support / escalate blocker / redesign approach / formal HR process

References

Related Articles
Did this answer your question?