What 22,000 Projects Reveal About Success and Failure
Why It Matters
Understanding that true project success hinges on value creation, not just on‑time‑on‑budget delivery, forces organizations to invest in rigorous planning, ultimately improving ROI and reducing waste.
Key Takeaways
- •Planning investment of 20‑30% dramatically improves project outcomes.
- •Only 0.5% of projects meet budget, schedule, and benefits simultaneously.
- •Success can occur despite overruns; value creation outweighs cost overruns.
- •Agile without thorough front‑end planning risks accelerating failure.
- •Historical data from 22,000 projects highlights importance of realistic forecasts.
Summary
The Shift Code podcast hosts Alexander Budzier, an Oxford professor, discussing his research on 22,000 projects to redefine what constitutes project success. Rather than relying solely on the traditional Iron Triangle of cost, schedule and scope, Budzier argues that a project should be judged by the net value it creates relative to its investment.
The data reveal stark realities: roughly half of all projects stay within budget, but only about eight percent meet both budget and schedule targets. When benefits are added to the equation, a mere 0.5 % of projects achieve all three criteria. Nonetheless, about half of the initiatives generate enough value to be considered successful, even if planning was unrealistic.
Illustrative cases underscore the paradox. The Sydney Opera House exceeded cost and time limits yet transformed the city’s economy, while Lidl’s €500 million IT platform delivered on schedule and won awards but was abandoned for lacking business fit. Budzier also cites the Madrid metro and a nuclear plant where extensive front‑end work proved essential.
The findings compel leaders to allocate a larger share of resources—often 20‑30 % of total cost—to thorough planning and realistic forecasting. Agile methods that skip this stage risk technical debt and failure, whereas disciplined upfront analysis can boost ROI and reduce the odds of costly overruns.
Comments
Want to join the conversation?
Loading comments...