CRYPTOITDATA

Project management

Why IT projects fail (and how to save them)

Why IT projects fail: scope creep, bad estimates, misaligned stakeholders, unmanaged vendors. What AI changes in 2026 and how to deliver on time and on budget.

Updated: 8 min read

Almost every business owner who has commissioned an IT project — a new ERP, a cloud migration, a complex website, an integration — has lived the same story: it started optimistically, with a budget and a deadline, and ended months later at twice the cost and half the promised functionality. The bad news: you were not unlucky. The statistics are against you. The good news: the causes are known and, mostly, avoidable.

The figures are brutal. A McKinsey analysis carried out with the University of Oxford on more than 5,400 IT projects shows that large projects (initial budget above $15 million) run on average 45% over budget and 7% over time, while delivering 56% less value than predicted. An Oxford study of 1,471 IT projects found an average budget overrun of only 27%, but the average hides the real problem: one in six projects was a "black swan", with an average cost overrun of 200% and a schedule overrun of almost 70%. In other words, "on time and on budget" is never guaranteed, and the big risk lies in the projects that go completely off the rails.

Here is the counterintuitive part: these projects rarely fail for technical reasons. They fail from a lack of process. Let us see where, concretely.

The most common causes of failure

Scope creep — the project that grows out of control

One of the most widespread problems is scope creep: scope poorly defined at the start that then grows uncontrolled. In the Project Management Institute (PMI) 2018 survey, 52% of projects completed in the previous 12 months experienced scope creep or uncontrolled changes to scope. Every "let us just add this too" looks small in isolation. Summed up without a change-control process — where each change is assessed for time and budget impact before being accepted — they turn a 3-month project into an 8-month one. Change is not the problem; ungoverned change is.

Unrealistic estimates from the start

In the same 2018 PMI survey, inaccurate cost estimates were cited among the primary causes of failure for 28% of failed projects. When the budget is based on an optimistic guess, every surprise — an unforeseen dependency, a late vendor, a misunderstood requirement — becomes an overrun. A project that starts from a poor estimate cannot end well: the problem is baked in from day one.

Misaligned stakeholders and poor communication

Many projects die because the people who decide only learn about problems at go-live. Without structured reporting, an engaged sponsor and a clear communication plan, every department has its own picture of "what the project should deliver" — and those pictures collide exactly when reconciling them is most expensive. In the PMI survey, poor communication (29%) and inadequate sponsor support (26%) appear among the primary causes of failed projects.

External vendors with no oversight

When you work with external suppliers — a software house, an integrator, a consultant — the quality of deliverables drops quickly if there is no one on your side who understands what to verify. Professional vendor management means clear SLAs, defined deliverables, structured escalations and a real technical counterpart. Without it, you pay for promises, not results.

What changed in 2026: AI in project management

The year 2026 brought a real shift in how projects are run. A large part of a project manager's time goes on administrative tasks: reports, status updates, repetitive planning. This is exactly where AI steps in: modern tools generate reports, automatically detect delays and deviations from the baseline, and free the PM's time for what matters — decisions and communication. The dominant trend is "agentic AI": agents that do not just suggest a plan, but identify resource bottlenecks and flag early when the project deviates.

There is also data linking AI to results, although older: in a 2019 PMI report, organisations applying all five AI adoption principles studied ("AI Innovators") reported delivering 61% of projects on time, versus 47% for those applying none. And PMI updated the PMP exam in July 2026: the new version adds AI, alongside sustainability and stakeholder engagement, in project-based scenarios.

A caveat, though: AI accelerates execution, it does not replace it. An AI agent can generate a flawless status report, but it cannot negotiate with a reluctant stakeholder, decide what scope to cut when the budget is blown, or carry accountability for delivery. AI is a tool that amplifies a good process — and amplifies chaos if the process is missing.

How to bring a project in on time and budget

The difference between projects that succeed and those that fail is not the budget or the technology — it is process discipline. Here is what works, concretely:

  1. 1Start with a sponsor-signed charter: a clear business case, measurable success criteria, a realistic budget and timeline. If you cannot articulate why you are doing the project, stop before you spend.
  2. 2Define a RACI from the start — who is responsible, who decides, who is consulted, who is informed. Half the confusion later disappears here.
  3. 3Enforce a change-control process: any scope change is assessed for time and budget impact before being accepted. That is how you stop scope creep.
  4. 4Report weekly with a RAG status (green / amber / red): where you are on timeline and budget, which risks are active, which decisions are needed. No surprises at go-live.
  5. 5Keep a living risk register — identify proactively, escalate in a structured way, decide on data, not gut feeling.
  6. 6For vendors: SLAs, defined deliverables, real quality verification. You pay for results, not promises.
  7. 7Use AI for the administrative side — reports, tracking, deviation detection — so time is left for the decisions that actually matter.

All of this is exactly what we deliver in a project management engagement: a structured kickoff, charter, RACI, weekly RAG reporting, vendor management and leadership through to go-live and closure. We use hybrid methodologies — waterfall for fixed-scope projects, agile for exploratory ones — the choice depends on the nature of the project, not on fashion.

IT projects do not fail because of the technology. They fail because no one held the wheel — and no one noticed in time that they were drifting off the road.

When to bring in an external PM

Not every project needs a dedicated project manager. But there are moments when not having one costs far more than the fee: a complex migration (ERP, CRM, infrastructure) with cutover and rollback; coordinating several vendors in parallel; a project already derailed that needs recovery; or simply a technically strong internal team without the capacity to run a big project alongside the day job. If you recognise one of these scenarios, let us talk for 30 minutes — I will tell you honestly whether you need a PM or not.

Conclusion

The data shows that budget and schedule overruns are common in IT projects, and some projects go completely off the rails. But the causes are not technical mysteries — they are scope creep, bad estimates, misaligned stakeholders and unmanaged vendors. All of them are solved with process, not luck. The AI of 2026 makes execution faster, but it does not replace discipline. If you have an important project on the table and want to keep it from becoming the next horror story, let us talk — I will show you where the risks are before they become problems.

Sources

Frequently asked questions

Why do most IT projects fail?+

Rarely for technical reasons. The dominant causes are scope creep (poorly defined scope that grows uncontrolled), unrealistic estimates from the start, misaligned stakeholders and unsupervised vendors. All are process problems, not technology problems — which is why they are avoidable.

What is scope creep and how do I stop it?+

Scope creep is the uncontrolled growth of requirements after the project has started. You stop it with a change-control process: every change is assessed for time and budget impact before being accepted. Change is not the problem; ungoverned change is.

Does AI replace the project manager in 2026?+

No. AI automates the administrative side — reports, tracking, deviation detection — and frees the PM's time, which otherwise is consumed by repetitive tasks. But decisions, negotiating with stakeholders and accountability for delivery remain human. AI amplifies a good process; it does not create one.

Do I need an external project manager for a small project?+

Not necessarily. An external PM is justified for complex migrations, coordinating multiple vendors, already-derailed projects, or when the internal team lacks the capacity to run a big project alongside daily operations. For small projects, a minimal disciplined process is often enough.

Have a concrete question?

30 minutes, free. We discuss exactly your situation.

Book a consultation