May 19 2026
I've worked with organisations across industries, sectors, and sizes. Different leadership teams. Different delivery partners. Different strategies, structures, and maturity levels.
And yet, I keep seeing the same thing.
Not similar things. Not related things. The same thing — wearing different clothes depending on where in the organisation you look.
It took me a long time to name it clearly. But once you see it, you can't unsee it.
Here's what the pattern looks like from the outside:
A transformation is approved. The business case is compelling. The executive team is aligned. The program kicks off with energy and intent.
Then, quietly, something shifts.
Milestones start slipping — not dramatically, just a little. Governance meetings fill with status updates and run out of time for decisions. Benefits that seemed certain start feeling theoretical. Teams get busy but lose sight of what they're building toward. The Sponsor stops hearing about problems until they've already become crises.
By the time it's visible, the damage is done. The question becomes: how did we get here?
The answer is always the same.
The first instinct is to look at delivery. Were the teams capable enough? Was the methodology right? Was the scope too ambitious?
Sometimes. But rarely.
In most of the organisations I've worked with, delivery capability is not the constraint. Teams are experienced, motivated, and working hard. The methodology is sound. The scope — while challenging — is achievable.
The problem isn't in the engine room. It's in the navigation system.
And in most organisations, the navigation system was never actually built.
Every organisation has invested heavily in accountability systems. Governance frameworks. Portfolio dashboards. Risk registers. Assurance processes. Reporting cycles.
These are accountability systems. They tell you what happened. They create a record. They distribute information.
What they don't do is tell you what's coming.
They were designed to answer: *"Where have we been?"*
Nobody designed them to answer: *"Where are we heading — and is that still where we want to go?"*
That distinction — between accountability and navigation — is the root cause of almost every transformation problem I've seen. Not the only cause. But the root.
I've been writing about this pattern from different angles for the past 6 months. Each article named a different manifestation of the same underlying dysfunction.
Project Drift is what happens when nobody is navigating. Projects don't blow up — they quietly lose direction because the system around them optimises for activity, not outcomes. Teams get busy. Alignment gets assumed. The "why" fades. By the time the drift is visible, it's been compounding for months.
The Value Realisation Gap is what happens at the portfolio level. Outputs get delivered. Dashboards glow green. And yet the outcomes the business case promised never quite materialise. Because the accountability system measured delivery, not value. And nobody owned the gap between them.
Governance Theatre is what the accountability system looks like when it mistakes process for governance. Committees meet. Reports are presented. Risks are noted. But decisions don't land, escalations don't happen, and the steering wheel is never actually turned. Governance becomes a ritual performed in the direction of oversight.
The Budget Trap is what happens when the funding system is built for accountability rather than strategy. Capital gets locked into the past — committed to plans made months ago against assumptions that have since moved. The organisation keeps funding what it approved rather than what the strategy now requires.
Alignment Traps are what happens when leaders assume agreement rather than create it. Silence gets mistaken for alignment. Dissent gets polished away in the meeting and resurfaces in the work. The organisation appears aligned but isn't — and the gap shows up in delivery.
Cultural Debt is the accumulated cost of all the difficult conversations that were avoided. Every time a hard truth was softened, every time a risk was understated, every time a problem was managed down rather than surfaced up — that's a deposit into the Cultural Debt account. It accrues silently. It's called in at the worst possible moment.
The Sponsor Paradox is what happens to the best executive leaders inside a broken navigation system. They're hired for their strategic instinct. They're trapped in a governance model that only shows them an iceberg when it's already scraping the hull. Their brilliance gets neutralised by a system that was never designed to give them early sight.
The Historian PMO is the mechanism that should be providing navigation — and isn't. It reports on the past with extraordinary precision. It provides almost no foresight. And because it doesn't, every other dysfunction gets to compound in the dark.
These aren't eight different problems. They're eight different expressions of one organisational design failure:
The system was built to account for what happened. Nobody built it to see what's coming.
Accountability without navigation produces a predictable set of symptoms:
Decisions arrive too late because problems are only surfaced when they're already crises
Value leaks silently because nobody is tracking the gap between what was promised and what's being built
Sponsors get blindsided because the warning signal never fired
Governance becomes theatre because the only information flowing through it is historical
Teams drift because clarity fades and nobody is holding the line of sight to outcomes
Budgets entrench the past because the funding system was never designed to respond to the future
None of this is intentional. Nobody designed an organisation to fail. They designed it to be accountable — and accountability, without foresight, creates all of the above.
The reason this pattern is so persistent is that the accountability system looks like it's working.
Reports are delivered on time. Dashboards are updated. Governance meetings run to the agenda. Risk registers are maintained. Budgets are tracked.
From the outside — and often from the inside — the system appears functional. It's generating output. It's producing artefacts. It's consuming effort.
What it isn't doing is protecting value.
And because the system looks like it's working, the question "what are we not seeing?" rarely gets asked. Until it's too late.
This is the most dangerous property of the accountability-without-navigation failure mode: it's self-concealing. The Watermelon Portfolio stays green on the outside long after it's red on the inside. The Historian PMO keeps producing clean reports while the iceberg keeps growing. Governance Theatre keeps filling the calendar while the real decisions go unmade.
The system is busy. The organisation is drifting.
The organisations that don't fall into this pattern share a set of disciplines that most organisations treat as optional.
They ask forward questions, not just backward ones. Not only "what happened?" but "what decisions are coming, and what do we need to know to make them well?"
They treat foresight as a governance responsibility. The Sponsor's primary job isn't to receive reports — it's to see around corners early enough to actually steer. Early Sighting isn't a nice-to-have. It's a fiduciary duty.
They own outcomes, not just outputs. Value doesn't happen automatically at the end of delivery. It has to be designed, tracked, and owned — by business leaders, not delivery teams.
They surface weak signals before they become strong ones. Pre-Mortem thinking. Materiality filters. Decision Velocity as a metric. These aren't advanced practices — they're basic navigation disciplines that most organisations have never formalised.
They treat alignment as something that requires continuous maintenance, not a one-time achievement. Silence is not alignment. Agreement in a meeting is not alignment. Alignment is visible in the work — and it requires regular, honest checking.
They pay their Cultural Debt. Difficult conversations don't get easier by being deferred. They compound. Organisations that create the conditions for honest escalation — where surfacing a problem is rewarded, not managed — build a structural advantage over those that don't.
I've described a systemic problem. But systems are made of decisions — decisions made by leaders, usually with good intentions, usually under pressure, usually without a clear view of what the accumulated effect would be.
So the honest question isn't "why is our organisation broken?"
It's: "What would we need to see differently to navigate better?"
That question — asked genuinely, without defensiveness — is the starting point for every meaningful change I've seen.
Not a new methodology. Not a governance framework refresh. Not a PMO restructure.
A different set of questions, asked earlier, by leaders who've decided that foresight is their responsibility — not someone else's.
Every transformation problem I see is the same problem.
Not the same symptom. The same root.
An organisation that was designed to account for the past, operating in a world that rewards the ability to navigate the future.
The good news is that once you can see the pattern, you can change it. The navigation system isn't complicated. It doesn't require a transformation of its own. It requires clarity about what you're trying to see, and the discipline to keep asking the questions that produce foresight rather than just the ones that produce reports.
Historians record what happened.
Navigators change what will.
The question — for every executive reading this — is which one your organisation is actually designed to be.
This article draws on the full Executive Insights series from Nsight. If you've recognised your organisation in any of the patterns described here, the series is worth reading in full — each article goes deeper on one piece of the same picture.