There’s a version of transformation projects that exists in presentations. Clean timelines. Aligned stakeholders. Confident decisions made by calm, reasonable people in well-lit rooms.
And then there’s the version I actually live in.
The Real Work Nobody Puts in the Deck
I’m currently running a large transformation programme — multiple parallel workstreams, teams across Europe, development offshore in Asia. On any given day I move between different accents, different communication styles, different cultural expectations. All in English, but not the same English.
The words are the same. The meaning behind them often isn’t.
What still surprises me, even now, is how little of this work is actually about delivery, architecture, or budgets. Most of it is about interpretation. Not language interpretation — emotional interpretation.
You learn to read the signals. The polite silence that means disagreement. The long explanation that’s really hiding uncertainty. The constant agreement that doesn’t mean commitment. The hesitation that tells you someone is uncomfortable, but they’ll never say it directly.
At some point you realise you’ve quietly become the global translator of emotional nuance. And honestly? I’ve made peace with that part.
When Clarity Meets Resistance
What’s harder is what happens when the project needs to move and the team isn’t ready to move with it.
In large offshore setups, there’s often a deep need for certainty before action. Every scenario defined. Every dependency confirmed. Every edge case answered before anyone touches anything.
In theory, that sounds responsible. In practice, transformation doesn’t work like that. You have to move with incomplete information. You have to test, adjust, decide in motion. And not everyone is comfortable with that — not because they aren’t capable, but because ambiguity feels risky when accountability is high and trust is still being built.
When people aren’t confident, they protect themselves by asking for more clarity. When mistakes feel costly, decisions get avoided. When accountability feels exposed, process becomes the shield.
Early in my career, this frustrated me. Now I see it for what it is: a signal, not a flaw. My job becomes less about pushing harder and more about creating enough direction that people feel safe enough to move.
The Assertiveness Trap
Sometimes that means being very direct. Writing the kind of email nobody particularly enjoys receiving. Having the conversation that clears the air even when the air was comfortable to breathe in.
And here’s where it gets interesting: assertiveness doesn’t land the same way everywhere.
In some cultures, directness signals efficiency and respect. In others, it can feel personal, confrontational, or threatening — especially when it comes from someone they didn’t expect to be that firm. The pushback rarely comes as open disagreement. It shows up as delays, side conversations, new problems materialising from nowhere.
For a long time I asked myself: is this about gender? Hierarchy? Culture? Probably all three, sometimes. But more often I’ve come to think it’s about confidence. People who trust their own skills don’t need endless clarification to get started. People who are secure in their work don’t need drama to feel in control. People who are comfortable with responsibility don’t freeze when the path isn’t fully defined.
Transformation projects expose all of that. They force people outside routine, outside certainty, outside the comfort of doing things the way they’ve always been done.
That’s exactly why they’re so hard to run. Not because the systems are complex. Because people are.
What I’ve Stopped Trying to Do
I’ve stopped trying to remove the tension. It’s not removable. The goal isn’t a frictionless project — it’s staying steady inside the friction.
Be clear. Be fair. Be direct when it’s needed. And stop absorbing every reaction as though it’s a verdict on you personally.
Some days I manage that well. Other days I close my laptop feeling like my brain has been in five countries simultaneously. But every project like this reinforces the same thing:
Leading transformation isn’t about controlling everything. It’s about holding the chaos without becoming chaotic yourself.
Three Things That Actually Help
These aren’t frameworks. They’re just what I’ve found works — in practice, not in theory.
1. Name the ambiguity out loud, early. Don’t let uncertainty become a silent source of anxiety for your team. Say it directly: “We don’t have full clarity on X yet, and here’s how we’re going to move anyway.” It doesn’t eliminate the discomfort — it normalises it. Teams that know ambiguity is expected cope with it far better than teams who feel like it’s a sign something has gone wrong.
2. Separate the signal from the noise in pushback. Not all resistance means the same thing. Some of it is cultural communication style. Some is genuine concern. Some is fear dressed up as process. Before reacting, ask: what is this person actually trying to tell me? The answer changes how you respond — and whether you need to push back or build more safety first.
3. Protect your own steadiness like it’s a deliverable. In a programme that runs on your ability to hold things together, your clarity is not a luxury — it’s infrastructure. That means knowing when to step away from the screen, when to stop replying to that email tonight, when to simply let the day end without resolution. You cannot lead well from a state of constant depletion. The project needs your best thinking, not your most exhausted reaction.
More on this as the programme unfolds — the small wins, the moments that test everything, and what I’m learning about leading under pressure in real time.