Most transformation programs fail before the delivery team makes its first mistake.
When programs fail, the standard responses follow a predictable pattern: more governance, tighter delivery management, larger PMOs. These responses address symptoms rather than causes. They assume the problem is execution when, more often, the structural conditions for success were never in place.
After two decades of leading and recovering transformation programs across government, defence, banking, logistics, and APAC commercial environments, I've observed a consistent pattern. Programs that succeed share five structural conditions. Programs that fail are usually missing one or more of them — and the gap is visible before delivery begins.
The Five Conditions
1. A shared definition of what the transformation is
Not a vision statement, but operational clarity. When I ask different stakeholders what the program is trying to achieve, do they give the same answer? When the definition varies by audience — "digital transformation" to one group, "cost reduction" to another, "customer experience" to a third — the program is already fragmented. Every team is executing against a different objective.
2. Governance that makes decisions, not just holds meetings
The test is simple: when an issue is escalated, how long does it take to get a decision? If governance committees review issues but defer decisions, if they request more information instead of resolving trade-offs, if escalation leads to further escalation — then governance is not functioning. It is producing documentation, not outcomes.
3. A delivery model designed for this program
Most programs inherit their delivery model from a previous initiative or from organisational habit. The methodology was designed for something else. The reporting cadence was inherited. The team structure reflects what was available, not what was needed. When I see a program in trouble, I often find a delivery model that was never fit for purpose — but no one stopped to ask.
4. Stakeholders who share a definition of progress
Different stakeholders measure success differently. Technology measures delivery. Business measures adoption. Finance measures cost. When these measures conflict — when a project can be "on track" by one definition and "failing" by another — the program is operating without a shared reality. Everyone reports green. The program still fails.
5. Someone accountable for benefits after the program director leaves
The most common failure mode: a program is delivered on time and on budget, declared a success, and produces no business impact. The delivery team has moved on. No one owns what happens next. Value realisation requires someone who will still be accountable after the program closes — and that accountability needs to be established before delivery begins.
The Diagnostic
These five conditions form the basis of my Integrated Transformation Execution Framework (ITEF). The framework is designed for program entry — asking, before resources are committed, which of these conditions is already fragile.
The answer determines whether you're building on solid foundations or setting up a program that will require heroic effort to save — effort that usually fails, because the structural weakness was never addressed.
I've applied this framework at Airservices Australia, NCR Corporation, and Visy Global Logistics. In each case, the diagnostic revealed structural risks that would not have been visible in traditional delivery metrics — risks that, left unaddressed, would have surfaced too late to correct.
The premise is simple: if you can identify where a program is structurally weak, you can address it before it fails. If you wait for delivery metrics to reveal the problem, you've already lost.