Why Change Programmes Fail at the Top — Not at the Front Line

Every enterprise transformation I've led starts the same way: the leadership team identifies resistance as the problem. "The frontline won't embrace the change," they say. "Middle managers are protecting their turf. People are comfortable with the old way."

After 30+ transformation mandates across 50+ countries, I can tell you that diagnosis is almost always wrong. The resistance isn't irrational. It's rational. People are watching. And what they're watching for is simple: does the leadership team actually believe this enough to change themselves?

When the answer is no—and it almost always is—everything that follows is noise.

The Myth of Frontline Resistance

Here's what I've observed consistently across mandates. When you survey a workforce about a change programme, the frontline doesn't say "I refuse to change." They say "I don't understand why it matters" or "I've seen this before and nothing changes" or, more damaging, "I see senior leaders still doing things the old way."

The last one is the killer. Because it translates to: "This change is for people below me, not for me."

I watched this at a pan-European bank I advised. €8 million transformation programme focused on customer-centricity. The problem, according to leadership, was that frontline advisors were still handling complaints slowly, still siloing information, still protecting their KPIs over customer outcomes.

Except the frontline advisors worked for a leadership team where each division head had completely separate P&Ls, where cross-functional projects required six sign-offs, and where the CEO measured executive bonuses on individual business unit performance. The frontline wasn't resisting customer-centricity. They were rationally reflecting the incentive structure their leaders had built.

The resistance you see is diagnosis of a different problem: a leadership team that hasn't aligned its behaviour with the change it's asking others to make.

Three Ways Leadership Teams Sabotage Their Own Programmes

This sabotage is rarely intentional. It's the result of three patterns I've seen repeat across continents and industries.

1. They Announce Transformation But Exempt Themselves

The new operating model applies to "the organization." But which parts exactly? When you start digging, the answer is: everywhere except where the decisions really get made.

I led a digital transformation at a telecom operator. New way of working: cross-functional squads, autonomous decision-making, fast iteration. Launched hard. Thousands trained. New tools, new structures, new language.

Then you'd walk into a leadership team meeting. Still seventeen decision-makers. Still a three-week approval cycle for anything meaningful. Still a CTO and CMO that barely spoke. The operating model applied to "the teams." Not to them.

The squads noticed. The squads had to iterate in days but wait weeks for leadership approval. So they stopped iterating. They waited for direction. The programme failed because the people asking for change hadn't changed the thing that was blocking change.

2. They Communicate the What and How, Never the Why It Matters to You

Most change communication is broadcast. "Here is what is changing. Here is how we will roll it out. Thank you for your patience during this transition."

That tells people what's happening. It doesn't tell them why they should care. And it definitely doesn't tell them what's in it for them.

A insurance company I worked with spent six months designing a shift to agile delivery. The communication said: "We are adopting agile practices to improve time-to-market." True. But for the individual claims adjuster or underwriter? The real message was: "You will have less stability, more meetings, and we have no idea how this affects your job security."

Nobody told them: "This change means your local team makes decisions faster, so you get feedback in days instead of months. This means you'll feel less stuck. This means when you identify a process problem, you'll be able to fix it without seventeen escalations."

The "why it matters to you" was real. But leadership never articulated it. So people filled the vacuum with their own narrative: "This is a cover for redundancies" or "This is management consultants selling methodology."

3. They Measure Activity, Not Behaviour Change

I've seen hundreds of dashboards tracking change programme metrics. Workshops delivered: 87%. Training completion rate: 94%. Change ambassador network: 356 people.

None of that means anything. Because what actually matters—did people change how they work?—is harder to measure. So leadership teams measure what's easy. Attendance. Completion. Deliverables shipped.

Then six months in, the programme declares victory. "Look at our engagement metrics. Look at our completion rates." And the business stays exactly the same.

I advised a financial services firm that ran a "customer-first culture transformation." By the metrics, it was a success. Thousands completed the training. Hundreds joined the transformation network. Engagement scores went up.

But the actual behaviour? Loan committees still took three weeks to approve anything. Sales teams still received bonuses for the number of products sold, not customer satisfaction. The email signature still said "Confidential and Proprietary." Every signal said: profits first, customer second.

