June 17, 2026
If it was so important, how did no one notice it had stopped?
Your organisation will almost never kill a project on purpose. You know this. Sunk cost, sponsor pride, the sheer inertia of a budget line that’s been approved once and never re-examined — initiatives don’t die, they fade, get re-baselined, quietly absorbed into business-as-usual. Deliberate, clean defunding is one of the rarest events in corporate life.
So when one actually happens — by accident — pay attention. You’ve just been handed a free experiment you would never have run on purpose: a live test of what was genuinely load-bearing. Most portfolios never get to run it once.
A project was quietly defunded last spring. Not killed in a steering committee, not debated, not eulogised. Its budget was reallocated to plug a hole somewhere louder, and the people who could have objected were busy with the thing that was louder. It simply stopped — not because anyone decided it should, but because the money was needed elsewhere and no one fought for it.
For a full quarter, nothing happened.
No objective slipped. No KPI moved. No customer complained, no executive asked where it had gone, no downstream team found themselves blocked. The organisation carried on exactly as it had the week before. The project that had occupied a line on every portfolio report, that had been rated, RAG-coloured, status-updated and steering-committee’d for the better part of a year, was gone — and the silence was total.
When someone finally noticed, the question they asked was the right one, and it should have been terrifying:
If this was so important, how did no one notice it had stopped?
There are only two possibilities, and neither is comfortable.
The first: it was important, and the organisation is so disconnected from its own work that it lost something valuable for three months without flinching. That’s a catastrophe of attention.
The second — the real one, almost every time — is worse, because it implicates the system that was supposed to be watching: it was never load-bearing in the first place. And here is the part that makes it insidious rather than merely sloppy: the project was not unaligned. It wasn’t an orphan someone forgot to link to the strategy. It was perfectly aligned — to an objective that didn’t matter. Properly wired, diligently delivered, pointed at a target the company had quietly outgrown or never truly prioritised. Nothing broke when it stopped because the thing it served wasn’t holding anything up either.
This is the watermelon in its most dangerous form. Green on the outside. Hollow underneath. But the usual telling of the watermelon story gets the mechanism wrong twice over. First, we imagine the green status was a lie — that someone was hiding bad news. Often there was no lie at all: the delivery status was accurate, the project genuinely on time, on budget, on scope. Second, we imagine the fix is alignment — “just connect every project to a strategic objective.” But this project was connected. It would pass any alignment audit that simply asks is it linked? It fails only when you ask the harder question: linked to something that matters?
The reports were answering the wrong question. So, it turns out, was the alignment check.
Here is the part that should keep portfolio leaders awake.
The governance system around this project worked perfectly. Status reports were filed on time. RAG ratings were applied with discipline. The project appeared on the right dashboards, in front of the right people, at the right cadence. Someone owned it. Someone reported on it. Someone read the report.
Everyone did their job. And none of it governed anything.
Because the entire apparatus was built to answer one question — is this project being delivered well? — and never the only question that determines whether the project should exist at all: is this project serving something that matters? A governance system can hum along flawlessly, consuming real hours from real people, producing accurate reports about the on-time delivery of work that advances an objective no one would defend if asked to rank it. That isn’t governance. It’s theatre with excellent production values.
The defunding was, in the end, the only honest importance audit the organisation ever ran. And it ran it by accident. The experiment the portfolio office should have designed deliberately — what strategic objective would actually suffer if we stopped this, and by how much? — got conducted blind, by a budget reallocation nobody connected to strategy, and the result took a quarter to read because no one was looking for it.
And here is the deeper failure underneath that one. The organisation didn’t run this audit on purpose because, in practice, it has no working mechanism for running it at all. Even where a re-justification step exists on paper — a quarterly portfolio review, a stage gate meant to re-test the case — it has usually decayed into a formality: the project restates its plan, delivery is confirmed on track, the alignment box is ticked because yes, it links to an objective, and the question of whether that objective still matters goes unasked. There is rarely a point in the governance calendar where someone is genuinely required to test importance, not just linkage. The system measures delivery, endlessly. It measures alignment occasionally, and crudely — as a yes/no link. It seldom measures weight. So the only importance audits it reliably performs are the accidental ones — the projects that happen to get stopped for unrelated reasons, revealing the truth as a side effect. Every watermelon that doesn’t get accidentally defunded simply survives, green and dutifully aligned, indefinitely.
So here is the prescription, and it is a single question. Run it against every significant initiative in your portfolio, today:
If we stopped this tomorrow, what strategic objective would suffer — and by how much?
Sit with both halves, because they do different work.
What would break points at linkage. If you cannot name the objective that fails, the KPI that stalls, the capability that goes missing — if the honest answer is “nothing concrete” — then the initiative isn’t connected to your strategy at all. That’s the easy watermelon to find.
And by how much points at the harder one. A project can clear the first test — yes, it’s linked, here’s the objective — and still fail this one, because the objective it serves is one the organisation has quietly demoted, outgrown, or never really ranked. The link is real. The weight is not. This is the watermelon that survives every alignment audit, because the audit only ever checked the link, never the importance of what sat at the other end of it.
If the honest answers are “very little” and “hardly at all” for even one of your green, dutifully-aligned projects, you’ve found a watermelon — and both your reporting and your alignment check have been painting it green the entire time.
The instinct, having read this far, is to take the question into your next steering committee and ask it. Do — it’s a good hour spent. But understand its limit.
You can interrogate one project this way. Maybe five. You cannot do it across fifty, every fortnight, for every initiative, consistently, without the discipline collapsing into exactly the box-ticking that produced the problem. The question is only protective if it is asked structurally — encoded into how the portfolio is measured, applied to every initiative the moment it is created, not remembered occasionally by whoever is paying attention that week.
Which means the test has to live in the instrument, not in someone’s memory — because the alternative is waiting for an accident. You cannot run your portfolio on the hope that the projects serving trivial objectives will happen to get defunded for unrelated reasons. The accidental audit is real, but it’s rare, random, and a quarter too late. The deliberate version — weighting every initiative by the importance of what it actually serves — has to be built in.
This is what we built Nsight Dashboards to do. Every project is plotted not just on whether it’s delivering, but on how much strategic weight sits behind what it’s delivering — its measured importance, not merely whether a link to an objective exists. A project can be a healthy green and still sit at the far edge of irrelevance, and the instrument shows both at once. The contradiction the defunding took a quarter to surface is visible on day one.
The failures everyone catches are the loud ones — low health, low importance, obviously in trouble; someone always deals with those.
The project that should worry you is a project sitting healthy and green, faithfully delivering against an objective that barely registers — healthy enough never to be challenged. This is the watermelon the accidental defunding revealed — except here it's flagged the day it was created, not the quarter after it was stopped.
The defunding worked, in its way. It answered the question. But it answered it a quarter late, at random, and only because someone needed the money for something else.
You should not have to lose a project to find out whether it mattered.
Ask the question of your own portfolio this week. And if you cannot answer it for every initiative without guessing — that, not the answer, is the finding.
Nsight helps portfolio and transformation leaders turn strategy into reality — by making the connection between strategy and execution measurable, not assumed. nsight.com.au