The 40-Country Playbook: What Makes Transformation Actually Stick

I've watched transformation programmes across 40+ countries, dozens of Fortune 500 organisations, and probably 200+ major initiatives. Most fail. Not dramatically — they don't crash and burn in six months. They limp along into year two, get quietly defunded, and by year three everyone's pretending it never happened. The pattern is so consistent it stopped being surprising around country seven.

The reason isn't what you think. It's not that the strategy was wrong, or the organisation wasn't ready, or people "resisted change." Those are all excuses. The real issue is simpler and more fixable: transformations are architected like projects instead of like leadership systems. And that distinction is the difference between something that sticks for a decade and something that evaporates the moment budget pressure hits.

The Pattern Nobody Talks About: Why Year Two Is Where Transformations Die

Everyone focuses on year one. "We're launching transformation." Budgets get approved. A transformation office is set up. A global programme manager is hired. There's a kickoff. People get excited, or at least they perform excitement in town halls.

Year one works. It has to, because everyone's watching. The CEO is committed. Budget is available. There's novelty and urgency. New initiatives launch smoothly because they're not competing against embedded ways of working yet. You can claim wins because you haven't hit the muscle memory of the organisation.

Year two is where the organisation's real shape emerges. The novelty fades. Budget gets tighter. Quarterly targets start pushing back against "transformation activities." And here's the part nobody plans for: the leadership team goes back to doing what they've always done, because the transformation office was supposed to "own" the change.

By year two, I've seen:

• Transformation offices becoming internal consultancies — busy running programmes that have zero impact on how the business actually operates
• New ways of working existing in parallel with old ways, giving people the worst of both systems
• Leadership saying they're committed while allocating zero time to actually modelling the behaviours they're asking everyone else to adopt
• Measurement systems that track "completion" of training or "adoption" of a new tool, while the actual operating model hasn't changed by a millimetre
• The organisation running transformation initiatives AND the old system simultaneously, doubling workload until people just stop participating in the new one

This happens because the fundamental architecture is wrong. Transformation was treated as a project to be executed, not as a leadership system to be embedded.

A CEO saying "we're transforming" is not leadership. A CEO saying "here's what we're stopping" and then actually stops doing it — that's leadership.

The Leadership Architecture Problem: Sponsorship Is Not Leadership

Most organisations confuse executive sponsorship with transformation leadership. They're almost opposite things.

Sponsorship is passive. A sponsor approves budget, shows up to steering meetings, removes blockers when escalated. They delegate the actual work. That's useful, but it's not leadership.

Leadership is active. It's modeling the behaviour. It's making visibly different decisions. It's doing the thing you're asking everyone else to do before anyone else does it. And then doing it again. And again, until people stop noticing it's different because it's just how the leadership team works now.

Here's what I've seen separate the organisations where transformation actually sticks:

The leadership team adopts the new operating model first, completely, before asking anyone else to. Not in principle. Not rhetorically. Operationally. If you're moving to agile, the leadership team runs on two-week sprints and retros before the first team outside that room does. If you're moving to a customer-centric operating model, the CFO is sitting in customer calls, not just approving the budget for a customer office. If you're implementing AI decision frameworks, the leadership team uses them for actual decisions in their own meetings.

This is uncomfortable. It takes longer. The first month of leadership team sprints is messy and inefficient. But that inefficiency is the point. Because it means the leadership team actually understands what they're asking for. They hit the obstacles first. They have to solve them. And when the organisation watches the leadership team doing something new and hard and staying with it, people believe it's real.

In the organisations that failed, the leadership team had a separate decision-making system. They talked about "empowerment" in town halls while centralising decisions upward. They claimed to be "agile" while planning quarterly with 18-month cycles. They said "we're digital-first" while still printing board packs. The organisation watched this, understood the real rules, and optimised for the old system underneath.

The contrast-box that follows isn't theoretical. These are both things I've lived through:

What "Sticking" Actually Requires: Three Non-Negotiable Elements

I've seen enough transformations that didn't stick to know the three things that separate the ones that do. Not three out of ten. Not three things that help. Three things that have to all be true.

1. The change has to be anchored in operating model, not initiative

