The Gap Between Announcing Transformation and Actually Doing It

There's a meeting I've been in more times than I can count over thirty years in property and construction. The setting changes — a boardroom in Sydney, a project office in Hong Kong, a program review on one of the largest developments in the world — but the meeting is always the same.

The schedule is on the table. The data is in front of everyone, and the data says the date cannot be met. This isn't controversial in the room — by any honest reading of progress, the timeline attached to the ambition is not achievable, and the capable people around the table know it. So the moment arrives. The evidence has been acknowledged. And you think: good. Now we'll have the real conversation. Now we'll talk about what's actually deliverable, and when, and we'll rebuild the plan on foundations that can bear weight.

That conversation almost never comes. Instead, the question that follows is some version of: do we have the wrong team?

The date stays fixed. The people become variable.

I've watched this moment play out at every scale — suburban developments, billion-dollar mixed-use programs, and transformation initiatives so large they have no precedent. The pattern doesn't discriminate. And it has taught me more about transformation than any framework I've encountered: the gap between announcing transformation and actually doing it isn't a knowledge gap or a technology gap. More often than not, it's the distance between what everyone in the room quietly understands and what the organisation has made safe to say out loud.

It's worth being fair about why this happens, because it rarely comes down to the individual capabilities of the people involved. There is real strength and power in planting an ambitious flag on the hill. The flag sets a vision, a date, a number. It generates momentum, attracts capital and talent, and creates a story people want to be part of. None of that is trivial — the future does need to be claimed before it can be built, and the organisations that plant no flag at all rarely build anything worth talking about. But here's what's almost always missing: the ability, and the empowerment, to shift and evolve the flag as reality reveals itself — without that movement being read as failure. Once capital has been raised against the flag, careers attached to it, credibility spent on it, the flag becomes the one thing on the hill that cannot move. And so everything else moves instead.

Actually doing transformation is a different kind of work altogether — it's about how the organisation itself is built, not just what it builds. It requires the unglamorous underlayer: a schedule that reflects reality rather than aspiration. Systems and processes designed to deliver the outcome rather than fixating on control. People with the capability for the roles they hold. Incentives that reward collective outcomes rather than unit-level self-protection. And a culture where the person who challenges the plan because they want the right outcome is treated as an asset, not a liability.

What I've observed — and anyone who has worked inside a large program will recognise it — is that organisations build the announcement layer with enormous care, while the operating layer is rarely refreshed, challenged, or tailored to what the ambition actually requires. Best-in-class ambitions get delivered through bureaucratic, outdated and suboptimal processes that make little use of technology or systems thinking. Forward-thinking visions sit on top of structures that incentivise business units to protect themselves rather than advance the whole. The announcement points one direction; the operating system points the other. And the operating system always wins.

The hardest part is what this does to people. When the stated objective is impossible and unquestionable at the same time, those delivering it are left with two rational responses: slow things down so the failure isn't theirs, or cut corners so the failure isn't visible. Both behaviours are entirely logical. Both are corrosive. And on a transformation program — where the entire premise is doing things differently — the contradiction is fatal. You cannot build the future with an organisation structured to protect itself from the present.

So what does actually doing it look like? The answer isn't intellectually complicated. It can't all be done at once; it has to be staged. The schedule has to be realistic, because the schedule is the foundation everything else stands on — quality, cost, value creation, risk. Get the date wrong and you haven't made one mistake; you've made all of them in advance. And the organisation has to be structured around collective success — shared outcomes, shared accountability — rather than a collection of units each optimising for its own survival.

None of that is difficult to understand. All of it is difficult to say inside an organisation where the flag has become sacred.

And this is not a story about any one program or any one place. The same gap runs through every market I've worked in — the feasibility everyone privately knows won't stack, the delivery program everyone privately knows is six months light, the digital transformation everyone privately knows is a software purchase wearing a strategy costume. The bigger the ambition, the more visible the gap becomes. But it was always there.

So here's the question I'd put to you: in your organisation, what happens to the person who tells the truth about the date? Are they invited deeper into the conversation — or quietly moved out of it?

Because whatever your answer is, that's your transformation strategy. Everything else is announcement.