Why Projects Still Fail – Even When They Are Delivered on Time and on Budget
The delivery paradox: projects can achieve every traditional metric and still fail to deliver the business result. The ICxA research across 1,406 organizations explains why – and why it is not your fault.
It Is Not About Execution
When a project is delivered on time, on budget, and within scope – and still fails to produce the intended business result – the instinctive response is to look for what went wrong. Who dropped the ball? Which team underperformed?
The ICxA research across 1,406 organizations globally suggests a different answer. This pattern is not the result of isolated poor performance. It is the result of a structural condition that affects nearly every organization in the industry, regardless of region, industry, or stakeholder type.
The current project delivery model is highly effective at governing activities – engineering, construction, commissioning, handover. Each phase is well-managed. What the model does not consistently do is govern whether those activities converge into an operational result that performs as intended. As the research states: “The system does not fail within activities. It fails between them.”
The Five Governance Gaps – Where the System Breaks Down
The Outcome Assurance Index (OAI) assesses five pillars of organizational capability. Together, they reveal not isolated weaknesses but a consistent structural imbalance across the global industry. Execution-oriented capabilities are relatively developed; governance and outcome delivery are not.
1. Outcome Governance – 25 / 100
Governance is not absent in capital projects. Projects are governed through schedules, budgets, milestones, approvals, and compliance structures. What is rarely present is governance explicitly tied to whether the intended outcome will be achieved. Governance is directed at activity completion – not outcome readiness. If governance does not reference outcomes, it cannot fully control them.
2. System Integration – 30 / 100
Integration activities are visible and widely practiced. Interfaces are managed, disciplines are coordinated. But integration functions primarily as coordination rather than control. Systems are brought together so work can proceed; they are less consistently governed to ensure the combined system will achieve its intended outcome.
3. Operational Readiness – 39 / 100
The strongest pillar – and yet overall Outcome Assurance remains low, introducing a contradiction. Preparation is not the same as demonstrated readiness under real operating conditions. Operational readiness appears to function more as a compliance activity than as a risk-driven process oriented to outcomes. Checklist completion and genuine operational readiness are not the same thing.
4. Performance Validation – 40 / 100
The highest-scoring pillar. Testing programs are implemented and systems are verified. But validation functions as confirmation rather than control. Evidence is produced; it does not consistently govern progression decisions. Testing confirms completion. In a higher-maturity model, validation authorizes progression.
5. Outcome Delivery – 24 / 100
The lowest-scoring pillar – and the one that matters most. Outcome Delivery is the point at which all preceding activity is expected to converge. Despite capability across other pillars, explicit ownership of the final result is rarely present. Outcomes are often expected to follow from execution. They are less often governed as a condition that must be demonstrated.
The Cross-Pillar Imbalance: Why the System Cannot Converge
The most revealing finding is not any individual pillar score – it is the imbalance between them. Execution-oriented capabilities (Operational Readiness at 39, Performance Validation at 40) are relatively well-developed. The control-and-accountability capabilities (Governance at 25, Outcome Delivery at 24) are significantly lower.
This imbalance appears sufficient to limit how effectively the system converges. Activity increases, but outcome certainty does not increase at the same rate. As the research concludes: “Each part is improving. The outcome is not.”
Without governance aligned to outcomes, the system lacks a mechanism to convert capability into assurance. Activities may be performed with increasing rigor – but their contribution to the final result remains uncertain.
“Everybody understands responsibilities. Nobody owns the outcome.”
– ICxA Outcome Assurance Gap Report
What Changes Everything: An Outcome-Based Governing Logic
The research does not suggest the industry must replace what it has built. It suggests a need to extend it. The capabilities required to achieve outcomes already exist across the industry. What appears less developed is the system that connects those capabilities into a single outcome-oriented governing logic.
Higher-maturity organizations – the few that approach the upper range of observed performance – share a set of distinguishing characteristics: they define explicit ownership of the intended outcome; they govern readiness, not just completion; they introduce evidence-based stage-gates tied to progression decisions; they extend validation beyond technical completion; and they maintain accountability continuously across handovers.
This is the shift from a delivery-based model to an outcome-based project delivery model – one in which the outcome is not treated as a downstream result of delivery, but as the reference point that governs it.
“The capability exists. The system does not.” Building that system is what ICxA exists to support.
Get the Framework to Close the Outcome Assurance Gap
The ICxA Outcome Leadership membership gives project managers and PMO leaders access to the frameworks, standards, and community built specifically to govern outcomes – not just deliver activities.