An initiative is something you do. You run a programme, you train people, you launch a tool, you measure adoption, you declare victory. Then you move on to the next initiative and the previous one collapses because it had no structural foundation.

Operating model is how the organisation actually makes decisions and gets work done. It's the meetings you have, the rhythm of those meetings, what information you bring, who decides, what happens after. Most organisations never actually change their operating model. They layer new initiatives on top of it and wonder why nothing sticks.

Real transformation means: "This is how we make these kinds of decisions now. This is when we make them. This is who's in the room. This is what we measure. This is how we escalate. And we do it this way every time, not just on transformation projects." That's operating model. Once it's embedded, it doesn't require ongoing initiative energy because it's just how you work.

I worked with a financial services organisation that wanted to move faster. They were blocked by slow decision-making. They implemented agile. But they didn't change the operating model. They still had monthly budget cycles. They still had five levels of sign-off. They still had 90-day planning. Agile teams were trying to move at two-week sprints while the rest of the organisation locked their decisions in place every 90 days. Within 18 months, the agile teams were slow again because they had to fit inside the operating model of the company.

The organisations where I've seen speed actually stick changed the entire operating model. Decision authority moved closer to execution. Planning cycles shortened. Sign-off got simplified. Budgets got allocated differently. The rhythm changed at every level, not just within the transformation office.

2. The leadership team has to model it before asking anyone else to

I've already covered this, but it's worth isolating because it's the most-violated rule. Modelling is not optional. It's not nice to have. It's foundational. People don't believe what you say; they believe what you do when no one's watching.

I worked with a pharma company introducing more distributed decision-making. The head of R&D kept centralising decisions that the new operating model said should be distributed. His teams watched him do it. They learned the real rule: call it distributed, but escalate everything upward anyway. So they did. And the programme failed because the leadership team wasn't actually living it.

He eventually understood. When I asked him why he was doing it, he said: "I don't trust their decisions." So we didn't actually transform. We just pretended. The transformation office ran its programmes, the company showed progress in surveys, but nothing changed.

The organisations where transformation sticks are the ones where leadership genuinely believes in the new operating model enough to use it even when it's slower, even when it's wrong and they have to live with those consequences. The visible acceptance of short-term inefficiency for long-term structural change is what makes people believe it's real.

3. Measurement has to track behaviour change, not activity completion

This is where most programmes fail silently. They measure everything except what matters.

I see transformation offices tracking: "How many people completed training? How many teams went through the change programme? How many tools are deployed? What adoption rate on the new system?" All activity measures. All easily gamed. All meaningless if the operating model hasn't actually changed.

The measures that actually matter track whether the new way of working is how people actually work:

• What percentage of decisions are made in the new rhythm, not escalated upward? (Not "did we train people on distributed decisions," but "are decisions actually distributed?")
• How many problems get solved at the level where they occur, versus escalated upward? (This tells you if empowerment is real or rhetorical.)
• Has the leadership team's decision-making cycle changed? (If your C-level is still planning quarterly but you told everyone else to be monthly, you haven't transformed.)
• Are people actually using new tools because they're better, or are they using them in parallel with old tools because the old way still works? (Parallel systems mean nothing stuck.)
• Has the allocation of time from leadership shifted? (If leaders spend the same percentage of time on new operating model stuff as they do on old, the old is still winning.)

Real measurement is harder because it requires you to observe how people actually work, not survey them about their intentions. But that's the only data that matters. Everything else is noise.

The Governance Trap: Why Most Transformation Offices Fail

Transformation offices are usually set up to create control. There's a PMO, there's a steering committee, there's a roadmap, there's governance. And all of it creates the illusion of control while producing the conditions for failure.

Here's what I've seen happen: A transformation office is created as the hub of control. All initiatives flow through it. It has a central roadmap. Every workstream reports into it. There's a single steering committee that governs everything. And what this actually does is centralise the change when the whole point of transformation is to distribute how the organisation works.

The best governance model I've seen is inverted. Instead of the transformation office controlling the change, it coaches the operating model change in each part of the business. The steering committee doesn't oversee programmes; it oversees whether the organisation's actual operating model is changing. It's obsessed with: "Are we actually making decisions faster?" not "Did the project hit its timeline?" It measures whether leadership is visibly different, not whether initiatives are on track.

