The dashboards are green. The organisation has not moved.
In Brief
- Transformation programs most often fail because the real constraint was misidentified before the work began, not because execution was poor.
- The incentive structure of a running program means no party at the table is positioned to question the original problem definition.
- Green dashboard metrics confirm every party is performing their role — not that the program is addressing the right constraint.
- An independent view, initiated before the next phase is approved, tests whether the program is solving the actual problem.
- Each program cycle that fails to shift the organisation makes the next one harder to fund, resource, and sustain.
The executive walking back to her office after the steering committee already knows it. Every report card was green. Vendor delivery was on track. Internal change activities had closed out their milestones on schedule. The slide that mattered most — capability uplift across the operating environment — was green too. And yet the conversation she had with her line areas that morning was the same conversation she had eighteen months ago, the same one she had three years ago, the same one her predecessor had before her. Nothing structural had shifted. The reports said one thing. The organisation, when she walked through it, said another.
This is not a story about delivery failure. The vendors are competent. The internal change team is experienced. The approach, whichever one is in use, has been applied with discipline. The dashboards are not lying; every measurable artefact that was supposed to be produced has been produced. The pattern this executive is recognising is older and more structural than any of that.
What tends to surface when these programs are examined in retrospect is that the misidentification happened before the work began — not in the execution.
A transformation program is a multi-year commitment to address a constraint. The strategy, the operating model, the technology choice and the change architecture are all the answer to a question that was asked at the front end, usually quickly, usually under pressure, often by the same parties who would later be paid to resolve it. When the answer turns out to be wrong, it is rarely because someone executed it poorly. It is because the question itself was wrong. The program was built around a constraint that was not the one limiting the organisation. The work was real. The cost was real. The constraint stayed where it was.
GovERP is the publicly available instance of this pattern. The $340 million whole-of-government ERP consolidation was wound up in 2024 after years of effort, with The Mandarin reporting that the secretaries board had enthusiastically signed off on the program at inception (Bajkowski, 2024). What the public record does not capture is evidence of an independent brief sitting underneath that sign-off — a piece of diagnostic work, paid for separately from the eventual delivery, asking whether the constraint these agencies were experiencing was actually a shared-platform problem at all. The reasonable inference is that no such brief was funded. The program was authorised against a problem statement supplied by the parties who would benefit from the program proceeding. That is the structural condition that produces a $340 million wind-up, and it is the structural condition that produces the green-dashboard moment the executive at the top of this article is walking out of.
The cross-program data tells the same story from a different angle. Gartner found that only 48 per cent of digital initiatives meet or exceed their business outcome targets (Gartner, 2024). A separate Gartner finding shows that only 43 per cent of executives consider their enterprise highly effective at assessing its ability to successfully execute strategy (Gartner, 2025). The gap between strategy potential and operating reality is consistent: McKinsey puts it at around 30 per cent of an organisation’s available value left on the table because of how the operating model is structured (McKinsey, n.d.). Forrester’s recent capability study, commissioned by SAP and read with that sponsorship in mind, reports that 72 per cent of organisations now run four or more transformation initiatives a year, with only 6 per cent qualifying as transformation leaders and only 24 per cent operating a cross-functional governance board across those initiatives (Forrester Consulting, 2026, SAP-sponsored). The same study found that 43 per cent of organisations name as their biggest capability gap that transformation projects are executed well within individual departments but lack an integrated, enterprise-wide strategy (Forrester Consulting, 2026, SAP-sponsored).
Read together, the pattern is unambiguous. The volume of transformation activity is rising. The proportion of organisations that get the outcome they paid for is not. And the most common executive response is the one McKinsey names as producing diminishing returns: structural redesigns, cost cuts and flatter hierarchies, applied to a problem the redesign was never going to fix (McKinsey, 2026).
No one is paid to disagree
The reason the original constraint is hard to see from inside the program is not that the people are wrong. It is that the structure of the program is not built to surface it. By the time a program has a name, a budget envelope, a delivery partner and a steering committee, every party at the table has an authority position that depends on the program continuing in roughly the shape it has been authorised in. The delivery partner cannot examine the original problem statement without examining their own scope. The internal program owner cannot revisit the diagnostic without re-opening decisions the executive board has already endorsed. The vendors are accountable for what they were contracted to deliver — not for whether what they were contracted to deliver was the right intervention.
None of this is bad faith. It is incentive geometry. Capable people, working hard, all behaving rationally inside their accountabilities, and none of them positioned to look at the question the program is actually answering. The green dashboard the executive is walking past is the visible signal of every party doing exactly what their role requires of them. The fact that the organisation has not moved is the visible signal that none of those roles included questioning the original diagnosis.
What the dashboard is actually showing
The green dashboard is doing its job correctly. It confirms that delivery milestones are being met, that vendor obligations are being honoured, that the change management checklist is progressing. What it cannot confirm — because it was not designed to — is whether those milestones are attached to the right constraint. The measurement system is downstream of the problem statement. It tests execution against the brief. It does not test the brief.
This is what the executive sees when she walks through the organisation and finds it unchanged: not evidence that the program failed, but evidence that the program succeeded at the thing it was designed to do, while the thing limiting the organisation remained unaddressed. The cost of this is not just the current program budget. It is the compounding effect of multiple cycles — each one consuming resources, executive attention, and organisational goodwill — none of them moving the needle because none of them identified the right constraint before the delivery work began. Over time this does not just cost money. It creates institutional scepticism about whether transformation programs work at all. A leadership team that has learned, correctly, not to trust the process is perhaps the most expensive outcome of misdiagnosis — because the next program starts with that scepticism already priced in.
What an independent view actually does
An independent review — initiated before the next phase is approved, by a party with no stake in what gets built next — does one thing the program structure cannot do for itself. It tests whether the constraint the program was built around is the constraint that is actually limiting the organisation. Because it is not accountable to the original problem statement, it is structurally positioned to find the question wrong. That is precisely what makes it useful.
The output is not a delivery plan. It is a clearer picture of the system the executive is operating in — clear enough to decide what to approve next with eyes open. Most of its value comes not from what it confirms, but from what it makes unnecessary: the next program built on the same untested assumption, the next cycle of well-executed work that does not shift the organisation.
The next steering committee question
The executive walking back from the steering committee has most of what she needs. She has delivery data, change metrics, a vendor relationship that has largely performed, and a steering committee that is technically aligned. What she does not have is an answer to the question that was never formally asked: whether the constraint the program was built around was the constraint that was actually limiting the organisation.
That question cannot be answered by the program itself. It requires someone with no stake in the answer — a party that benefits from finding the problem correctly, not from confirming the solution. The most practical point to ask it is before the next phase is scoped and approved, not after it is underway.
The most expensive assumption in a transformation is not in the delivery plan. It is in the problem statement that no one was paid to question.
References
- Bajkowski, J. (2024, August 20). GovERP declared a $340 million pain in the back office. The Mandarin.
- Forrester Consulting. (2026). The capability mindset [Report commissioned by SAP].
- Gartner. (2024, October 22). Gartner survey reveals that only 48% of digital initiatives meet or exceed their business outcome targets.
- Gartner. (2025). 4 actions to boost strategy performance management.
- McKinsey & Company. (n.d.). How the right operating model can close your performance gap.
- McKinsey & Company. (2026). The state of organizations.
