Why independent reviews matter more than ever
Large transformations rarely fail because people stop working. They fail because they stop seeing. The recent findings on Immigration New Zealand’s Biometric Capability Upgrade are a sharp reminder. Years of effort, governance structures, reporting cycles, and committed people, yet the programme drifted, reality diverged from reporting, and critical concerns did not travel.
The issue was not a lack of information. It was a breakdown in how truth moved. Dashboards stayed green. Milestones were met. But activity replaced progress, and reporting became a performance rather than a lens. Over time, the system protected itself from discomfort instead of exposing risk. This is the real failure mode in large programmes: not incompetence, but loss of organisational self-awareness.
When speaking up feels risky, when bad news is softened or filtered, and when governance consumes reports without truly interrogating them, organisations lose the ability to see clearly, even while everything appears to function. Independent review matters not because it judges the past, but because it restores sight in the present.
The question for any leadership team is simple, and uncomfortable: Are we being informed, or reassured?
Large transformations rarely fail because people stop working. They fail because they stop seeing.
In June 2026, an independent report into Immigration New Zealand’s Biometric Capability Upgrade landed on the desk of Public Service Commissioner Sir Brian Roche. The findings were serious enough that the Immigration Minister, Erica Stanford, described them as almost as bad as it gets. The project had been launched in 2018 without ministerial sign-off, shifted to an off-the-shelf model in 2020 without adequate due diligence, and continued for years despite delays, missed milestones, and rising cost before being stopped in 2025, having delivered no measurable benefit and more than thirty million dollars of sunk cost.
One detail matters more than the money. Ministerial reporting throughout was found to be inconsistent and at times to have misrepresented the project’s true status, and people who raised concerns were, in the chief executive’s own account, not listened to and may have been moved off the project.
Sit with that for a moment. The problem was not that nobody knew. Somebody always knew. The problem was that what they knew did not travel, the reporting said one thing while reality said another, and the people closest to the truth learned that speaking up was not safe.
That is the question worth asking here. How does an organisation full of capable people lose the ability to see itself clearly? This is not just a story about a failed IT system. It is a story about what happens to organisational self-awareness, and it could be a story about almost any large programme in almost any sector.
Most organisations do not lack reporting. They have dashboards, steering committees, status updates and governance packs. Immigration New Zealand had all of these, and they still produced a picture that misrepresented reality for years. So what were all those reports actually for? Reporting was not the safeguard. In a sense, it was the disguise.
This is the paradox independent reviews exist to resolve. They are not about finding fault, and they are not a verdict on whether a project has succeeded or failed. They are about creating the conditions for better decisions while there is still time to influence outcomes. The most useful review does not tell leaders what already went wrong. It shows them what they can still change.
Activity versus progress
Reporting tends to focus on what is easiest to count. Milestones, deliverables, spend against budget, and status ratings are visible, discrete and comfortable to present. The difficulty is that activity and progress are not the same thing, and the gap between them is where projects quietly fail.
Consider the Biometric Capability Upgrade. The status reports kept working long after the project itself had stopped being viable. The instruments of oversight kept producing green while the thing they were meant to watch drifted into distress. How often do our own dashboards do the same?
This is a failure of measurement more than effort. When a measure becomes a target, it ceases to be a good measure, because people optimise for the indicator rather than the outcome it was meant to represent. A milestone met on paper becomes the goal, and whether the milestone still means anything is a question nobody is incentivised to ask.
A related problem is organisational defensiveness. Organisations become skilled at producing information that protects them from discomfort rather than information that helps them learn. Seen that way, reporting was not failing at its job. It was succeeding at a different job: maintaining the appearance that everything was under control.
None of this requires bad people. The Immigration case involved, by the chief executive’s own description, passionate staff who did not want the project to fail. Capable, committed teams are not immune to this pattern. If anything, they are more exposed to it, because the more invested people are in a shared narrative, the more coherent and self-reinforcing that narrative becomes, and the harder it is to say the thing that breaks it.
Organisations rarely fail because people stop working. They fail because they stop seeing.
When truth stops travelling
The most revealing detail in the Immigration findings is not about accounting or governance. It is that concerns were raised and not heard, and that raising them may have carried a personal cost. That turns a project failure into an organisational one, because it explains why early warnings never reached the people who could have acted on them.
Research on psychological safety gives this its clearest frame. Teams do not fail to surface problems because people lack information; they fail because the interpersonal risk of speaking up is too high, so silence becomes the rational individual choice even when it is disastrous collectively. When an organisation quietly teaches its people that bad news is unwelcome, it does not stop the bad news existing. It only stops the bad news arriving.
A related model of organisational culture distinguishes between environments that punish messengers and those that develop them. In that sense, how information flows is itself a measure of organisational health. A project where dissenters were moved on was telling you what kind of culture it had long before the final report confirmed it.
This is where reviews and fear intersect. If a review is experienced as a search for blame, it deepens exactly the culture that caused the problem. People rehearse their answers, close ranks and manage the reviewer, and the review produces a tidy account that everyone can live with and nobody learns from. The paradox is sharp: the more an organisation needs the truth, the more likely its culture is to suppress it.
That is why any review has to be designed to work against that grain rather than with it. A review that increases fear reduces the flow of information it depends on. The aim is not to establish who failed. It is to make it safe enough for the organisation to see itself honestly.
Why independence changes the conversation
Everyone inside a programme carries the assumptions of the programme. That is not a weakness of individuals; it is how shared endeavour works. People align around a common story so they can move quickly, and the more capable and committed the team, the more coherent and self-reinforcing that story becomes. The cost of coherence is that certain questions stop being asked, because asking them starts to feel like disloyalty or like re-litigating decisions everyone thought were settled.
An external reviewer is not bound by that story, and that single fact changes the conversation. A good independent reviewer can ask uncomfortable questions without carrying the political cost that an insider would, connect patterns across functions that each team can only see in fragments, identify blind spots that have become invisible precisely because everyone shares them, challenge assumptions respectfully, and distinguish symptoms from root causes.
The point is not that outsiders are cleverer than the people doing the work. They usually are not, and they know far less about the detail. Their advantage is positional. They can see the whole because they are not standing inside any part of it, and they can say what they see because they do not have to live with the internal history of every decision.
Three moments for review
We tend to treat reviews as a single instrument, wheeled out at the end of a programme or when something has clearly gone wrong. In practice, independent review earns its keep at three quite different moments.
A mid-programme health check is the cheapest form of insurance an organisation can buy, and the most frequently skipped. Its purpose is not to grade the programme but to test whether the assumptions it was built on still hold. Circumstances change. Strategy shifts. What was a sound plan eighteen months ago may now be solving a problem the organisation no longer has.
A useful health check asks whether the objectives are still valid, whether governance is actually functioning rather than merely meeting, whether new risks are emerging beneath the reported ones, whether stakeholder confidence is quietly changing, and whether scope has drifted without anyone deciding that it should. The value lies almost entirely in timing. Early course correction is far cheaper, in money and credibility, than recovery.
Sometimes a programme has clearly lost momentum and nobody can quite say why. The reporting still functions, the meetings still happen, but progress has become sticky in a way that resists the usual explanations. This is the moment for an intervention review.
Programmes stall for reasons that are rarely technical. Decision-making becomes unclear, so choices are deferred rather than made. Governance fatigue sets in, and forums that were once decisive become ceremonial. Competing priorities pull the same people in different directions. Capability gaps that were tolerable at the start become binding constraints at scale. And organisational politics, the quiet friction of who owns what, slows everything without ever appearing on a risk register.
A good intervention review asks what is actually preventing progress rather than who is responsible. That distinction matters. The first question opens the system up for examination and invites honesty. The second closes it down, because once a review becomes a search for blame, people stop telling the truth.
Post-implementation reviews are the most commonly wasted of the three. They are often done too late to be honest, once the people involved have moved on and the incentive is to declare victory, or they are treated as a compliance step rather than a source of learning.
A post-implementation review earns its place when it asks genuinely open questions. What actually worked, and would we know how to repeat it? What surprised us, and what does that surprise tell us about the gaps in our original thinking? Which assumptions proved wrong? Which decisions created the greatest value, and which merely created activity? And what capability have we genuinely gained, as distinct from what we have simply completed?
Answered seriously, those questions turn a finished programme into an organisational asset. Answered as compliance, they produce a document nobody reads.
Assurance and learning
It helps to be precise about what a review is for, because one word is often asked to do two jobs. One is assurance. The other is learning. They are related, often travel together, and they are not the same thing.
Assurance asks a protective question: did we comply, did we follow the process, did we do what we said we would do? It exists to give boards and sponsors confidence that risk is being managed and obligations are being met. It looks backwards and downwards, checking the work against the rules.
Independent review, in its fuller sense, asks a generative question: did we create value, and are we still creating it? It looks forward and outward, checking the work against its purpose. Assurance protects organisations from downside. Learning improves them for the future. A mature organisation values both and confuses neither.
The Immigration case exposes the trap: assurance that is not honestly fed produces false comfort rather than real protection. All the process in the world cannot help you if the culture underneath it will not let the truth move freely.
Reviews should build agency
The real test of a review is not the quality of its analysis. It is what people can do differently once it is finished. A review that produces a thick report and a longer list of recommendations, none of which anyone feels able to own, has failed regardless of how astute its findings are. A review that leaves a team clearer, more confident and more capable of acting has succeeded even if its written output is short.
A well-run review should leave people with greater clarity about what is actually happening, more confidence in their own judgement, genuine ownership of the actions that follow, better decision-making at the points that matter, and a small number of practical steps they can take straight away. It should not leave them with pages of recommendations that belong to no one, or with the quiet sense that they have been graded and found wanting.
This is where independent review connects most directly to leadership and transformation. The purpose of holding a mirror up to an organisation is not to make it flinch. It is to help the people inside it see clearly enough to act well. A review that increases fear reduces agency, and an organisation with less agency is less able to fix the problems the review identified.
What good reviews look for
Weak reviews concentrate on schedule and budget, because those are the numbers easiest to obtain and hardest to argue with. They matter, but they are lagging indicators. By the time schedule and budget have moved, the causes have usually been in place for months.
A stronger review looks past the numbers to the conditions that produce them. It examines strategic alignment, decision quality, governance effectiveness, leadership behaviours, stakeholder confidence, organisational capability, delivery approach, risks and dependencies, benefits realisation and the ability to adapt.
Looked at together, these are less a checklist than a way of seeing. They shift the conversation from “is the project on track” to “is this organisation building the right thing, making good decisions, and able to change course when it needs to?” That is a more uncomfortable set of questions, and a more useful one.
What New Zealand shows
The Immigration case is the sharpest recent illustration, but it is far from an outlier. The strongest argument for continuous independent review is written into the recent history of large-scale change across the public sector, where the most significant transformations have not been reviewed once at the end but assessed again and again throughout their lives.
Large organisations evolve through continuous review, not through a single programme declared finished and then left alone. The point is not that every review prevents failure. It is that regular independent assessment helps keep strategic intent, operating model and delivery aligned as conditions keep changing.
The clearest case of assessment built into delivery is a multi-year business transformation such as Inland Revenue’s, where independent gateway and assurance reviews were part of the work rather than an afterthought. That is precisely the argument for reviewing during transformation rather than after it: the reviews happen while there is still room to act on what they find.
Across examples like this, the same message keeps surfacing. Mature organisations do not rely solely on internal reporting. They build independent perspective into the work on purpose.
The real failure mode
It is tempting to frame all of this as a story about catching problems. It is more accurate, and more useful, to frame it as a story about alignment. Transformation does not usually fail because organisations stop delivering work. It fails because they lose sight of what the work is meant to achieve.
At the start of any major change, strategy, operating model, governance, people and technology sit in a deliberate but fragile relationship. Everyone broadly understands how each connects to the others and why the whole hangs together. Then delivery begins, and each element starts to move at its own pace. Technology decisions are made to keep the build moving. Governance adapts to the rhythm of reporting. The operating model bends to accommodate what is being built. People adjust to the reality in front of them.
Each adjustment is reasonable on its own. The trouble is that the sum is a slow drift, in which the parts stop adding up to the whole and nobody notices the moment it happens.
This is what independent review is really for: not to check whether milestones have been met, but to reconnect the pieces that delivery has gradually pulled apart. The most valuable question a review can ask is not “are we on schedule” but “do these things still fit together, and do they still serve what we set out to do?”
Why experience matters
The quality of a review depends heavily on who conducts it, and the relevant experience is broader than it first looks. Reading a programme well means seeing how strategy, governance, organisational design, delivery and executive leadership interact, because a problem that shows up in one of these almost always begins in another. A schedule slip is rarely a scheduling problem. A governance failure is rarely a governance problem.
The skill is in tracing the symptom back to its source, and that skill comes from pattern, not from theory. Independent judgement is built by seeing many organisations rather than one. A reviewer who has watched the same drift occur across different sectors, in different structures, under different leaders, learns to recognise it early and to tell the features that are specific to this organisation from the patterns that are common to all of them.
That, in the end, is the real basis of independence. It is not distance for its own sake, but the accumulated perspective that lets someone see a particular situation clearly because they have seen its relatives many times before.
Closing
Independent reviews are not about proving whether a programme has succeeded or failed. They are about creating better decisions while there is still time to shape the outcome. Whether they come during delivery as a health check, in the middle of difficulty as an intervention, or after implementation as a source of learning, a thoughtful review gives an organisation something it can rarely generate for itself: a clear account of what is happening, why it matters, and what should happen next.
The Immigration review will run its course, and in time it should offer lessons the whole system can learn from about risk management, assurance, monitoring, reporting and the environment leaders create for people and programmes to succeed. The most important of those lessons may well be the least technical one. Systems and dashboards do not fail on their own. They fail when the culture around them stops carrying the truth, and no amount of reporting can make up for an organisation that has quietly made honesty expensive.
The greatest value of an independent review is not the report. Reports are read once and filed. The value is what the report makes possible: restored clarity, recovered alignment, and the confidence it gives leaders to act. An organisation that can see itself clearly can change course while change is still cheap. That, in the end, is the whole point.