The transformation office in that model becomes much smaller. It has subject matter expertise, not programme control. It helps teams understand what distributed decision-making looks like. It helps design the new operating model. It coaches leaders through modelling the change. But it doesn't control the roadmap. The business does.

This is scary for organisations used to centralised control. But it's also the only model I've seen that prevents year-two collapse. Because if the business owns the change, the business continues it when the transformation office winds down. If the transformation office owns it, it collapses when the office gets defunded.

The question that separates transformation success from failure isn't "What will we add?" It's "What will we stop doing?"

The Subtraction Question: The Difference That Actually Matters

Almost every failed transformation I've watched added new ways of working without subtracting the old ones. You got training on the new system but still had to use the old one because decisions that were made in the old system still needed to flow through old channels. You adopted a new planning rhythm but the quarterly financial reviews still happened the old way. You empowered teams to make decisions but escalation was still the default path because the leadership team hadn't changed.

Transformation that sticks requires subtraction. Not just addition. And subtraction is the one thing I've rarely seen organisations willing to do, because it requires someone to stop doing something they've always done.

When I ask leadership teams "What will you stop doing?" the silence is usually long. Someone eventually says "Nothing, we need it all." And then I know the transformation probably won't stick. Because if you're not stopping anything, you're not actually changing. You're just adding on top. And the organisation will optimise for the old system because it's easier, it's proven, and the new system is just extra work.

The organisations where transformation works are the ones willing to say: "We will stop having this meeting. We will stop requiring this approval. We will stop planning on this cycle. We will stop escalating this type of decision. We will stop measuring this metric." And then they actually stop. They create friction to doing it the old way.

This is what separates real transformation from initiative theatre. Any organisation can run a transformation programme. But organisations that actually change are ones that stop something old so systematically that the new way becomes the only feasible way to work.

I worked with a logistics company that wanted to move to real-time operations instead of batch overnight runs. They designed the new system. But they kept running the batch system in parallel because it was "safer." For 18 months they ran both. People used whichever was convenient. The new system never became the standard because the old system was still available. When they finally turned off the batch system, suddenly everyone learned the new one in weeks because they had to. The parallel system had been the blocker all along.

The Challenge: What You Actually Have to Do

If you're leading transformation right now, here's what this actually means:

First: Stop measuring activity. Measure whether your operating model is actually different. Are decisions getting made differently? Are people working at different rhythms? Is leadership modelling something new? That's all that matters. Everything else is noise.

Second: Make your leadership team change their own system first, completely, before asking anyone else to move. Not halfway. Not in rhetoric. In daily, visible, operational reality. When your CEO does a retro on a decision her team made last week, when your CFO sits in customer calls, when your head of ops runs on two-week cycles — people believe. Until then, it's theatre.

Third: Anchor the change in your operating model, not in initiatives. Ask yourself: "How do we make this decision? Who's in the room? When do we make it? What information do we bring? What happens after?" If you can't answer those questions with the new way of working as the standard rhythm, you haven't transformed. You've launched a programme.

Fourth: Create explicit subtraction. Not "we'll reduce" or "we'll streamline." Actual deletion. "We are stopping this meeting. We are stopping this approval. We are stopping this planning cycle." Write it down. Monitor that it stops. Because if you don't actively delete the old way, the organisation will maintain both systems in parallel until the old one wins by weight of habit.

Fifth: Invert your governance. Your steering committee should obsess over whether your operating model is changing, not whether your initiatives are on track. Your transformation office should coach, not control. The business should own the roadmap. If the business owns the change, the business continues it when the transformation office closes.

This is not a consulting engagement. This is a leadership re-architecture. It takes time. It requires leaders to be visibly uncomfortable with new ways for months. It requires saying no to quick wins that reinforce the old system. It requires having the discipline to keep measuring the right thing when the wrong measurements are easier.

But it's also the only approach I've seen that produces transformation that actually sticks beyond year two. And at the scale you're operating, year two is where everything really matters.