Project Success Rates by Industry: How IT, Construction, Healthcare, and Government Compare
Project success is often discussed as though every industry uses the same definition and the same scorecard. It does not. A software rollout can go live on schedule yet fail to change how employees work. A hospital system can be technically delivered but disrupt clinical workflows. A construction project can finish late and still provide a durable asset that meets its business case. A government program may deliver its contracted outputs while missing the public outcome that justified the investment.
The strongest available cross-industry comparison in this article comes from the Project Management Institute's 2024 Maximizing Project Success research. Rather than measuring only whether projects finished on time, within budget, and within scope, PMI asked respondents whether their most recently completed project delivered value worth the effort and expense. That distinction changes how the numbers should be interpreted.
What the project success rates actually measure
PMI's 2025 study drew on more than 5,800 project professionals, key stakeholders, and knowledge workers across global industries. It continued PMI's value-based approach to success: a project succeeds when it delivers value that justifies the effort and expense involved, as perceived by stakeholders. The report also distinguishes projects that fully succeed from those that partially deliver expected results and those that fail outright.
This is a perception-based measure of value, not a universal audit of delivery performance. It is useful for comparing how respondents viewed projects across sectors, but it does not prove that every project in an industry has the same probability of success. Industry-level figures should be treated as survey benchmarks, not as forecasts for an individual project.
PMI's 2025 research reported that about 50% of projects fully succeeded, 37% partially delivered expected results, and 13% failed outright. These global figures are a useful reference point, but they should not be confused with the percentage of projects completed on time and on budget. The latter is a narrower delivery measure.
IT, construction, healthcare, and government compared
The 2025 comparison shows a different pattern from a simple stereotype that IT projects are the least successful. IT has the highest success share among these four sectors, healthcare and construction are close behind, and government has the lowest success share and the highest outright-failure share.
Industry | Rated successful | Mixed result | Rated failure |
IT | 53% | 37% | 10% |
Healthcare | 52% | 38% | 11% |
Construction | 51% | 39% | 10% |
Government | 37% | 38% | 25% |
Source: Project Management Institute, Step Up: Redefining the Path to Project Success With M.O.R.E. (2025). Percentages are rounded and reflect the report's industry-level survey results.
Three observations matter. First, IT leads this comparison at 53% successful, although that still leaves 47% of projects short of full success. Second, healthcare and construction are nearly level at 52% and 51%, respectively, while their mixed and failure shares differ. Third, government has a 25% outright-failure share, more than double the IT figure. These are patterns to investigate, not proof that industry labels alone cause outcomes.
These percentages should not be read as a league table for every project. A small software implementation, a hospital-wide clinical transformation, a residential building, and a national transport program differ in duration, uncertainty, regulation, and the number of stakeholders whose definition of value matters.
Why IT projects face a different success test
IT projects often combine technical delivery with organizational change. A system can meet its specification and pass testing yet deliver little value if employees avoid it, data migration is incomplete, integrations are unreliable, or operating processes remain unchanged. Benefits therefore depend on adoption and the redesign of work, not only on software quality.
Requirements also evolve during implementation. Product teams may learn more about user needs, security threats can change, and legacy systems may contain dependencies that were not documented at the outset. Treating every scope change as failure can discourage sensible adaptation; accepting every change without reforecasting can conceal cost and schedule risk.
IT leaders should define success at three levels: delivery, adoption, and business outcomes. Delivery measures include release readiness, defects, reliability, and forecast variance. Adoption measures include active use, task completion, support demand, and workflow compliance. Outcome measures might include reduced processing time, lower operating cost, improved service availability, or fewer errors. Baselines and benefit owners should be agreed before the project starts.
The comparison also depends on project type. PMI's research separates industry from project type, and the two classifications should not be treated as interchangeable. An IT organization may manage software product development, infrastructure upgrades, and business-process change, each with different risk profiles. Before benchmarking, compare similar project types and sizes rather than assuming the sector average predicts an individual initiative.
Why construction and healthcare compare relatively well
Construction projects frequently produce tangible outputs with defined acceptance criteria: a building, facility, road, or other physical asset. Design specifications, inspections, contractual milestones, and quality standards can make completion easier to verify than benefits from a broad organizational transformation. PMI's research also highlights intended benefits, customer satisfaction, and quality as relevant performance themes for construction.
That does not make construction low-risk. Ground conditions, design changes, labor shortages, material prices, permitting, contractor interfaces, and weather can all affect delivery. A project can meet its completion date while exceeding its approved cost, or finish within budget but leave the owner with an asset that is difficult to operate. Effective control requires a live risk register, disciplined change control, realistic contingency, and clear accountability across the client, designer, main contractor, and subcontractors.
Healthcare shares some characteristics with construction in that outcomes can be defined around a specific service or facility, but the implementation environment is more operationally sensitive. A new hospital wing, electronic health record, diagnostic service, or clinical pathway can affect patient safety, staff workload, privacy, and service continuity. A technically successful launch is not sufficient if clinicians cannot use the system safely or patients experience delays.
Healthcare projects should therefore track both implementation milestones and clinical or service outcomes. Measures may include safety incidents, waiting times, staff adoption, data quality, service availability, patient experience, and compliance. Baselines must be chosen carefully, because changes in patient mix, staffing, demand, or clinical practice can affect results independently of the project.
For both sectors, the higher PMI scores should be interpreted as a pattern in perceived project value, not evidence that physical deliverables guarantee success. Clearer outputs may help stakeholders agree on what was delivered, but benefits still depend on quality, usability, operational readiness, and lifecycle cost.
Why government projects need a broader view of delivery
Government projects often operate across multiple approval layers, procurement rules, budget cycles, political priorities, and public accountability requirements. These controls serve legitimate purposes, including fairness, transparency, and stewardship of public money. However, they can make decisions slower and make it difficult to change direction when assumptions no longer hold.
Public projects also have a more complex stakeholder landscape. A project sponsor may prioritize cost and schedule, service users may prioritize access and quality, elected officials may emphasize policy commitments, and auditors may focus on compliance. A program can satisfy its contract and still fail to deliver the intended public benefit. Conversely, a project that changes scope responsibly to meet a new public need may be valuable even if its original plan changes.
The response should not be to weaken controls. It should be to connect controls to outcomes. Establish a named senior responsible owner, a clear business case, measurable public benefits, and explicit decision rights. Use stage gates to test whether the case remains valid, not merely to confirm that paperwork is complete. Escalate unresolved cross-agency dependencies early, and report forecast cost and benefits together rather than treating expenditure as the only reliable metric.
Government's lower result should prompt examination of governance, procurement, decision rights, and outcome measurement rather than an assumption that public-sector work is destined to fail. Public accountability and procurement controls serve legitimate purposes; the management challenge is to connect them to timely decisions and measurable public benefits.
How to use industry benchmarks without misleading yourself
Benchmarks are most useful when they improve decisions inside a portfolio. They are least useful when a single percentage is presented as a prediction for a specific project. A project executive should compare like with like: similar project type, scale, complexity, delivery model, geography, and definition of success.
A practical approach is to establish a balanced scorecard before authorization. Define the delivery baseline, expected outcomes, benefit owners, and the evidence that will demonstrate value. Record leading indicators, such as unresolved high risks, resource gaps, test failures, or low user participation, alongside lagging indicators such as cost variance, schedule variance, and realized benefits.
At each major decision point, ask whether the project is still worth the effort and expense. If the answer is no, the correct response may be recovery, a controlled reduction in scope, a redesigned business case, or cancellation. Continuing simply because substantial money has already been spent is not a success strategy.
Finally, review outcomes after handover. Benefits may take months or years to emerge, particularly in IT and healthcare transformation. A project closeout report should not mark benefits as achieved merely because a system was launched or an asset was handed over. Assign operational owners, set measurement dates, and compare actual performance with the original baseline.
Conclusion: Project Success Rates by Industry: How IT, Construction, Healthcare, and Government Compare
PMI's 2025 results show that perceived project success varies by industry: IT has the highest full-success share among the four sectors compared, healthcare and construction follow closely, and government has the lowest success share and the highest outright-failure share. These are comparative signals, not universal probabilities or proof that one sector's projects are inherently better managed.
The central lesson is to measure more than completion. Delivery discipline matters, but lasting success depends on whether the outputs are adopted and produce value worth the investment. Organizations should use industry data as context, then set project-specific measures, monitor risks and outcomes, and act when evidence shows the business case is weakening.
Over the next two years, pressure to demonstrate measurable benefits is likely to increase as organizations scrutinize technology spending, infrastructure investment, and public budgets. That outlook is directional rather than certain. Projects that connect governance and delivery controls to clearly owned outcomes will be better positioned to show whether they have succeeded.
FAQs
Are project success rates directly comparable across industries?
Not perfectly. Definitions, project sizes, survey populations, and evaluation periods vary. PMI's 2024 figures use a value-based perception measure, so compare them within that framework and avoid treating them as audited probabilities for an individual project.
Why does government score lower than construction or healthcare?
The survey shows lower perceived success, but it does not prove a single cause. Complex procurement, multiple stakeholders, policy changes, and slower decision rights can contribute to delivery difficulty, while strong governance and outcome-based oversight can mitigate these risks.
Should organizations measure success beyond time, cost, and scope?
Yes. Retain schedule, budget, scope, quality, and risk measures, but add adoption, customer or citizen outcomes, and realized benefits. Agree on baselines and owners before work begins, then review results after handover as well as at closure.
