Why Senior Executives Don’t Understand Change Management

Let’s be honest. Most senior executives don’t hate change management.

That would at least suggest they’ve thought deeply about it.

The bigger problem is quieter and, in some ways, worse: many executives simply don’t understand what change management is for. They tolerate it. They fund it reluctantly. They mention it in steering committees. They ask whether “the comms are ready.” They nod when someone shows a stakeholder map. They request training completion figures. Then, when adoption fails, they wonder why people are so resistant.

Well, here’s the awkward part.

People are not resistant to change management. They are resistant to poorly understood change, weak sponsorship, contradictory incentives, bad timing, vague accountability, and solutions designed as if employees were installation endpoints.

Change management gets blamed for the mess, but it is usually brought in after the mess has already been designed.

In large transformations—ERP, CRM, AI, operating model redesign, shared services, digital planning, data governance—the gap between executive understanding and change reality becomes painfully visible. Senior leaders often see strategy, benefits, milestones, budget, and risk. Employees see disrupted routines, lost autonomy, unclear roles, new tools, extra work, and managers who are not sure what to say.

Both views are real. Only one usually gets a steering deck.

That is where the problem begins.

1. They Think Change Management Means Communication

Ask many executives what change management does and you’ll hear some variation of this: “making sure people are informed,” “getting the message out,” “managing resistance,” “preparing training,” or the dead giveaway—”landing the change.”

Landing the change. As if transformation were a small aircraft and employees were a runway.

Communication matters, obviously. Without it, people invent their own explanations, and those explanations are usually darker, funnier, and more contagious than anything produced by the programme team. But communication is not adoption. It is not commitment. It is not behaviour change. It is not readiness. It is not capability.

A newsletter can announce a new ERP process. It cannot make a procurement manager stop using the old workaround when the new approval flow slows down urgent purchasing. A town hall can explain the AI strategy. It cannot make a legal team trust generative AI outputs in a regulated process. A beautifully designed FAQ can reduce confusion. It cannot repair a broken incentive system.

This is the first executive misunderstanding: they confuse message delivery with behavioural movement.

Good change management does communicate, yes. But that’s the visible part. The less glamorous work sits underneath: impact assessment, stakeholder analysis, readiness diagnostics, manager enablement, role clarity, resistance analysis, training design, adoption measurement, reinforcement, feedback loops, hypercare, and sometimes the politically unpleasant task of telling leaders that their plan is not adoptable in its current form.

That last part is where the room gets cold.

2. They Want Adoption Without Disturbance

Many senior executives say they want transformation. What they often mean is: better results, faster processes, cleaner data, lower cost, more transparency, and a workforce that adapts without making too much noise.

It’s a lovely fantasy. Very popular.

Real change disturbs. It shifts power. It exposes bad process discipline. It makes informal work visible. It takes away local exceptions that people have defended for years. It forces managers to have conversations they previously avoided. It asks employees to trade familiar inefficiency for unfamiliar control.

In software and AI programmes, this disturbance is not a side effect. It is the work.

A CRM programme that improves pipeline transparency may also reduce the ability of sales teams to hide weak opportunities. An ERP rollout that standardises processes may reduce local autonomy. An AI implementation that improves productivity may raise questions about job design, expertise, accountability, and surveillance. A new operating model may clarify ownership, which sounds harmless until people realise that clarity also removes plausible deniability.

Executives often underestimate this because they experience the change as intent. Employees experience it as consequence.

Intent is clean: improve customer experience, harmonise processes, modernise capabilities, use data better.

Consequence is messier: my approval rights changed; my spreadsheet is banned; my team has to enter data we don’t trust; my manager now sees my backlog; my old expertise matters less; my workload just increased during transition; my bonus still rewards the old behaviour.

Change management lives in that gap. Senior executives often don’t.

3. They Outsource Sponsorship to the Change Team

Here’s a small corporate tragedy: executives ask change managers to “drive adoption” while the leaders themselves continue behaving as if the change were optional.

They skip key meetings. They delegate messages to programme managers. They approve one thing in steering and tolerate another in their functions. They say the new process is mandatory, then accept exceptions from powerful stakeholders. They ask for adoption metrics but don’t use them in performance conversations. They praise transformation in public and protect old habits in private.

Then they ask why resistance is so high.

Sponsorship is not a signature on a charter. It is not a launch speech. It is not appearing in a video with gentle background music.

Sponsorship is repeated, visible, uncomfortable behaviour by leaders who make the change safer, clearer, and harder to ignore. It means making trade-offs. It means refusing old reports. It means asking managers why adoption is low. It means defending the new operating model when the first important person asks for an exception. It means absorbing political heat instead of letting middle managers become the shock absorbers of executive ambiguity.

Change managers can support sponsorship. They cannot substitute for it.

This is maybe the most important thing senior executives misunderstand. They think change management is a function that manages change on behalf of leadership. It isn’t. Change management is a discipline that helps leadership make change possible.

Leadership still has to lead.

Annoying, I know.

4. They Prefer Activity Metrics Because Outcome Metrics Are Inconvenient

Executives like numbers. Until the numbers become too revealing.

Change management is often asked to report activity: number of communications sent, training attendance, stakeholder sessions completed, champions appointed, FAQs published. These metrics are easy to count. They also make programmes look busy, which can be politically useful.

But activity is not impact.

A thousand people can attend training and still be unable to perform the new process. A champion network can exist on paper and have no influence in the business. A manager cascade can be delivered and still leave managers confused. A sentiment survey can show cautious optimism before go-live and collapse two weeks later when users meet the actual system.

Results-oriented change management asks harder questions. Are people using the new tool correctly? Are transactions flowing through the standard process? Are managers reinforcing the new behaviour? Are old workarounds decreasing? Is data quality improving? Are adoption gaps concentrated by region, role, team, or process? Are benefits materialising because behaviour has changed, or are we just hoping they will?

