The direct cost is what gets reported. The real cost — indirect, long-term, and organizational — is typically two to five times larger. Here’s how to calculate it.
When IT projects fail, the cost that gets reported is usually the direct project spend: the budget allocated, the amount spent before cancellation, the overrun explained to the board. That’s the visible cost. The real cost is much larger. Understanding the full cost changes the calculus around investment in prevention.
The Direct Costs: What Gets on the Balance Sheet
Wasted development investment. For cancelled projects, the entire development spend is a write-off. For projects that fail to deliver expected value, a large portion of spend produced outcomes that don’t justify the investment.
Rework. Research estimates that rework accounts for 40 to 50 percent of total IT staff time, and 75 percent of rework is directly attributable to requirements problems.
Overruns. McKinsey’s research found an average budget overrun of 45 percent for large IT projects. For a $10 million project, that’s $4.5 million in overrun.
Cancellation costs. Projects that are cancelled have often incurred vendor contracts, licensing fees, and infrastructure investments that can’t be recovered.
PMI’s research estimated that organizations lose/waste an average of $97 million in direct costs for every $1 billion invested in projects due to poor performance.
The Indirect Costs: What Doesn’t Appear in Project Accounting
Lost opportunity cost. Every failed project represents a business capability that wasn’t delivered. For a customer-facing system supposed to reduce churn by two percentage points, the opportunity cost is two percentage points of annual churn, multiplied by customer lifetime value, for every year the system is delayed.
Operational continuity burden. Failed projects often leave organizations operating legacy systems longer than planned and absorbing the ongoing operational costs of systems that don’t fit how the business needs to work.
Employee productivity loss. Team members who spent months on a failed project lose those months of productivity. Morale impacts from high-profile failures affect productivity and retention. Key people leave.
Organizational trust erosion. Perhaps the most underestimated indirect cost. When projects fail, business leaders draw conclusions about IT’s ability to deliver. Future IT initiatives face skepticism and political resistance. Business units develop shadow IT as a defensive response. Rebuilding trust after a pattern of failures is expensive and slow.
Customer and competitive impact. A capability that was supposed to create competitive differentiation, delivered late or not at all, cedes advantage to competitors who weren’t waiting.
Calculating the True Cost: A Framework
Applying this framework to most IT projects produces a true cost that is two to five times the direct project cost. A $5 million failed project typically represents $10 million to $25 million in true organizational cost.
Direct project costs: Total project spend (including overrun) minus value delivered.
Rework and remediation: Costs of fixing what was built wrong.
Opportunity cost: The value of the business outcomes that were supposed to be delivered, for the duration of the delay or non-delivery.
Operational continuity costs: Additional ongoing costs of running legacy systems or operating suboptimally.
Organizational costs: Estimated cost of trust erosion — reduced business engagement, shadow IT development, IT staff attrition — over a two-to-three year horizon.
What Prevention Costs vs. What Failure Costs
Better requirements processes add cost to the early phase of a project — typically 5 to 15 percent of total project budget. Against a 45 percent average overrun for large projects, and against the true cost calculation that’s two to five times the accounting cost, the investment in prevention is one of the highest-return investments available.
Making the Business Case
The conversation isn’t “we should spend more time on requirements because it’s the right way to do projects.” The conversation is: “Our last major project failure cost us $X in direct costs and $Y in indirect costs, totaling $Z. The investment required to prevent a similar failure is W. The expected value of that investment is strongly positive.”
→ If you’re approaching a significant project where the true cost of failure would be substantial, the investment in a better requirements process is the investment with the best risk-adjusted return available. Our training program gives project managers and their teams the methodology to get requirements right.
Explore the course → bridgingbusinessit.com/the-course/
