How CMOs Should Manage Resistance to Change
Treat resistance as evidence to investigate, then build readiness through clarity, involvement, practical enablement, manager reinforcement, and accountability.
Five Principles for Managing Change Resistance
- Listen for the cause before defending the solution.
- Clarify business, team, and role-level impacts.
- Involve affected teams in workflow and rollout design.
- Remove capacity, capability, incentive, and system barriers.
- Reinforce adoption through managers, metrics, and consequences.
The Resistance-to-Readiness Process
| Step | What to do | Output | Owner | Timeframe |
|---|---|---|---|---|
| 1 | Listen to concerns and assess readiness by audience | Resistance and readiness map | Change lead | Before rollout |
| 2 | Diagnose awareness, trust, capability, workflow, capacity, and incentive causes | Root-cause assessment | CMO and managers | Within one week |
| 3 | Clarify outcomes, role impacts, expectations, and decision boundaries | Role-level change narrative | Executive sponsor | Before implementation |
| 4 | Involve teams, remove barriers, and provide practical enablement | Improved workflow and support plan | Process owners | During pilot and rollout |
| 5 | Reinforce behavior, monitor adoption, and address persistent exceptions | Adoption actions and decision log | Managers and governance council | Weekly, then monthly |
Build a Resistance-to-Readiness Loop
Resistance is a signal that the change design, message, or operating environment needs investigation. Begin by listening to affected employees, frontline managers, and cross-functional partners. Separate valid execution risks from uncertainty, habit, or preference. TPG identifies common causes including unclear strategy, fear of losing control or relevance, change fatigue, weak enablement, workflow friction, capacity constraints, data distrust, and incentives that reward old behavior.
Respond to the cause, not the symptom. Clarify why the change matters, what remains stable, what will change by role, and how success will be measured. Involve employees in process mapping, pilots, and retrospectives so legitimate concerns improve the design. Remove barriers such as conflicting priorities, missing skills, unreliable systems, or unclear ownership. Give managers role-specific messages, coaching guides, escalation paths, and time to reinforce the change.
Set clear expectations after support is in place. Use the new process and data in leadership reviews, align incentives and recognition, retire avoidable workarounds, and address persistent noncompliance consistently. Track concern resolution, manager reinforcement, adoption, proficiency, business impact, and reversion. Review resistance and adoption weekly during rollout, then monthly until the new behavior is stable.
Source: pedowitzgroup.com, 2026; prosci.com, 2025; mckinsey.com, 2025
TPG Point of View
Use a Resistance-to-Readiness Loop - listen, diagnose, clarify, involve, enable, reinforce, and sustain.
Why TPG? TPG reports completing 100+ B2B transformations with 3x average pipeline improvement.
Change Resistance and Adoption Metrics
| Metric | Formula | Target/Range | Stage | Notes |
|---|---|---|---|---|
| Readiness coverage | Employees completing role-impact review / employees in scope | Increasing to full coverage | Preparation | Segment by audience |
| Concern resolution | Valid concerns resolved by due date / concerns due | High and improving | Response | Publish owners and status |
| Manager reinforcement | Managers completing required coaching / managers in scope | Increasing to full coverage | Enablement | Verify quality, not attendance |
| Adoption rate | Users performing the required new behavior / users in scope | Increasing to approved threshold | Behavior | Define meaningful adoption |
| Reversion rate | Eligible work completed through the old path / eligible work | Declining toward zero | Sustainability | Investigate approved exceptions |
Frequently Asked Questions
Teams may resist because the purpose is unclear, previous changes lacked follow-through, roles or status feel threatened, workflows are impractical, capacity is limited, or incentives still reward the old behavior.
Yes, when their concerns can improve workflow design, risk controls, enablement, or sequencing. Involvement should inform the solution without giving every stakeholder veto power over required outcomes.
Managers translate enterprise change into role-level expectations, answer personal-impact questions, coach new behaviors, surface barriers, and reinforce accountability through daily work.
It becomes a performance issue after expectations are clear, support and resources are available, legitimate barriers are addressed, and an employee still refuses or repeatedly avoids required behaviors.
Track readiness, concern resolution, manager reinforcement, meaningful adoption, proficiency, process compliance, sentiment themes, reversion, and the business outcome the change is expected to improve.