Fragile office meeting?

The Change Initiative No One Asked For

How to move organisations forward without losing the people inside them.

Most change initiatives fail.

Not because the solution is wrong. Because we treat people like software updates.

‘Push the code. Reboot. Expect improvement.’

Except people don’t work that way.

The failure rate is consistent across industries and geographies. McKinsey puts it at roughly 70%. Harvard Business Review says 70-95%. Kearney’s 2025 study found 83% miss targets. BCG’s global research shows only 26% of transformations create lasting value. The numbers vary by methodology, but the direction is clear: most change efforts do not achieve what they set out to achieve.

The reasons are surprisingly consistent across continents: employee resistance, weak management support, poor communication, and organisational fatigue.

Here is what I have learned about why that happens—and what to do about it.

Change Is Loss

When a team’s workflow changes, something dies.

Not a person. But a way of being. Familiar routines. Established relationships. A sense of competence that took years to build. An identity tied to expertise and belonging.

Researchers have documented this for decades. Hobfoll (2002) showed that loss during organisational change is directly tied to psychological resources. The Kübler-Ross grief model has been adapted to organisational change—denial, anger, bargaining, depression, acceptance. What looks like resistance is often grief.

The World Economic Forum published research stating: “Change has little chance of success unless the severity of loss is acknowledged, grief is enfranchised and mourning is encouraged.”

De Klerk (2025) put it plainly: “Organizations need to be concerned about emotional trauma, grief and mourning when enacting change.”

If your team is acting indifferent, they are not broken. They are grieving. And they are rational. They have watched three other “transformations” come and go without improving their daily reality. Why would this be different?

The Only Two Problems

Every stalled change has the same root cause. Not “bad communication.” Not “lack of buy-in.”

One of two things:

1. They don’t feel the heat. The threat is abstract. “Market headwinds” does not keep anyone up at night. The local cost of changing feels higher than the local cost of keeping still.

2. The system is physically rigged to say no. Approvals take weeks. The old habit is easier. “That’s how we’ve always done it” is not stubbornness. It is physics.

Pick which one you are dealing with. Do not try to fix both at once. You will burn out your best people and the change will die anyway.

Two-thirds of executives cite resistance to change as their biggest obstacle. Eighty-four percent say change management is critical, but only 13 percent feel their organisations actually excel at it. The gap between intention and capability is enormous.

The Cultural Dimension

The principles are universal. The delivery is not.

The experience of loss and grief during change is human, not Western. Research from Brazil found that “ruptures required in changes can be perceived as a symbolic death” generating “bereavement.” Studies from Saudi Arabia, Europe, and global contexts confirm the same pattern.

But how resistance and grief manifest—and how you should respond—varies significantly across cultures.

In high uncertainty avoidance cultures (Japan, Germany, France, South Korea), resistance often looks like quiet anxiety rather than open confrontation. People comply outwardly while experiencing internal distress. Acknowledge the loss formally and respectfully—through structured meetings, written communications, or one-on-one check-ins, not casual hallway conversations.

In collectivist cultures (China, India, Southeast Asia, Latin America), resistance is often group-level, not individual. People may be too polite to express concerns openly. When surfacing blockers, do so anonymously or through group consensus rather than calling out individuals, which can cause loss of face.

In high power distance cultures (Middle East, parts of Asia, Latin America), centralised authority is expected and respected. Rather than trying to bypass decision-makers, influence them. Map the approval chain. Present data. Ask for their help in streamlining. The structure stays intact. The friction decreases.

In individualist cultures (USA, UK, Australia, Northern Europe), more direct and informal approaches work well. The same advice applies, but the tone can be conversational and the pace faster.

The “what” holds. The “how” adapts.

The Objections, Addressed Honestly

“I don’t have time for prototypes or sprints.”

Fine. Take one broken process. Three people. Four hours. Break it on purpose and rebuild it fast.

This is not a workshop. It is a dissection. Find the specific rule, approval, or habit that kills momentum. Kill that one thing. Document it. Move on.

If you cannot find four hours, your change is not a priority. Admit that. Stop wasting everyone’s energy.

“I can’t give away authority. Compliance and legal exist.”

Yes, they do. You probably cannot give frontline staff veto power over contracts. That is reality.

What you can do is map the approval chain. Write down every step and the average wait time. Publish it. Then ask each approver one genuine question: “If we miss our deadline because we are waiting on you, is that a risk you want to explain to the board?”

Sometimes the fastest route to decentralisation is just making the bottleneck visible.

“I don’t get paid enough to care about this rollout.”

Honest. And fair. Change usually means more work for the same pay. You cannot argue someone out of that.

So stop arguing. Make the ask smaller. Do not ask them to “embrace the vision.” Ask them to test one new thing for one week. Promise that if it makes their day worse, you will roll it back personally.

Offering a genuine off-ramp is not weakness. It is the only honest contract you can make with someone who has been burned before.

“This is just repackaged [insert methodology].”

Maybe. But that methodology did not fix your culture, did it?

This is not about ceremonies or frameworks. It is about one thing: does the person who needs to make a decision have the information and permission to make it? If not, nothing else matters.

What Actually Works

Three things. No jargon.

1. Acknowledge the loss.

Before you ask people to adopt the new way, name what they are leaving behind. “I know this process has been part of how you work for years. It is okay to feel frustrated that it is changing.”

This is not weakness. It is the foundation of trust.

Research confirms: sharing and validation destigmatise loss. When grief is acknowledged, people can begin to move through it rather than resist from within it.

2. Build the ugly version today.

Do not wait for the perfect strategy. Put something broken in front of people and let them tear it apart. The feedback you get is worth ten planning sessions.

This is not about delivering a polished product. It is about testing assumptions cheaply and quickly.

3. Name the blocker.

Somewhere in your organisation, there is a person or a rule that is killing momentum. Find it. Call it out. Do not blame them personally—just make the cost of the delay visible.

You would be surprised how quickly things move when everyone can see the bottleneck.

A Quick Reference

If you diagnose… Your primary move Your secondary move
Low urgency Make the cost of not changing tangible. Share real data on churn, risks, or missed opportunities. Set a public, achievable deadline with visible tracking.
High inertia Map the approval chain and its wait times. Share it widely. Ask each approver: “If we miss our deadline because of this wait time, is that acceptable?”
Both Run a focused “dissection” of one broken process. Fix that one thing. Build a cheap prototype of the new approach and test it in a low-risk area.

A Quiet Note on Inspiration

Fragile office meeting?

A small, underfunded unit in WWII called WATU achieved remarkable results with almost no resources. They had no budget, no authority, and a hostile hierarchy above them. They succeeded by testing cheap prototypes on a wooden floor and giving frontline people permission to act without calling London for approval.

The lesson is not about warfare. It is about constraints. They are not an excuse to wait. If you have no budget, prototype with paper. If you have no authority, test in the one corner of the business that trusts you.

One Last Reality

You might do all of this and the change still fails.

That is fine. Failure is data. It tells you which parts of your organisation are structurally unchangeable. That is valuable intelligence. It saves you from running the same doomed initiative next quarter.

Sometimes the most useful outcome is finding out, cheaply and quickly, that something cannot be done. That knowledge is worth the price of admission.

Go gently. Go practically. Go with the grain of your context, not against it.

Sources