The programme failed because leadership measured theatre, not change.

What Genuine Leadership Commitment Looks Like

I worked with a manufacturing company trying to shift from a command-and-control culture to participative leadership. The CEO sponsored it. The executive team approved it. Training happened.

Nothing moved until the COO—who had spent 25 years making every decision—stopped going to weekly tactical meetings with her team. She still owned the results. But she made the team's planning decisions for them, in advance, in writing. She asked questions instead of giving answers. She said "I don't know, what do you think?" in front of her peers.

That's when change started. Because the signal was: "The senior person I respect most is actually doing this differently."

Or the telecom I mentioned. The programme was stalling because the CTO and CMO couldn't align. They'd been rivals for twelve years. The CEO could have sent a memo. Could have commissioned a workshop. Instead, she did three things:

• Changed the incentive structure so the CTO and CMO shared one P&L
• Had them present together at the next all-hands—and required them to publicly name one assumption they'd been wrong about
• Made it clear: if they couldn't align on the transformation, they wouldn't be in those roles anymore

That changed the entire programme. Not because the communication improved. Because the power dynamics shifted.

The Communication Failure Inside Change Programmes

Most change communication misses one thing: it assumes people will move if they understand the logic. They won't.

People move when they trust the person asking them to move, when they see visible proof that person is actually moving, and when they understand what's in it for them—not the company, them.

Effective change communication requires three things.

First: Specificity. Not "we are becoming more agile" but "starting next month, you will have authority to decide technical approaches for your project without a review committee." That's specific enough that someone can imagine what it means.

Second: Honesty about what's hard. Every change costs something. Someone loses status, or autonomy, or a way of working they liked. The communication can't ignore that. It has to name it. "If we decentralize decision-making, we lose some consistency. Here's how we're accepting that trade."

Third: Visible leadership vulnerability. The leaders have to model what you're asking others to do. And they have to do it in front of witnesses. The CEO admits a mistake. The CFO says "I've been doing this wrong for years." The business unit head changes their decision-making in public, not in private.

I watched a retail company transform their supply chain. The COO could have said: "We're implementing a demand-driven model. Trust the data." Instead, she said: "For fifteen years I've overridden the demand forecast based on my gut. It worked maybe 40% of the time and cost us millions. I'm not doing that anymore. And I'm going to feel stupid the first time I trust the algorithm and it contradicts what I believe."

Her entire leadership team watched her do it. Not once, repeatedly. Within three months, the culture shifted. Because she made it safe to fail at doing things a new way.

The Test

Here's the single question that tells you whether a change programme will work:

"Could a frontline employee name one specific thing their direct leader has done differently in the last 30 days because of this programme?"

If the answer is no, the programme is theatre.

Not "my leader cares about the change." Not "my leader sent an email about it." One specific behaviour that's visibly different. My team lead now asks me what I think before they decide. My manager stopped checking in on progress daily. My director made a decision that went against their incentive because it aligned with the new values.

That specificity matters. Because it means the frontline isn't interpreting the change, they're observing it.

I ask this question in every engagement. In firms where the answer is "yes," change moves. In firms where the answer is "my leader attends the meetings," change stalls.

Change Is the Most Human Thing an Organisation Does

Every change programme I've led that succeeded shared one characteristic: the top moved first, visibly, and in ways that cost them something.

The CEO who stopped attending the meeting she'd chaired for ten years. The CFO who slowed down decision-making to let analysis inform rather than override. The board member who admitted the strategy she'd championed for five years was built on an assumption that wasn't true anymore.

That's not softer. It's harder. Because it requires leaders to be uncertain in public. To admit they've been wrong. To move at a pace that feels slower than they'd like.

But that's the deal. You can't ask people to change while you stay still. The resistance you see on the frontline isn't resistance to the change. It's a rational response to watching leaders who aren't willing to live by the rules they're making.

Change is the most human thing an organisation does. It's about identity, competence, status, autonomy. You can't delegate those conversations downward. They have to happen at the top first. And they have to happen not in words, but in behaviour.

The programmes that fail are the ones where leadership thought they could order change from above. The ones that succeed are the ones where leadership goes first.