{"id":26281,"date":"2026-06-11T12:28:56","date_gmt":"2026-06-11T00:28:56","guid":{"rendered":"https:\/\/www.psoda.com\/global\/?p=26281"},"modified":"2026-06-11T13:07:34","modified_gmt":"2026-06-11T01:07:34","slug":"hidden-costs-project-failure","status":"publish","type":"post","link":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/","title":{"rendered":"The Real Cost of Project Failure: What Your CFO Doesn&#8217;t See"},"content":{"rendered":"<p><em>Project failures cost infrastructure operators millions annually but the visible budget overruns are just the tip of the iceberg.<\/em><\/p>\n<p style=\"text-align: center;\"><span style=\"font-size: 18pt;\"><strong style=\"color: red;\">$4M+<\/strong><\/span><\/p>\n<p>That&#8217;s what a single failing $10M infrastructure project actually costs. The CFO sees a $1M overrun. The real bill is three to five times that.<\/p>\n<p>When a project fails, the CFO sees a $10M project that cost $11M. The $1M overspend is painful but manageable. What almost nobody sees is that the visible $1M has dragged a much larger bill behind it in costs that never make it into the report. Using that $1M as an example, the three to five times multiplier pushes the true cost to somewhere between $3M and $5M. This isn&#8217;t an isolated incident either. This pattern repeats across every failed, delayed or troubled project in your portfolio. The Project Management Institute found that organisations ineffective at project management waste 21 times more money than high-performing ones. For a lines company managing a $50M capital works programme, a council running a long-term infrastructure plan or a government agency delivering a complex transformation programme, that&#8217;s not a footnote. It&#8217;s the difference between hitting your targets and explaining to stakeholders why you didn&#8217;t.<\/p>\n<p>In over two decades working with NZ infrastructure operators across energy networks, councils and government agencies, we&#8217;ve analysed the cost of project failure across hundreds of projects and found nine major cost categories that rarely, if ever, make it into the post-project report. This article will share each one, show you how to measure it and give you practical strategies to prevent it, whether you use a PPM tool like Psoda or not.<\/p>\n<h2><span style=\"font-size: 12pt;\">Why it matters for NZ infrastructure operators<\/span><\/h2>\n<p><a href=\"https:\/\/tewaihanga.govt.nz\/\">The NZ Infrastructure Commission, Te Waihanga<\/a>, put it plainly in its 2026 National Infrastructure Plan: New Zealand invested around 5.8% of GDP annually on infrastructure over the past 20 years, making us one of the top-spending countries in the OECD. Yet we rank towards the bottom for efficiency, or &#8216;bang for buck&#8217;. (<a href=\"https:\/\/tewaihanga.govt.nz\/national-infrastructure-plan-online\/foreword\">Te Waihanga, National Infrastructure Plan, 2026<\/a>)<\/p>\n<p>It gets worse. New Zealand ranks last in the OECD for infrastructure procurement governance; the processes and systems organisations use to scope, contract and deliver projects. Not near the bottom. Last. (Te Waihanga, National Infrastructure Plan, 2026) Te Waihanga&#8217;s own research has found that organisational and leadership factors, not technical issues, are the primary driver of cost overruns on major NZ infrastructure projects. It&#8217;s not the geology or the weather. It&#8217;s how projects are run.<\/p>\n<p>The scale of what&#8217;s at stake is enormous. The National Infrastructure Pipeline currently tracks 11,925 projects worth $275 billion in planning or delivery across New Zealand, with a workforce of more than 100,000 people delivering it across the infrastructure sector. (Te Waihanga, National Infrastructure Plan, 2026) That workforce will need to grow to 130,000 by 2035 to meet investment demand while already struggling to retain experienced people. Around 30% of electrical engineering and telecommunications technicians are already older than 55, concentrating the knowledge loss risk in exactly the occupations infrastructure operators need most (Te Waihanga, National Infrastructure Plan, 2026)<\/p>\n<p>The delivery track record against that pipeline is sobering. Infrastructure New Zealand reports that across projects of this type, just 27% come in on budget, 3% on budget and on time and only 0.2% on budget, on time and to the original quality specification. (<a href=\"https:\/\/infrastructure.org.nz\/wp-content\/uploads\/2023\/12\/Infrastructure-NZ-Policy-Postions-Delivery-of-Megaprojects.pdf\">Infrastructure NZ, Delivery of Megaprojects position paper, 2023<\/a>) An Ipsos survey found that only 17% of New Zealanders believe NZ has a good record of delivering national infrastructure projects, placing us tied last with Hungary across 32 countries. (<a href=\"https:\/\/www.ipsos.com\/en-nz\/2024-global-infrastructure-index-nz-edition\">Ipsos Global Infrastructure Index, 2024<\/a>) Infrastructure Minister Chris Bishop said the state of NZ&#8217;s public asset management would &#8216;shock&#8217; people. (<a href=\"https:\/\/www.stuff.co.nz\/nz-news\/360939242\/where-nz-failing-infrastructure-and-what-its-10-year-priorities-could-be\">Stuff, February 2026<\/a>) He was right.<\/p>\n<h3><span style=\"font-size: 12pt;\">The regulatory and reputational stakes<\/span><\/h3>\n<p>NZ&#8217;s infrastructure organisations face a level of public and regulatory scrutiny that most private sector businesses don&#8217;t. Lines companies have Commerce Commission disclosure obligations and price-quality path targets. Councils answer to elected members and ratepayers on every dollar of capital spend. Government agencies are accountable to Ministers and Treasury on project delivery and benefits realisation. Poor project management in this environment doesn&#8217;t just cost money. It creates regulatory exposure, damages public trust and puts long-term asset management plans at risk. As Te Waihanga noted, the public and the construction sector are becoming increasingly sceptical about announced project timeframes and budgets. That scepticism has a direct cost: it makes it harder to secure funding, harder to maintain stakeholder confidence and harder to deliver the next project.<\/p>\n<p>The pressure is growing. National infrastructure spending will climb from just over $20 billion per year today to more than $40 billion per year over the next 30 years, with around 60% of that investment targeting renewals and replacements rather than new builds (Te Waihanga, National Infrastructure Plan, 2026) The <a href=\"https:\/\/www.mbie.govt.nz\/building-and-energy\/building\/supporting-a-skilled-and-productive-workforce\/national-construction-pipeline-report\">MBIE National Construction Pipeline Report 2025<\/a> forecasts infrastructure activity growing from $16.9 billion in 2024 to $19.6 billion by 2030, with electricity and gas projects accounting for 17.4% of total infrastructure project value commencing in 2025 despite representing just 3% of project numbers. (MBIE, National Construction Pipeline Report, 2025) For the energy networks, councils and government agencies running capital programmes right now, the cost of poor project management is not shrinking. It&#8217;s compounding.<\/p>\n<p>Most organisations try to fix this with tactical responses:<\/p>\n<ul>\n<li>Adding governance layers that slow everything down without improving outcomes.<\/li>\n<li>Hiring more project managers who inherit the same broken systems.<\/li>\n<li>Producing more reporting that nobody reads.<\/li>\n<li>Buying new software without changing the processes underneath it.<\/li>\n<\/ul>\n<p>That&#8217;s treating symptoms rather than causes. To fix project failures you need to understand the full cost of failure and that means looking beyond the budget lines.<\/p>\n<h2><span style=\"font-size: 12pt;\">The 9 hidden costs of project failures<\/span><\/h2>\n<h3><span style=\"font-size: 12pt;\">1. The communication tax AKA death by meetings<\/span><\/h3>\n<p>Project teams spend an extraordinary amount of time in meetings. Status meetings, alignment meetings, steering committee preparations, contractor briefings and emergency meetings about why the last five meetings didn&#8217;t solve the problem. Sound familiar?<\/p>\n<h4>By the numbers<\/h4>\n<p>The average NZ worker spends 11.3 hours per week in meetings, with 5 of those hours estimated to be genuinely unproductive. (NZ Herald, Inspiring Performance NZ) For managers and senior staff, the programme managers, project directors and engineers who run infrastructure delivery, that burden rises to between 16 and 23 hours per week. The number of meetings has also tripled since 2020, driven by the rise of hybrid work. The coordination overhead has never been higher. (<a href=\"https:\/\/archieapp.co\/blog\/workplace-statistics\/\">Archie App, Meeting Statistics, 2026<\/a>)<\/p>\n<h4>How to calculate your coordination overhead:<\/h4>\n<ul>\n<li>Calculate the average hourly rate by dividing fully loaded annual cost by 2,080 hours.<\/li>\n<li>Use 5 hours per week as the NZ benchmark for unproductive meeting time per person.<\/li>\n<li>Multiply by number of project staff and 52 weeks.<\/li>\n<\/ul>\n<p><strong>Example:<\/strong> 50 project staff with a fully loaded cost of $150,000 per person:<br \/>\n$72.12 x 5 wasted hours x 50 staff x 52 weeks = <strong>$937,000 per year<\/strong><\/p>\n<h4>Fixing it without software:<\/h4>\n<ul>\n<li>No meeting without a written agenda circulated 24 hours beforehand.<\/li>\n<li>Every meeting must have a decision-maker present.<\/li>\n<li>Default lengths of 30 and 60 minutes, nothing in between.<\/li>\n<li>Store minutes in a shared searchable location and record decisions and actions.<\/li>\n<li>A monthly meeting audit: any meeting that hasn&#8217;t produced a decision in 60 days gets cancelled.<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">2. Rework<\/span><\/h3>\n<p>Rework is the hidden cost nobody tracks. It doesn&#8217;t appear as a separate line item. It shows up as &#8216;it&#8217;s taking a bit longer than expected&#8217; or &#8216;the requirements turned out to be more complex than we thought.&#8217; Putting it bluntly: it&#8217;s waste.<br \/>\nIn NZ, the average organisation spends 16% of total project time on rework. Large businesses report higher rates, around 20% of project time, compared to 13% for smaller organisations. (Infrastructure News NZ, 2026) Design errors are the dominant driver, contributing up to 70% of total rework costs. (Avanza Solutions, The True Cost of Construction Rework in New Zealand, 2026) For infrastructure operators, those design errors take a specific form: field crews building to superseded drawings, contractors working from specs someone updated three weeks ago without telling them and coordination failures between design disciplines that only surface on site.<\/p>\n<h4>Common rework triggers:<\/h4>\n<ul>\n<li>Unclear scope: Work begins before anyone has properly defined what done looks like.<\/li>\n<li>Outdated information: A field crew builds to an old drawing. A team delivers to a spec that someone replaced three weeks ago and forgot to update.<\/li>\n<li>Late stakeholder input: An executive with no prior involvement in the project suddenly has strong opinions at the 80% mark and expects everyone to act on them.<\/li>\n<li>Contractor handoffs: Contractors complete work to the wrong standard because nobody distributed the updated requirements.<\/li>\n<li>Technical debt: &#8216;We&#8217;ll fix it properly later&#8217; shows up on the rework bill six months down the track.<\/li>\n<\/ul>\n<h4>How to calculate the cost of rework:<\/h4>\n<p>NZ research indicates rework typically accounts for 5-15% of total project value, with large organisations trending toward the higher end of that range. Using a conservative 15% on a $150M annual project portfolio: (Avanza Solutions, The True Cost of Construction Rework in New Zealand, 2026)<br \/>\n$150,000,000 x 0.15 = <strong>$22.5M per year<\/strong><\/p>\n<h4>Fixing it without software:<\/h4>\n<ul>\n<li>One source of truth: Even without document management software, a single shared folder with a clear naming convention eliminates the wrong-version problem. If the document isn&#8217;t in that folder, it doesn&#8217;t exist. Given that design errors drive up to 70% of rework costs, version control is the single highest-return fix available.<\/li>\n<li>The three-line summary: Before any work begins, have the person doing it send a three-line summary of what they&#8217;re about to build. If the requester doesn&#8217;t agree with the summary, work doesn&#8217;t start. Measure twice, cut once.<\/li>\n<li>Fortnightly stakeholder briefs: Ten minutes every two weeks is cheaper than three months of rework at the end of a project.<\/li>\n<li>Technical debt list: Every time someone says &#8216;we&#8217;ll fix it later&#8217;, add it to a list. Review it at every milestone and make it a rule that new work can&#8217;t start until a minimum of two items are cleared. <span class=\"TrackChangeTextInsertion TrackedChange TrackChangeHoverSelectColorRed SCXW232152429 BCX0\"><span class=\"TextRun SCXW232152429 BCX0\" lang=\"EN-NZ\" xml:lang=\"EN-NZ\" data-contrast=\"auto\"><span class=\"NormalTextRun TrackChangeHoverSelectHighlightRed SCXW232152429 BCX0\">Better yet,\u00a0<\/span><\/span><\/span><span class=\"TrackChangeTextInsertion TrackedChange TrackChangeHoverSelectColorRed SCXW232152429 BCX0\"><span class=\"TextRun SCXW232152429 BCX0\" lang=\"EN-NZ\" xml:lang=\"EN-NZ\" data-contrast=\"auto\"><span class=\"NormalTextRun TrackChangeHoverSelectHighlightRed SCXW232152429 BCX0\">don\u2019t<\/span><\/span><\/span><span class=\"TrackChangeTextInsertion TrackedChange TrackChangeHoverSelectColorRed SCXW232152429 BCX0\"><span class=\"TextRun SCXW232152429 BCX0\" lang=\"EN-NZ\" xml:lang=\"EN-NZ\" data-contrast=\"auto\"><span class=\"NormalTextRun TrackChangeHoverSelectHighlightRed SCXW232152429 BCX0\"> leave more than two items on the list, ever.<\/span><\/span><\/span><\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">3. Projects that fail or get cancelled<\/span><\/h3>\n<p>Every organisation has projects that get cancelled after significant investment. A 2026 industry survey found that 15% of projects are considered outright failures and 70% of organisations suffered at least one project failure in the prior 12 months. (Infrastructure NZ, 2026) What makes this so damaging is that projects tend to fail late, typically after 60% to 80% of the budget has already been spent.<\/p>\n<p>The pattern is visible at every scale in NZ. The government spent $507 million on cancelled iReX ferry plans. The government cancelled Auckland Light Rail after years of planning and significant investment. The government&#8217;s own 100-day plan in 2024 identified nearly $2 billion in previously committed funds as effectively wasted on projects that were cancelled or fundamentally altered. (University of Auckland, Why Are We So Bad at Infrastructure Planning, 2025; 1News, 2024) These are the headline cases. The same pattern of late cancellation, significant sunk cost and nothing to show plays out quietly across infrastructure portfolios every year.<\/p>\n<p>Failed and stalled projects also create a stop-start effect across the wider portfolio. The resources tied up in a failing project, the engineers, project managers and budget headroom can&#8217;t be redeployed until someone makes the call to stop. The longer that call is delayed, the more damage compounds.<\/p>\n<h4>The top five reasons projects fail:<\/h4>\n<ul>\n<li>The executive sponsor lost interest or left the organisation.<\/li>\n<li>Nobody properly defined the scope and it grew until the budget couldn&#8217;t contain it.<\/li>\n<li>Overly optimistic planning met reality and never recovered.<\/li>\n<li>Third-party or contractor performance fell short of what was promised.<\/li>\n<li>The organisational priority changed and the problem being solved stopped being a problem.<\/li>\n<\/ul>\n<h4>How to calculate the cost:<\/h4>\n<p>15 projects per year, 15% failure rate, $10M average budget, 80% of budget spent at failure:<br \/>\n15 x 0.15 x $10,000,000 x 0.8 = <strong>$18M per year<\/strong><\/p>\n<h4>Fixing it without software:<\/h4>\n<ul>\n<li>An exit criteria contract: At project kickoff, get a signed agreement with the sponsor that defines three conditions that would trigger an immediate pause. It makes it safe to raise concerns early rather than waiting until it&#8217;s too expensive to stop.<\/li>\n<li>A pre-mortem: Ask the team at the start: it&#8217;s a year from now and the project spectacularly failed. Why? Those answers become your risk register.<\/li>\n<li>Sponsor engagement tracking: A simple red\/amber\/green rating on whether the sponsor attended the last three briefings. Low engagement is the most reliable leading indicator of project failure.<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">4. Staff turnover and knowledge loss<\/span><\/h3>\n<p>Nobody wants to work in an environment where projects consistently fail, sponsors disappear and the same problems repeat month after month. Gallup&#8217;s research shows that when people feel their work is valued and well-organised, engagement goes up significantly. The reverse is equally true.<br \/>\nFor infrastructure operators, the knowledge loss problem is acute and getting worse. Te Waihanga&#8217;s National Infrastructure Plan found that around 30% of electrical engineering and telecommunications technicians in NZ are aged 55 or over, concentrating the knowledge loss risk in exactly the occupations infrastructure operators depend on most. An experienced project manager or engineer who leaves takes with them years of institutional knowledge that doesn&#8217;t sit in any system: which projects are genuinely at risk versus which ones just look bad on paper, which contractors can be trusted on complex deliveries, which stakeholders need to be managed carefully.<\/p>\n<p>While NZ&#8217;s national staff turnover rate was 21.4% in 2023, infrastructure project roles run significantly higher. (Lawson Williams, 2024 NZ Staff Turnover Report) The Infrastructure NZ 2025 Industry Survey found that project managers in NZ infrastructure average 44.9% annual turnover, with coordinators at 48.7%. Across the sector, 45% of organisations reported increased attrition due to overseas opportunities in 2025 and 61% of employees in project roles are either intending to leave or are unsure about staying. (Infrastructure NZ, 2025 Industry Survey) If anything, these figures are getting worse, not better. Demand for engineers and technical staff grew 17.6% in 2025 while supply continued to tighten.<\/p>\n<p>Replacing a mid-level project employee costs roughly 150% of their fully loaded annual cost by the time you factor in recruitment fees, onboarding time, lost productivity and the knowledge gap. For a senior engineer or project manager the figure can exceed 200%.<\/p>\n<h4>How to calculate it:<\/h4>\n<p>50 project staff, 40% annual turnover (conservative blended rate for infrastructure project roles), $150,000 fully loaded cost per person:<br \/>\n50 x 0.40 x $150,000 x 1.5 = <strong>$4.5M per year<\/strong><\/p>\n<h4>Fixing it without software:<\/h4>\n<ul>\n<li>Shadow assignments: The moment someone announces they&#8217;re leaving, assign a buddy whose job during the notice period is capturing the knowledge in that person&#8217;s head. Not the job description, the actual how-to knowledge.<\/li>\n<li>Consistent recognition: Public acknowledgement of good work costs nothing and has an outsized effect on retention. Whether it&#8217;s a shout-out in the weekly stand-up or something more formal, people stay longer when their work is seen.<\/li>\n<li>Career pathways: Infrastructure project staff leave when they can&#8217;t see a future. A visible career framework that rewards delivery performance over tenure gives people a reason to stay.<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">5. Scope creep<\/span><\/h3>\n<p>Scope creep is an insidious budget blower. NZ construction research documents a budget drift of approximately 23.86% across projects, with major infrastructure projects frequently experiencing variances of 20-30% or more. (NZ Journal of Applied Business Research; ScienceDirect, 2026) Research consistently identifies scope changes as one of the top three drivers of that drift, alongside optimism bias and external market factors. Most scope changes never get formal approval. They just happen and the budget disappears.<\/p>\n<p>In infrastructure delivery, scope creep has a particularly stubborn form: you start replacing poles on a 5km section of line and discover the crossarms need replacing too. You begin a council facility upgrade and find asbestos in the walls. You scope a data migration for a government agency and discover the source data is far messier than anyone admitted. Each discovery is legitimate. The cost still compounds.<br \/>\nThe flat 10% contingency that most NZ projects budget for is consistently found to be insufficient for complex infrastructure delivery. (Prendos NZ, How Accurate is a Cost Estimate) It covers the known unknowns. It doesn&#8217;t cover scope creep, late stakeholder input or the field discoveries that only surface once work is underway.<\/p>\n<h4>How to calculate it:<\/h4>\n<p>15 projects at $10M average budget, 20% scope creep, which is conservative relative to the 23.86% NZ average budget drift:<br \/>\n15 x $10,000,000 x 0.20 = <strong>$30M per year<\/strong><\/p>\n<h4>Fixing it without software:<\/h4>\n<ul>\n<li>Written change requests, no exceptions: Nothing changes without a written request that gets reviewed and assessed against time, scope and budget. Feed back the result to whoever submitted it.<\/li>\n<li>The field discovery protocol: Define in advance what the team should do when they discover something outside scope. The answer should never be &#8216;just fix it and we&#8217;ll sort the paperwork later&#8217;.<\/li>\n<li>Realistic contingency: A flat 10% contingency is a starting point, not a risk strategy. For complex infrastructure delivery, a separate risk-based reserve held outside the project budget is the only way to absorb genuine unknowns without triggering a scope conversation every time something unexpected surfaces.<\/li>\n<li>Communicate every change: Every approved change gets communicated to all stakeholders. Surprises at project close are almost always scope changes nobody told anyone about.<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">6. Poor resource allocation<\/span><\/h3>\n<p>A previous analysis of NZ commercial construction found that only one-third of a typical project budget actually delivers the physical asset. The remainder is absorbed by overheads, waste and inefficiencies. (Stuff, Poor project management blamed for construction budget blowouts) Poor resource allocation sits at the heart of that gap.<br class=\"yoast-text-mark\" \/>Without clear visibility into who is allocated to what, your best people end up carrying too many projects simultaneously, sitting idle waiting for decisions or being pulled off priority work for something urgent that should have been planned for. The problem is compounded by NZ&#8217;s ongoing shortage of skilled engineers and technical personnel. When your resource pool is constrained, misallocation costs more, not less.<\/p>\n<p>For infrastructure operators this problem has a specific shape: capital delivery and business-as-usual maintenance compete for the same engineers and project managers. When a network fault hits or a council emergency comes in, capital gets paused. When capital hits a delivery crunch, maintenance slips. Neither outcome is good and neither shows up clearly in a project report. Many teams still manage this across spreadsheets rather than dedicated systems, making it nearly impossible to see conflicts early enough to act on them. (Xigo NZ, Planning Phase Scheduling and Resource Allocation)<\/p>\n<h4>How to calculate it:<\/h4>\n<p>50 project staff at $150,000 fully loaded cost, 15% resource allocation waste:<br \/>\n50 x $150,000 x 0.15 = <strong>$1.125M per year<\/strong><\/p>\n<h4>Fixing it without software:<\/h4>\n<ul>\n<li>The rule of two: No one is assigned to more than two projects at once. If a third is added, one of the original two must be officially paused in writing.<\/li>\n<li>The Friday check-in: Every Friday afternoon, ask the team whether they have everything they need to work on Monday. If the answer is no, that&#8217;s the manager&#8217;s problem to solve before 5pm.<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">7. Delays<\/span><\/h3>\n<p>Major infrastructure projects frequently face delays measured in years. (<a href=\"https:\/\/nzinfrastructure.nz\/the-time-to-change-is-now\/#:~:text=To%20meet%20the%20needs%20of,pipeline%20and%20policy%20flip%2Dflopping.\">Infrastructure NZ, The Time to Change is Now<\/a>) A delayed capital project doesn&#8217;t just incur the cost of the delay. Ageing assets staying in service longer than planned. For a council, it means a community benefit that doesn&#8217;t arrive on schedule. Government agencies find themselves explaining to Ministers why policy outcomes have slipped. Around 17% of infrastructure projects also incur material holding costs from consenting delays alone, averaging a 1.7% increase in project budget before anyone makes a single delivery decision. (<a href=\"https:\/\/tewaihanga.govt.nz\/our-work\/research-insights\/the-cost-of-consenting-infrastructure-projects-in-new-zealand\">Te Waihanga, The Cost of Consenting Infrastructure Projects in New Zealand<\/a>) The direct delay cost is real but it&#8217;s rarely the biggest cost of being late.<\/p>\n<p>New research by Shamubeel Eaqub quantifies exactly what delay costs in NZ. Pausing a $500M state highway upgrade for three years costs $284M, 56.7% of the original project value and drops the benefit-cost ratio from 2.2 to 1.7. Pausing a $50M council water treatment upgrade for two years costs $26.7M, 53.4% of project value. As Eaqub concluded: \u201cPausing a project costs roughly half its value in combined direct costs and deferred benefits.\u201d (<a href=\"https:\/\/civilcontractors.co.nz\/Pages\/SYSTEM\/Utility\/Download.aspx?id=8a65ff0c-6bba-4b1b-afcf-cafe27d37f0a&amp;newtab=1\">Eaqub, Cost of Stopping, commissioned by Civil Contractors NZ, Infrastructure NZ and Water NZ, May 2026<\/a>) The pattern is consistent across project types and sizes. A project that was worth doing before the pause is still worth doing after. But it delivers less per dollar, takes longer to restart than anyone plans for and the workers who knew how to build it have moved on.<\/p>\n<h4>How to calculate the direct delay cost:<\/h4>\n<p>15 projects, 30% delayed, $10M average budget, 2-month average delay:<br \/>\n($10,000,000 \/ 12) x 2 months x 4.5 delayed projects = <strong>$7.5M per year<\/strong><\/p>\n<h4>Fixing it without software:<\/h4>\n<ul>\n<li>The secret buffer: Whatever the estimate, add a management reserve of 20%. Tell no one. Use it only for genuine unforeseen issues, not as a cushion for poor planning.<\/li>\n<li>The known buffer: Add a 20% contingency to the end of every stage. This one is visible to the team and can be drawn on as needed. Having both buffers gives you flexibility without encouraging complacency.<\/li>\n<li>The escalation clock: Agree upfront that anything blocking progress will be escalated after a defined period. This stops problems sitting in someone&#8217;s inbox festering until they&#8217;re too big to fix cheaply.<\/li>\n<li>The fortnightly delivery review: A 30-minute forward-looking conversation with the delivery lead every two weeks. Not a progress update, a question: what might stop delivery in the next six weeks and what are we doing about it now?<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">8. Lost opportunity<\/span><\/h3>\n<p>When projects fail or are significantly delayed, the resources tied up in them can&#8217;t be deployed elsewhere. The direct cost isn&#8217;t the whole story. Every failed capital project is a network reliability improvement that didn&#8217;t happen, a community facility that didn&#8217;t open, a policy outcome that wasn&#8217;t delivered. Every delayed project is an asset management plan commitment showing red.<br \/>\nWe calculate opportunity cost conservatively at 50% of the direct failure cost. In practice, for organisations where project outcomes drive regulatory compliance, public trust or long-term asset performance, the true opportunity cost is often significantly higher.<\/p>\n<p>Eaqub\u2019s research puts a precise figure on the deferred benefit cost. Using a conservative benefit-cost ratio of 1.5, NZ has lost $1 billion in deferred community benefits from stop-start investment over the past 25 years. At a more typical BCR of 2.0 the figure reaches $3.2 billion. These are deferred benefits and not permanently lost but the years of waiting cannot be recovered. (Eaqub, Cost of Stopping, May 2026)<\/p>\n<p>We calculate opportunity cost conservatively at 50% of the direct failure cost. In practice, for organisations where project outcomes drive regulatory compliance, public trust or long-term asset performance, the true opportunity cost is often significantly higher.<\/p>\n<h4>How to calculate it:<\/h4>\n<p>Using the project failure cost from category 3:<br \/>\n$18M x 0.50 = <strong>$9M per year<\/strong><\/p>\n<h4>Fixing it without software:<\/h4>\n<ul>\n<li>The waitlist: Keep a visible list of every new opportunity waiting to start. The rule is that a new opportunity can&#8217;t be activated until a current project is finished or officially stopped. This creates a forcing function for hard decisions.<\/li>\n<li>Quarterly opportunity review: Once a quarter, review the waitlist against the current portfolio. If a waiting opportunity is clearly more valuable than a dragging current project, be brave and make the call to stop one and start the other.<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">9. Regulatory and compliance reporting overhead<\/span><\/h3>\n<p>This cost category is unique to regulated infrastructure operators and the one most generic PPM tools have never thought about.<\/p>\n<p>Lines companies face Commerce Commission Information Disclosure requirements. Councils produce long-term plans and infrastructure strategies that require accurate capital programme data. Government agencies report to Treasury and Ministers on project delivery and benefits realisation. In every case, if your project and asset data lives across spreadsheets, email chains and disconnected field systems, assembling that reporting is an enormous manual undertaking every single time.<\/p>\n<p>We regularly see infrastructure organisations spending three to four weeks of senior staff time per year on nothing but hunting down data, reconciling inconsistencies and formatting reports for regulators, elected members or Treasury officials. That&#8217;s not project delivery. That&#8217;s manual data assembly that a well-configured PPM platform eliminates.<\/p>\n<h4>How to calculate it:<\/h4>\n<p>Five senior staff spending eight weeks each on compliance reporting at a fully loaded rate of $72.12 per hour:<br \/>\n5 staff x 8 weeks x 40 hrs x $72.12 = approximately <strong>$115,000<\/strong> per year in direct labour<\/p>\n<p>That figure doesn&#8217;t include management review time, the risk of errors in the disclosure or the cost of dealing with queries about data inconsistencies. For organisations with multiple regulatory reporting obligations the real cost is considerably higher.<\/p>\n<h4>Fixing it without software:<\/h4>\n<p>This is the hardest category to address without an integrated platform. The best analogue approach is to build a single source of truth for project and asset data and run a quarterly compliance readiness check rather than assembling everything under pressure at year-end.<\/p>\n<h2><span style=\"font-size: 12pt;\">What it all adds up to<\/span><\/h2>\n<p>For an infrastructure organisation running 15 projects at an average of $10M in a $150M annual portfolio with 50 project staff at a fully loaded cost of $150,000 per person, a conservative estimate across all nine categories looks like this:<\/p>\n<ul>\n<li>Coordination overhead: $937,000<\/li>\n<li>Rework: $22.5M<\/li>\n<li>Failed projects: $18M<\/li>\n<li>Staff turnover: $4.5M<\/li>\n<li>Scope creep: $30M<\/li>\n<li>Resource allocation waste: $1.125M<\/li>\n<li>Delays: $7.5M<\/li>\n<li>Lost opportunity: $9M<\/li>\n<li>Compliance overhead: $115,000+<\/li>\n<\/ul>\n<p>Total: <strong>over $93.6M in hidden costs annually.<\/strong><\/p>\n<p>These figures are based on published research benchmarks applied to a realistic NZ infrastructure project portfolio. Use our calculator to run the numbers against your own portfolio size, project budgets and team composition. Every assumption is transparent and adjustable.<\/p>\n<h2><span style=\"font-size: 12pt;\">Measuring your costs<\/span><\/h2>\n<p>Having identified the nine hidden cost categories, the next step is applying them to your own organisation. For infrastructure operators this is particularly valuable because the numbers become part of the business case for better project management, whether that conversation is with a board, an executive team, a Commerce Commission auditor or elected members.<\/p>\n<h3><span style=\"font-size: 12pt;\">Step 1: Gather historical data<\/span><\/h3>\n<p>You need at least 12 months of data. For infrastructure operators, most of this already exists across your capital programme reporting, your asset management system and your HR platform.<\/p>\n<p>Gather the following:<\/p>\n<ul>\n<li>A complete list of all capital and operational projects including budgets, actual spend and status (completed, in-flight or cancelled).<\/li>\n<li>Project timelines with original estimates versus actual delivery dates, including any Commerce Commission or long-term plan commitments that slipped.<\/li>\n<li>HR data: headcount, fully loaded cost per person and turnover rate for the past year, with particular attention to project managers and engineers.<\/li>\n<li>Average meeting hours per person (calendar analytics will give you this across your project teams).<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">Step 2: Calculate each cost category<\/span><\/h3>\n<p>Use the formulas above or the calculator on our website. It doesn&#8217;t need to be perfectly accurate. A directionally correct number is enough to make the case with a CFO, a GM or a board. In a regulated environment, even a conservative estimate of $90M+ in hidden costs on a $150M portfolio is a conversation-starting number.<\/p>\n<h3><span style=\"font-size: 12pt;\">Step 3: Verify the numbers<\/span><\/h3>\n<p>Share the results with your leadership team. You&#8217;re looking for two things: do the numbers feel right and which cost categories concern them most. In our experience, compliance reporting overhead and staff turnover tend to land hardest with infrastructure leadership. The second question is often more useful than the first.<\/p>\n<h3><span style=\"font-size: 12pt;\">Step 4: Start tracking<\/span><\/h3>\n<p>Set up quarterly reviews to track:<\/p>\n<ul>\n<li>Project success rates: percentage of capital projects delivered on time, on budget and meeting asset management plan commitments.<\/li>\n<li>Average project delay in months and the downstream impact on planned maintenance schedules.<\/li>\n<li>Percentage rework per project, particularly on field delivery where rework has both cost and safety implications.<\/li>\n<li>Turnover rate for programme managers and engineers, where knowledge loss is hardest to recover.<\/li>\n<\/ul>\n<h2><span style=\"font-size: 12pt;\">Prevention strategies that work<\/span><\/h2>\n<p>Throughout this article we&#8217;ve shared tactical fixes for each cost category. For them to stick, they need a strategy that ties everything together. For infrastructure operators, where delivery failures have consequences beyond the project, these four principles matter more than in most sectors.<\/p>\n<h3><span style=\"font-size: 12pt;\">Create a transparent culture<\/span><\/h3>\n<ul>\n<li>Most project failures happen in the dark. In a regulated environment, that darkness has consequences: a Commerce Commission auditor, an elected member or a Treasury official asking questions you can&#8217;t answer quickly is a risk in its own right. The fix is transparency at every level:<\/li>\n<li>Single source of truth: all project and asset data in one place, accessible to everyone who needs it. For infrastructure operators this means capital programme data, maintenance schedules and field delivery information in the same system, not spread across three departments.<\/li>\n<li>Real-time status: anyone involved in a project should be able to answer &#8216;what&#8217;s the status of project X?&#8217; in 30 seconds. Your Commerce Commission disclosures and long-term plan reporting depend on this data being accurate.<\/li>\n<li>Clear ownership: every project has a named owner and every task has a named person responsible for it. In organisations where capital and BAU maintenance compete for the same engineers, clear ownership stops both from falling through the cracks.<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">Make faster decisions<\/span><\/h3>\n<p>Delayed decisions are expensive in any organisation. In infrastructure delivery they can stall field crews, push out regulatory milestones and compound into asset management plan slippage. Create structures that cut the time it takes to make them:<\/p>\n<ul>\n<li>Authority: formally document who can approve what and at what delegated authority. Field teams and programme managers should never be waiting for a decision they could have made themselves with the right authority framework.<\/li>\n<li>Bias to action: make trying things the default rather than drowning in endless analysis.. This is especially true for the tactical fixes in this article. Pick one and implement it this week.<\/li>\n<li>Deadlines: every decision that needs to be made should have a defined deadline, with escalation if it isn&#8217;t made in time. Late decisions are a leading indicator of the kind of project drift that shows up in your next regulatory disclosure.<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">Build a culture of done<\/span><\/h3>\n<p>Infrastructure organisations are often perfectionist by necessity. The asset has to work. The network has to be reliable. The consent conditions have to be met. That&#8217;s right and proper. But perfectionism applied to project management rather than engineering outcomes is where projects go to die:<\/p>\n<ul>\n<li>Define done: what is the minimum viable outcome for each project? A lines company doesn&#8217;t need every piece of documentation to be perfect before energising a new asset. A council doesn&#8217;t need a 200-page report before opening a new facility.<\/li>\n<li>Celebrate completion: finishing an 80% solution is better than not finishing a 100% solution. Programme teams in infrastructure organisations rarely get recognised for delivery. Make it a habit.<\/li>\n<li>Enforce deadlines: we&#8217;ll spend two weeks on this, then move on with what we have. In a regulated environment, a delivered project with minor imperfections is almost always better than a delayed one.<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">Learn from your failures<\/span><\/h3>\n<p>Post-project reviews in infrastructure organisations either don&#8217;t happen, or they focus on what went wrong with the asset rather than what went wrong with the project. Teams capture the engineering lesson. The delivery lesson disappears. Fix this:<\/p>\n<ul>\n<li>Focus on systems and processes, not people. The question is never &#8216;who caused this?&#8217; but &#8216;what in our process allowed this to happen?&#8217;<\/li>\n<li>Create a searchable database of lessons learned and actually use it. The same scope creep patterns, the same contractor handoff failures and the same sponsor disengagement problems repeat across infrastructure organisations because nobody writes them down in a way that informs the next project.<\/li>\n<li>Build lessons from previous projects into your templates and processes. If your capital delivery methodology doesn&#8217;t yet reflect what you learned from your last three delayed projects, it&#8217;s not a living document.<\/li>\n<\/ul>\n<h2><span style=\"font-size: 12pt;\">When to recognise you need a proper PPM platform<\/span><\/h2>\n<p>The prevention strategies in this article work but they have limits and at some point, manual systems create more cost than they save. For infrastructure operators, that tipping point tends to arrive earlier than in other sectors because the complexity is higher: concurrent capital projects, regulatory reporting cycles, BAU maintenance competing for the same resources and field delivery that no spreadsheet can handle.<\/p>\n<p>The tipping point is generally when:<\/p>\n<ul>\n<li>You&#8217;re running more than 10 active capital or operational projects concurrently.<\/li>\n<li>Your capital and maintenance projects share engineers and project managers and nobody has clear visibility of who is working on what.<\/li>\n<li>Leadership are asking for portfolio-level insights you can&#8217;t produce without days of manual work.<\/li>\n<li>Your regulatory or compliance reporting cycle requires weeks of data reconciliation across disconnected systems.<\/li>\n<\/ul>\n<p>These are the signals we&#8217;ve seen across lines companies, councils and government agencies that told us the time was right:<\/p>\n<ul>\n<li>Your programme managers spends more time chasing status updates than solving problems.<\/li>\n<li>\u00a0Your CFO or GM can&#8217;t get a consolidated view of project portfolio performance without waiting days for someone to assemble it.<\/li>\n<li>Your team has to assemble your regulatory or compliance reporting data manually every cycle from multiple disconnected systems.<\/li>\n<li>You have no reliable view of what resources are committed to which projects three months from now.<\/li>\n<li>You&#8217;ve had a project fail because nobody had visibility of the warning signs early enough to intervene.<\/li>\n<\/ul>\n<h2><span style=\"font-size: 12pt;\">What to look for in a PPM tool for infrastructure operators<\/span><\/h2>\n<p>Not every platform is built for the way infrastructure organisations actually work. Things to look for:<\/p>\n<ul>\n<li>Support for multiple delivery methodologies in the same platform: waterfall capital delivery, agile and planned preventative maintenance.<\/li>\n<li>Asset register integration with your project and maintenance data.<\/li>\n<li>Regulatory and compliance reporting: the ability to produce disclosure outputs directly rather than assembling them manually.<\/li>\n<li>Real-time resource visibility across concurrent projects.<\/li>\n<li>NZ-based support that understands your regulatory environment.<\/li>\n<li>Agentic AI for real-time portfolio analysis.<\/li>\n<\/ul>\n<h3><span style=\"font-size: 12pt;\">Red flags:<\/span><\/h3>\n<ul>\n<li>Forces your organisation to fit its processes to the tool rather than the other way around.<\/li>\n<li>Built for software delivery teams and retrofitted for infrastructure.<\/li>\n<li>Support is a helpdesk in another timezone that has never heard of the Commerce Commission, a long-term plan or a price-quality path.<\/li>\n<\/ul>\n<h2><span style=\"font-size: 12pt;\">The PowerCo story<\/span><\/h2>\n<p>PowerCo is New Zealand&#8217;s largest dual utility, electricity and gas networks across much of the North Island. When they first deployed Psoda, 18 users were managing their capital project visibility.<\/p>\n<p>Today 180 people use Psoda across the business. That growth happened because the platform delivered visible, measurable value at each stage. No big-bang rollout, no forced adoption, just consistent results that earned wider adoption organically.<\/p>\n<p>PowerCo&#8217;s Psoda configuration now produces their Commerce Commission information disclosure reports directly from the platform. The data is already there. They&#8217;ve already configured the report format. At disclosure time they download it and submit it.<\/p>\n<h2><span style=\"font-size: 12pt;\">Other large Psoda customers<\/span><\/h2>\n<p>Hamilton City Council uses Psoda to manage their capital project portfolio and deliver transparent reporting to elected members. Massey University uses it to manage project portfolios and resource allocation across a complex multi-site environment.<\/p>\n<p>The organisations are different. The underlying problem, too many projects, not enough visibility, too much time spent on reporting rather than delivery, is always the same.<\/p>\n<h2><span style=\"font-size: 12pt;\">Getting started<\/span><\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal leading-[1.7]\">The nine cost categories we&#8217;ve covered can add up to three to five times your visible budget overruns. For an infrastructure organisation running a $150M annual project portfolio, that&#8217;s tens of millions of dollars your organisation doesn&#8217;t have to spend.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal leading-[1.7]\">The good news is that the prevention strategies work. Although they need discipline and leadership commitment, the investment required is modest compared to most organisational change programmes. Start by measuring your baseline. Next, pick the two or three categories where your exposure is highest and implement the fixes. Finally, track the numbers quarterly and adjust.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal leading-[1.7]\">As a result, within 12 to 18 months you should be seeing measurable improvement in project delivery rates, team morale and the quality of your portfolio reporting.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal leading-[1.7]\">To see what this looks like in practice, <a href=\"https:\/\/www.psoda.com\/global\/schedule-a-demo\/\">book a 30-minute demo<\/a>. We&#8217;ll show you the PowerCo story and what Psoda looks like for an organisation like yours.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Project failures cost infrastructure operators millions annually but the visible budget overruns are just the tip of the iceberg. $4M+ That&#8217;s what a single failing $10M infrastructure project actually costs. The CFO sees a $1M overrun. The real bill is three to five times that. When a project fails, the CFO sees a $10M project <a href=\"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/\" class=\"more-link\">&#8230;<span class=\"screen-reader-text\">  The Real Cost of Project Failure: What Your CFO Doesn&#8217;t See<\/span><\/a><\/p>\n","protected":false},"author":4,"featured_media":26291,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[22],"tags":[],"class_list":["post-26281","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-project-management"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>The Hidden Cost of Project Failure: Calculate Your Lost ROI<\/title>\n<meta name=\"description\" content=\"The true cost of project failure for NZ infrastructure operators. 9 hidden categories and a free calculator | Psoda\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The Hidden Cost of Project Failure: Calculate Your Lost ROI\" \/>\n<meta property=\"og:description\" content=\"The true cost of project failure for NZ infrastructure operators. 9 hidden categories and a free calculator | Psoda\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/\" \/>\n<meta property=\"og:site_name\" content=\"Enterprise portfolio, programme and project management software\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-11T00:28:56+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-11T01:07:34+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.psoda.com\/global\/wp-content\/uploads\/2026\/06\/The-9-hidden-costs-of-project-failure-for-NZ-infrastructure-operators-1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1859\" \/>\n\t<meta property=\"og:image:height\" content=\"921\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Rhona\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Rhona\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"27 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/\"},\"author\":{\"name\":\"Rhona\",\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/#\\\/schema\\\/person\\\/6fb5a9c94059d0ddb4c05ebd3965f81a\"},\"headline\":\"The Real Cost of Project Failure: What Your CFO Doesn&#8217;t See\",\"datePublished\":\"2026-06-11T00:28:56+00:00\",\"dateModified\":\"2026-06-11T01:07:34+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/\"},\"wordCount\":5807,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/The-9-hidden-costs-of-project-failure-for-NZ-infrastructure-operators-1.png\",\"articleSection\":[\"Project management\"],\"inLanguage\":\"en-NZ\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/\",\"url\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/\",\"name\":\"The Hidden Cost of Project Failure: Calculate Your Lost ROI\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/The-9-hidden-costs-of-project-failure-for-NZ-infrastructure-operators-1.png\",\"datePublished\":\"2026-06-11T00:28:56+00:00\",\"dateModified\":\"2026-06-11T01:07:34+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/#\\\/schema\\\/person\\\/6fb5a9c94059d0ddb4c05ebd3965f81a\"},\"description\":\"The true cost of project failure for NZ infrastructure operators. 9 hidden categories and a free calculator | Psoda\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/#breadcrumb\"},\"inLanguage\":\"en-NZ\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-NZ\",\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/The-9-hidden-costs-of-project-failure-for-NZ-infrastructure-operators-1.png\",\"contentUrl\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/The-9-hidden-costs-of-project-failure-for-NZ-infrastructure-operators-1.png\",\"width\":1859,\"height\":921,\"caption\":\"Infographic showing the 9 hidden costs of project failure for NZ infrastructure operators, totalling $93.6M annually across categories including rework, scope creep and staff turnover. Sources include Te Waihanga, Infrastructure NZ and Lawson Williams.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/2026\\\/06\\\/11\\\/hidden-costs-project-failure\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"The Real Cost of Project Failure: What Your CFO Doesn&#8217;t See\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/#website\",\"url\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/\",\"name\":\"Enterprise portfolio, programme and project management software\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-NZ\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.psoda.com\\\/global\\\/#\\\/schema\\\/person\\\/6fb5a9c94059d0ddb4c05ebd3965f81a\",\"name\":\"Rhona\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"The Hidden Cost of Project Failure: Calculate Your Lost ROI","description":"The true cost of project failure for NZ infrastructure operators. 9 hidden categories and a free calculator | Psoda","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/","og_locale":"en_US","og_type":"article","og_title":"The Hidden Cost of Project Failure: Calculate Your Lost ROI","og_description":"The true cost of project failure for NZ infrastructure operators. 9 hidden categories and a free calculator | Psoda","og_url":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/","og_site_name":"Enterprise portfolio, programme and project management software","article_published_time":"2026-06-11T00:28:56+00:00","article_modified_time":"2026-06-11T01:07:34+00:00","og_image":[{"width":1859,"height":921,"url":"https:\/\/www.psoda.com\/global\/wp-content\/uploads\/2026\/06\/The-9-hidden-costs-of-project-failure-for-NZ-infrastructure-operators-1.png","type":"image\/png"}],"author":"Rhona","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Rhona","Est. reading time":"27 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/#article","isPartOf":{"@id":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/"},"author":{"name":"Rhona","@id":"https:\/\/www.psoda.com\/global\/#\/schema\/person\/6fb5a9c94059d0ddb4c05ebd3965f81a"},"headline":"The Real Cost of Project Failure: What Your CFO Doesn&#8217;t See","datePublished":"2026-06-11T00:28:56+00:00","dateModified":"2026-06-11T01:07:34+00:00","mainEntityOfPage":{"@id":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/"},"wordCount":5807,"commentCount":0,"image":{"@id":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/#primaryimage"},"thumbnailUrl":"https:\/\/www.psoda.com\/global\/wp-content\/uploads\/2026\/06\/The-9-hidden-costs-of-project-failure-for-NZ-infrastructure-operators-1.png","articleSection":["Project management"],"inLanguage":"en-NZ","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/","url":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/","name":"The Hidden Cost of Project Failure: Calculate Your Lost ROI","isPartOf":{"@id":"https:\/\/www.psoda.com\/global\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/#primaryimage"},"image":{"@id":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/#primaryimage"},"thumbnailUrl":"https:\/\/www.psoda.com\/global\/wp-content\/uploads\/2026\/06\/The-9-hidden-costs-of-project-failure-for-NZ-infrastructure-operators-1.png","datePublished":"2026-06-11T00:28:56+00:00","dateModified":"2026-06-11T01:07:34+00:00","author":{"@id":"https:\/\/www.psoda.com\/global\/#\/schema\/person\/6fb5a9c94059d0ddb4c05ebd3965f81a"},"description":"The true cost of project failure for NZ infrastructure operators. 9 hidden categories and a free calculator | Psoda","breadcrumb":{"@id":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/#breadcrumb"},"inLanguage":"en-NZ","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/"]}]},{"@type":"ImageObject","inLanguage":"en-NZ","@id":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/#primaryimage","url":"https:\/\/www.psoda.com\/global\/wp-content\/uploads\/2026\/06\/The-9-hidden-costs-of-project-failure-for-NZ-infrastructure-operators-1.png","contentUrl":"https:\/\/www.psoda.com\/global\/wp-content\/uploads\/2026\/06\/The-9-hidden-costs-of-project-failure-for-NZ-infrastructure-operators-1.png","width":1859,"height":921,"caption":"Infographic showing the 9 hidden costs of project failure for NZ infrastructure operators, totalling $93.6M annually across categories including rework, scope creep and staff turnover. Sources include Te Waihanga, Infrastructure NZ and Lawson Williams."},{"@type":"BreadcrumbList","@id":"https:\/\/www.psoda.com\/global\/2026\/06\/11\/hidden-costs-project-failure\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.psoda.com\/global\/"},{"@type":"ListItem","position":2,"name":"The Real Cost of Project Failure: What Your CFO Doesn&#8217;t See"}]},{"@type":"WebSite","@id":"https:\/\/www.psoda.com\/global\/#website","url":"https:\/\/www.psoda.com\/global\/","name":"Enterprise portfolio, programme and project management software","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.psoda.com\/global\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-NZ"},{"@type":"Person","@id":"https:\/\/www.psoda.com\/global\/#\/schema\/person\/6fb5a9c94059d0ddb4c05ebd3965f81a","name":"Rhona"}]}},"_links":{"self":[{"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/posts\/26281","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/comments?post=26281"}],"version-history":[{"count":9,"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/posts\/26281\/revisions"}],"predecessor-version":[{"id":26297,"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/posts\/26281\/revisions\/26297"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/media\/26291"}],"wp:attachment":[{"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/media?parent=26281"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/categories?post=26281"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.psoda.com\/global\/wp-json\/wp\/v2\/tags?post=26281"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}