This is where executives sometimes become strangely less enthusiastic about measurement.

Because adoption data can expose uncomfortable truths. Maybe the solution is poorly designed. Maybe the timeline was unrealistic. Maybe the sponsor coalition is weak. Maybe one region was never aligned. Maybe the business case assumed behaviour that no one has seriously enabled. Maybe the problem is not “resistance,” but executive impatience dressed up as ambition.

A good change dashboard is not a decoration. It is a mirror. Not everyone enjoys mirrors.

5. They Don’t See Middle Managers as the Real Adoption Infrastructure

Senior executives often communicate over the heads of middle managers and then expect those same managers to make the change stick locally.

This is unfair and ineffective.

Middle managers are where transformation becomes credible or dies slowly. They translate abstract strategy into team priorities. They decide what gets attention in weekly meetings. They answer practical questions. They sense resistance early. They know who is struggling. They know which process changes are fake, which are painful, and which are quietly brilliant. Employees often trust them more than central programme teams.

Yet in many transformations, middle managers are briefed late, overloaded with generic slide packs, and expected to cascade messages they did not help shape. Worse, they may be personally conflicted. The change may reduce their autonomy, alter their metrics, expose their team’s performance, or demand time they don’t have.

So they comply, politely. Which is not the same as leading.

Executives underestimate this layer because they mistake hierarchy for transmission. They assume that if a message is sent down, it lands intact. It doesn’t. It is interpreted, filtered, softened, delayed, mocked, adapted, resisted, or ignored—depending on local context and managerial belief.

Change management understands this. Or should.

That is why manager enablement is not a nice extra. It is core infrastructure.

6. They Treat Resistance as a Personality Problem

Senior leaders sometimes speak about resistance as if it were a character flaw among employees who “don’t get it.”

Occasionally, yes, people resist because they are protecting comfort, status, or old privileges. Let’s not romanticise every objection. Some resistance is political. Some is lazy. Some is theatre.

But much of it is signal.

Resistance may mean the purpose is unclear. Or the process is unworkable. Or the change creates extra work in one function while benefits appear in another. Or the system removes flexibility that customers still demand. Or the adoption ask conflicts with incentives. Or employees have survived five previous “strategic transformations” that disappeared after leadership changed.

In other words, resistance often tells us where the design, governance, or trust is weak.

Executives who don’t understand change management want resistance reduced. Executives who do understand it want resistance interpreted.

That difference is enormous.

If resistance is just noise, the response is persuasion. If resistance is data, the response is diagnosis. Sometimes the solution is communication. Sometimes it is training. Sometimes it is process redesign. Sometimes it is a leadership decision. Sometimes, awkwardly, the resistors are right.

Not always. But more often than steering committees enjoy admitting.

7. They Forget That Transformation Competes With Daily Work

From an executive level, transformation is a strategic priority. From the employee level, it is one more demand arriving on top of customer issues, reporting deadlines, operational firefighting, hiring gaps, audits, system problems, and the low-grade fatigue of modern organisational life.

Executives see the portfolio. Employees feel the pile-up.

This is why capacity matters. Not as an excuse, but as a condition for adoption. People cannot properly test a system, learn a new process, clean data, attend workshops, support colleagues, and continue business-as-usual at full speed without something breaking. Usually the thing that breaks is quality. Or trust. Or the change itself.

Senior leaders often underestimate transition load because they focus on end-state efficiency. They see the future benefit and discount the temporary burden required to reach it. But temporary burdens are where adoption is won or lost.

If the organisation does not create capacity for change, employees will create capacity themselves—by skipping training, ignoring communications, delaying data cleanup, using workarounds, or waiting until the programme becomes someone else’s problem.

That isn’t irrational. It is survival.

How to Fix It

Senior executives don’t need to become change managers. That would be unnecessary, and possibly dangerous. The world has enough executives with half-understood frameworks.

But they do need to understand what change management is actually for.

It is not corporate decoration. It is not internal marketing. It is not “soft stuff.” It is not a polite name for training. It is not the department that makes resistance go away.

Change management is the discipline that turns strategic intent into adopted behaviour. It tests whether the organisation is ready, willing, able, and reinforced enough to work differently. It connects executive ambition with operational reality. It tells leaders where their transformation is not yet believable.

So here’s the executive checklist, stripped of ceremony.

Say the real thing. Don’t dress disruption in cheerful nonsense. If the change reduces autonomy, say so. If it increases transparency, say what that means. If there will be trade-offs, name them.

Sponsor the change with behaviour, not slogans. Use the new metrics. Ask about adoption. Stop accepting old-process outputs. Challenge exceptions. Show up after kick-off.

Measure the right thing. Not only activity. Adoption. Proficiency. Data quality. Behavioural use. Process compliance. Workaround reduction. Benefit realisation. Confidence. Manager reinforcement.

Respect middle managers. Bring them in early. Equip them properly. Listen when they say the plan does not fit operational reality.

Treat resistance as information before treating it as opposition.

And perhaps most importantly: involve change management before the solution is frozen and the timeline is politically untouchable.

By then, the change team may still help. Good people often do heroic things late in bad programmes. But the opportunity to shape adoption has already narrowed.

Senior executives don’t misunderstand change management because they are foolish. They misunderstand it because, from the top, change looks cleaner than it is. Strategy has edges. Roadmaps have logic. Benefits have numbers. People, unfortunately, have memories, incentives, fears, habits, loyalties, and jobs to do.

That is not a barrier to transformation.

That is the transformation.

For more on how sponsors and executives shape adoption outcomes, browse the transformation leadership articles.