Project Management

Why 70% of IT Projects Fail, and How to Avoid It

November 18, 2026 · 11 min read

Why 70% of IT Projects Fail, and How to Avoid It

"70% of IT projects fail" is one of the most repeated statistics in technology. It appears in boardroom presentations, vendor pitches and project management courses. But where does it come from, is it true and, most importantly, what can you do to make sure your project ends up among the successful ones?

In this guide, we look honestly at the research behind the number, explain why IT projects fail, list the warning signs that a project is in trouble and share practical steps to prevent failure, or to rescue a project that is already slipping.

Is It Really 70%? Where the Number Comes From

There is no single official failure rate for IT projects. The "70%" figure is a shorthand that draws on several different studies, which measure different things:

SourceWhat It Found
Boston Consulting Group (2020)70% of digital transformations fall short of their objectives
Standish Group CHAOS data (2011–2015)Only 29% of software projects were fully successful; the rest were challenged or failed
McKinsey and the University of OxfordLarge IT projects run 45% over budget and deliver 56% less value than predicted
PMI Pulse of the Profession (2018)52% of projects experienced scope creep

Here is what each study tells us:

  • BCG: research by Boston Consulting Group found that 70% of digital transformations fall short of their objectives. It also found that getting six critical factors right can flip the odds of success from 30% to 80%.
  • Standish Group: the CHAOS reports define success strictly, as on time, on budget and with a satisfactory result. As Cprime's summary of more than 10,000 projects from 2011 to 2015 shows, only 29% met that bar. Most of the remainder were "challenged" (late, over budget or missing features) rather than cancelled outright.
  • McKinsey: research by McKinsey and the University of Oxford found that large IT projects run 45% over budget and 7% over time on average, while delivering 56% less value than predicted. Around 17% went so badly that they could threaten the very existence of the company.
  • PMI: the Project Management Institute reported that 52% of projects experienced scope creep in 2018, up from 43% five years earlier.

So, is it really 70%? It depends on how you define failure. A minority of projects are cancelled outright, but a much larger share are late, over budget or deliver less than promised. The exact number matters less than the pattern: most IT projects struggle for the same predictable reasons, and most of those reasons are preventable.

What Does "Failure" Actually Mean?

An IT project can fail in several ways:

  • Cancelled: the project is abandoned before delivery, and the investment is lost.
  • Challenged: the software is delivered, but late, over budget or with fewer features than planned.
  • Delivered but unused: the software works, but users do not adopt it or it does not deliver the expected business value.

The third type is the most overlooked. A project can be on time and on budget and still fail if it solves the wrong problem.

Why IT Projects Fail: The 12 Most Common Reasons

1. Unclear goals and success criteria

If nobody can say what success looks like, nobody can deliver it. Projects launched with vague goals such as "modernise our systems" drift, because every stakeholder has a different picture of the outcome.

How to avoid it: define measurable goals before you start, such as "reduce order processing time from three days to one", and tie every major feature to one of them.

2. Poor or incomplete requirements

When requirements are vague, developers fill the gaps with assumptions, and the client discovers the mismatch at the end.

How to avoid it: invest in a discovery phase and a clear software requirements document with acceptance criteria and an explicit out-of-scope list.

3. Scope creep

Small additions accumulate until the project is far bigger than the one that was budgeted and scheduled.

How to avoid it: use a formal change process and assess the time and cost impact of every new request. Our guide on scope creep explains how.

4. Unrealistic estimates and deadlines

Deadlines are often set before anyone understands the work, and estimates are squeezed to fit them. People also consistently underestimate how long tasks will take, a bias psychologists call the planning fallacy.

How to avoid it: estimate in ranges, include testing and project management time, and add contingency. See our guide to estimating software development time.

5. Weak executive sponsorship

Without a senior sponsor who champions the project, it struggles to get decisions, resources and priority when it competes with day-to-day work.

How to avoid it: name an accountable sponsor with budget authority, and schedule regular steering reviews.

6. Lack of user and stakeholder involvement

Software designed without real users often misses how work is actually done.

How to avoid it: involve users from discovery onwards, test prototypes with them and hold regular demos.

7. Poor communication

Misunderstandings between business and technical teams, or between client and vendor, cause rework and frustration. Problems that are hidden early become crises later.

How to avoid it: agree communication channels, meeting rhythms and reporting formats at the start, and create a culture where bad news travels fast.

8. The wrong team or missing skills

A team without experience in the technology, the business domain or projects of a similar size will learn on your budget.

How to avoid it: check relevant experience and references, and fill skill gaps early, whether in-house or with a partner. See our comparison of outsourcing vs in-house development.

9. The wrong technology choices

Choosing a tech stack because it is fashionable, rather than because it fits the problem and the team, leads to slow progress and costly rewrites.

How to avoid it: choose proven technology that suits your requirements and your team's skills. Our guide on how to choose a tech stack walks through the decision.

10. Big-bang delivery

