ITEF is built on a single premise: transformation programs do not fail because of poor delivery. They fail because one or more of the five foundational conditions was never structurally sound. By the time that failure is visible in a dashboard, the structural conditions that caused it have been in place for months.
Fixing delivery when the problem sits at governance or strategic clarity is like tightening the bolts on a structurally compromised frame.
Strategic Clarity
Is the transformation clearly defined — and is that definition shared?
The most common and least diagnosed failure mode. Country leads, business units, and delivery teams carry different versions of the program's objective. Each one is executing to brief. None of them are executing to the same brief.
The divergence is rarely visible early. It surfaces when a decision needs to be made that requires a shared definition — and none exists.
Governance Strength
Are the right decisions made by the right people at the right time?
Governance failure is slow and deniable. Issues compound across reporting cycles. Decisions that should be made at steering committee level sit unresolved in a working group. By the time the problem is visible in a dashboard, the structural conditions that caused it have been in place for months.
Most governance structures are designed to document, not decide. A board that only reviews delivery metrics is governing one layer too late.
Execution Architecture
Is the delivery model designed for this program — or inherited from the last one?
Every program borrows its delivery framework from somewhere. The risk is not the borrowing — it is the assumption that because it worked before, it will work here. Programs with different structural profiles, different stakeholder maps, and different risk profiles require different execution models.
The delivery team that is heroically executing against a structure that was never designed for what they are building will eventually reach its limits.
Stakeholder Alignment
Do all critical parties share a definition of progress and success?
The most frustrating failure mode to diagnose — because everyone is acting in good faith. Both sides report green. Neither is wrong. The program is still failing, because green means different things to different people.
In cross-agency programs and APAC rollouts, this divergence operates across organisational cultures and reporting structures simultaneously. What one organisation calls aligned, another is actively disputing internally.
Value Realisation
Who is accountable for benefits after the program director exits?
Delivery accountability ends at go-live. Business accountability for benefits often begins — and ends — with the program closure report. No named owner, no measurement framework, no sustained outcome. The organisation declares success on the delivery metrics and quietly absorbs the missing benefits.
On the NCR Southeast Asia restructure, USD 200K in annual savings were sustained because benefit owners were named and accountable before program close. The benefits held because the structure held.
How I use it
At program entry: To identify which layer is already fragile and what that means for the layers above it. This is the most valuable application — intervention at the point where cost of change is lowest.
At governance reviews: To give boards and steering committees a structured way to assess program health beyond delivery metrics. A red-amber-green dashboard tells you what is visible. ITEF tells you what is structural.
In program recovery: When a program is already in trouble, the visible problem is almost always Layer 3 or 4. The root cause is almost always Layer 1 or 2. ITEF locates it.
Where it has been applied
The ITEF diagnostic has informed program leadership across Airservices Australia (safety-critical government, cross-agency with Defence), NCR Corporation (USD 75M APAC portfolio, 14 countries), and Visy Global Logistics (operational transformation, 5 countries). It is not a theoretical framework. It is what I actually use.