The short answer
When the information reaching the executive team about an ongoing transformation primarily comes from the people responsible for delivering it. That is not a question of trust. It is a question of structure. Internal status reporting is necessary but not sufficient, because the people best placed to identify systemic risk are also the people whose performance depends on the programme being seen as successful.
An independent review provides what internal reporting structurally cannot: an outside view, calibrated against empirical patterns from comparable programmes, free of any incentive to make the picture look better than it is.
Five signals that warrant an independent review
Across 14 years of advisory work, the same patterns recur. None of them is conclusive in isolation. Two or more occurring together typically indicate that the formal status of the programme has decoupled from its actual condition.
Signal 1: Milestones are passed but the deliverables are not visible
The status report shows green. Milestone three was completed on schedule. But when leadership asks to see the working integration, the demonstrable user journey, or the validated data model, what is shown is a presentation about progress rather than the progress itself.
This pattern reflects what behavioural research calls a shift from outcome reporting to activity reporting (Standish Group, 2020). The team is genuinely working hard. The activities are real. But the link between the activities and the original outcomes has weakened, often without anyone making a deliberate decision that it should.
Signal 2: Scope keeps growing without a formal decision
The original business case had three workstreams. Now it has six. Each addition was justified individually and often correctly. But no one has stepped back to ask whether the cumulative scope still corresponds to the original case for the investment.
Scope creep is rarely the product of a single bad decision. It is the cumulative effect of many reasonable ones.
This pattern is particularly common in transformation programmes that span multiple business units. Each unit contributes a legitimate requirement. The aggregate exceeds what any business case could honestly justify, but that aggregate is rarely re-evaluated as a whole.
Signal 3: The sponsor's involvement has shifted from active to ceremonial
In the early phase, the executive sponsor attended every steering committee, asked detailed questions, and challenged assumptions. Six months in, attendance is intermittent. Twelve months in, the sponsor receives a summary deck rather than participating in the discussion. The programme is still important on paper. The actual oversight has eroded.
Prosci's research on change management effectiveness shows that active sponsorship is the single strongest predictor of programme success. Programmes with excellent sponsor engagement are 6-7 times more likely to meet their objectives than those with weak sponsorship (Prosci, 2023, n=6,000+). The decline of sponsor engagement over time is one of the most robust patterns in the data.
Signal 4: Bad news arrives late, softened, or pre-explained
Issues that should have surfaced in week three appear in the status report in week eight. When they do appear, they are framed as already resolved or about to be resolved. There is rarely a moment of structural alarm, even when the cumulative pattern of late-arriving issues should provoke one.
This is not dishonesty. It is the predictable outcome of a reporting structure where the people producing the report also bear the cost of bad news. Variability is high. Some teams report problems early and clearly, others compress and reframe. But the structural incentive points in one direction. An independent reviewer is not subject to that incentive.
Signal 5: Sunk-cost reasoning has replaced the original business case
The conversation about whether to continue is no longer framed as "does this still produce the value the original case promised?" but as "we have spent X already, so we have to finish." This shift typically happens late in a programme, when the gap between the original promise and the likely outcome has become difficult to ignore.
Sunk-cost reasoning is one of the most consistently identified biases in decision research (Kahneman, 2011). It is also one of the most consequential in transformation programmes, because it converts what should be a decision about future value into a defence of past spend.
What an independent review actually delivers
An independent review of a transformation programme is not an audit. It does not check whether processes were followed. It examines whether the programme is on track to deliver the value the original business case promised, given the patterns visible in the current data and the empirical base rates from comparable programmes.
Three things separate it from internal status reporting.
An outside view. The reviewer has no stake in the programme's continuation, no relationship with the vendor, and no incentive to make the picture look better than it is.
Calibration against base rates. The current variance is evaluated against published data from comparable programmes. A 15% schedule overrun looks acceptable until calibrated against the median for similar programmes, which may be lower or higher than 15%, and that calibration changes the meaning of the number.
A forward-looking risk assessment. Internal reporting tends to focus on what has happened. An independent review focuses on what is likely to happen next, based on the patterns visible in the current data and the empirical base rates from comparable programmes.
When the board should commission the review directly
There is one situation where the independent review should be commissioned by the board rather than by the executive team: when the executives themselves were involved in initiating and sponsoring the transformation. In that case, the people who should be evaluating the programme's health are also the people with an interest in it looking good. This is not a question of trust. It is a question of structural independence.
When is it too late?
The pattern is consistent: the cost of correction grows exponentially with time. A programme reviewed at month six can typically be corrected at low cost. A programme reviewed at month eighteen often cannot be corrected at all. The question becomes whether to continue at all.
A review at month six can correct course. A review at month eighteen often cannot.
The signal that an independent review is needed is rarely a single dramatic event. It is the cumulative pattern of small concerns that have not been resolved. When two or more of the five signals above are present, the case for an independent review is strong. When three or more are present, the question is no longer whether to commission a review but how quickly.
A signal that this pattern applies to a specific situation: the formal status reports remain green while informal conversations with delivery staff produce a different picture. Where that gap exists, the cost of testing it now is bounded; the cost of letting it widen is not.