Projects that deliver everything at once, after months or years, find problems too late. The bigger the release, the bigger the risk.

How to avoid it: deliver in small increments, starting with a minimum viable product. Standish Group data summarised by Info-Tech Research Group found that agile projects were almost four times more likely to succeed than waterfall projects. Our comparison of agile vs waterfall explains why.

11. Cutting corners on quality and testing

When schedules slip, testing is often the first thing to be squeezed. The result is bugs, security holes and technical debt. A CISQ report sponsored by Synopsys estimated that poor software quality cost the US economy $2.41 trillion in 2022.

How to avoid it: build testing into every sprint, automate where possible and never skip user acceptance testing.

12. Ignoring change management and adoption

New systems change how people work. Without training, communication and support, users resist the new software or find ways to work around it.

How to avoid it: plan training, documentation, launch communications and post-launch support as part of the project, not as an afterthought.

Warning Signs Your IT Project Is in Trouble

Most failing projects show warning signs long before they are officially in trouble. Watch for these:

  • Milestones keep slipping, and tasks stay "nearly done" for weeks
  • No working software has been shown after several months
  • Requirements are still changing in the final phase
  • Stakeholders stop attending reviews or cannot agree on priorities
  • The team is working long hours of overtime to keep up
  • New bugs are reported faster than they are fixed
  • The budget is being spent faster than progress is being made
  • Status reports are always "green" despite visible problems

A Simple Framework to Prevent IT Project Failure

StageWhat to Do
Before the projectClear goals, an accountable sponsor, a discovery phase, prioritised requirements and a realistic budget with contingency
During the projectShort iterations, regular demos, change control, a risk log, honest reporting and continuous testing
At launchUser acceptance testing, training, a phased rollout and a support plan
After launchMeasure results against the goals, gather feedback and plan maintenance and improvements

Budget planning is a big part of this. Our guides on how to budget an IT project and the hidden costs of software development help you avoid the most common financial surprises.

Keep Projects Small

One of the most consistent findings in project research is that smaller projects succeed more often than large ones. Large projects have more requirements, more stakeholders, more integrations and more time for things to change. McKinsey's research found that every additional year a project runs increases cost overruns by 15%. If you have a big vision, break it into smaller releases, each delivering real value on its own. Launching an MVP first is often the safest way to start.

How to Rescue a Failing IT Project

If your project is already in trouble, it is not too late. A structured recovery often saves most of the investment:

  1. Pause and assess: stop adding new work and get an honest view of what is finished, what is half done and what remains.
  2. Reconfirm the goals: agree with the sponsor which outcomes still matter most.
  3. Cut the scope to the essentials: identify the smallest release that delivers real value, and move everything else to a later phase.
  4. Re-estimate and re-plan: build a new, realistic plan with ranges and contingency.
  5. Fix the team and the process: fill skill gaps, clarify roles and introduce short iterations with regular demos.
  6. Communicate openly: share the new plan and progress with all stakeholders to rebuild trust.

Sometimes an independent review of the code and the project is the fastest way to see what can be saved.

Frequently Asked Questions

What percentage of IT projects fail?

It depends on the definition. Standish Group data from 2011 to 2015 found that only 29% of software projects were fully successful, and BCG found that 70% of digital transformations fall short of their objectives. Outright cancellations are less common than projects that are late, over budget or deliver less than planned.

What is the number one reason IT projects fail?

There is rarely a single cause, but unclear goals and poor requirements sit at the root of many failures, because they lead to scope creep, bad estimates and building the wrong thing.

Do agile projects fail less often?

Research suggests they do. Standish Group CHAOS data from 2011 to 2015 found success rates of 39% for agile projects compared with 11% for waterfall projects, although project size and team practices also play a big role.

How can small businesses avoid IT project failure?

Start small with a clearly defined MVP, choose an experienced development partner, agree requirements and acceptance criteria in writing, keep a contingency budget and review working software every one to two weeks.

What is the difference between a failed and a challenged project?

A failed project is cancelled or never used. A challenged project is delivered but is late, over budget or missing features. Many statistics combine the two, which is why failure rates vary so much between studies.

Who is responsible when an IT project fails?

Usually several parties share responsibility: sponsors who set unrealistic expectations, teams that hide problems and vendors that overpromise. The best prevention is shared ownership, with clear roles, honest reporting and early escalation of risks.

Conclusion

Understanding why IT projects fail is the first step to making sure yours succeeds. Whether the true figure is 70% or somewhat lower, the causes are well known: unclear goals, poor requirements, scope creep, unrealistic estimates, weak sponsorship, big-bang delivery and cutting corners on quality. Each one has a practical fix. Define success clearly, deliver in small increments, manage change deliberately and keep communication honest, and you shift the odds firmly in your favour. Working with a distributed team? Our guide on how to manage a remote development team covers the extra risks to watch.

Worried about your next IT project, or one that is already off track? Our team helps businesses plan projects that succeed and rescue those that have stalled. Book a free consultation today.