May 27, 2026
Most executives will tell you their organisation has good visibility.
The dashboards are up to date. The status reports arrive on time. Governance is meeting on schedule. The PMO is producing the pack.
And yet, when something goes wrong, the same phrase comes up in every post-mortem:
"We didn't see it coming."
That phrase should be impossible. If you have all those instruments running, you should see everything coming. The fact that you don't — that organisations with millions invested in reporting still get blindsided — tells you something important about what those instruments are actually doing.
They're not helping you see. They're helping you account.
There's a difference.
What follows is five questions. Ask them of your executive team. Ask them of yourself.
You don't need a workshop. You don't need a consultant. You need five minutes and the discipline to answer honestly.
For each question, there are three possible outcomes:
→ You can answer in under thirty seconds, with specifics. That's navigation.
→ You can answer, but vaguely — with hedges, generalities, or "I'd need to check." That's reporting.
→ You can't answer, or you'd have to ask someone. That's flying blind.
Score yourself on all five. Then we'll talk about what it means.
Not the decisions you made last quarter. Not the ones currently on the agenda. The ones that are coming — that haven't surfaced yet, but will.
If your governance system can't name them, it isn't governing. It's reviewing.
The organisations that navigate well know what's coming because someone is looking. The ones that are flying blind discover decisions the moment they become urgent — which is also the moment options collapse.
Note the second half of that question. It's the harder one.
Every portfolio has value leaking somewhere — scope drift, delayed benefits, assumptions quietly going stale. The question isn't whether it's happening. It's whether your instruments can detect it before it shows up in the delivery report.
If the only way you'd know is when a project goes red, you don't have a Value at Risk system. You have a damage report system.
By the time damage shows up, the value is already gone.
Every business case is built on assumptions — about the market, the technology, the customer, the regulatory environment, the team that would deliver it.
Some of those assumptions stop being true within weeks of approval. Most organisations never re-examine them. The business case gets approved, filed, and never revisited until the benefits review eighteen months later — when it's too late to do anything about it.
If nobody on your team can tell you which assumptions have shifted, you're not running an investment portfolio. You're running a hope portfolio.
This is the test of whether your warning system works.
If the answer is "we're never surprised" — that's not a good sign. It means either nothing is moving (unlikely) or the reporting is sanitised before it reaches the executive (likely). Green dashboards in a complex transformation environment are almost always a watermelon — green on the outside, red underneath.
If the answer is "we were surprised, and here's what we changed" — that's a healthy system. Surprise is information. The question is whether your governance processes it or absorbs it.
If the answer is "we were surprised, but nothing changed" — that's the worst outcome. You have a warning system that nobody acts on.
This is the one that hurts.
I've watched organisations do exactly this — cancel status reporting, simplify governance, "free up executive time." A few months later, the same executives are in the room asking why they didn't know about something.
The answer is uncomfortable: the reporting wasn't the problem. It was the only thing they had. Cancel it and you don't get better governance. You get no governance.
A navigation system can survive the loss of status reporting because it's built around different things — forward decision flow, assumption tracking, value-at-risk monitoring, weak-signal detection. A reporting system can't, because the reporting is the system.
If the answer to this question is "we'd be in trouble within a month" — your governance isn't navigating. It's narrating.
Five answers, in under five minutes.
→ Five specific answers: Your organisation can see. You have a navigation system, not just a reporting one. Rare.
→ Three or more vague or unknown: You're flying blind. The instruments you have are pointed backwards. You'll keep being surprised, and the surprises will keep being expensive.
→ Anywhere in between: You have pieces of a navigation system, but they're not joined up. The visibility you have is accidental, not systematic — which means you can't rely on it when it matters most.
The five questions aren't really about projects, or governance, or the PMO.
They're about whether your organisation has any forward visibility at all — or whether everything you know about your portfolio is something that already happened.
Every transformation problem I've written about — Project Drift, the Value Gap, Governance Theatre, the Budget Trap, the Sponsor Paradox, the Historian PMO — traces back to the same root: organisations built to account for the past, operating in environments that reward the ability to navigate the future.
This test surfaces that gap in five minutes.
If you took it honestly and didn't like the result, you're not alone. Most organisations would fail it. The difference between the ones that keep failing and the ones that change is whether the executive team is willing to look at the score.
The dashboard won't tell you you're flying blind.
That's the whole problem.
This article is part of the Executive Insights series from Nsight. If this resonates, the previous articles in the series — Every Transformation Problem Is the Same Problem, The PMO Navigator, and The Sponsor Paradox — build out the framework this test is measuring against.