Stabilizing Escalated IT Projects: The Path to Turnaround

When an IT project overruns time and budget, the first reaction is usually the same: more pressure, more overtime, more status meetings. The numbers show why that is rarely enough. According to research by McKinsey and the University of Oxford covering more than 5,400 IT projects, large IT initiatives run 45 percent over budget and 7 percent over schedule on average, while delivering 56 percent less value than planned; 17 percent spiral so far out of control that they can threaten the company itself. Escalation is not an exception but a calculable risk — what matters is how early and honestly it is addressed.

Stabilization starts with transparency

Four steps bring an escalated project back under control:

Honest assessment: Scope, plan and actual status are compared without embellishment. What has actually been accepted — as opposed to “90 percent done”? Only a reliable picture of the situation makes further decisions possible.
Re-baseline instead of perseverance slogans: A plan that is demonstrably unachievable steers nothing — it merely keeps people busy. A new, realistic baseline with clear milestones is not capitulation but the precondition for accountability. According to McKinsey, every additional project year increases cost overruns by 15 percent: postponing gets expensive.
A steering committee able to decide: The board needs decision papers with options and consequences instead of slide battles. If every meeting ends with “we will keep monitoring”, governance is part of the problem — in an escalated project, deferral is the most expensive decision.
Manage vendors, refocus the team: Contracts, dependencies and open items with external partners are reordered and tied to the new baseline. Inside the team: reduce parallel work, set few clear priorities, shield people from interruptions.

The price of poor project governance

According to PMI’s Pulse of the Profession 2018, 9.9 percent of every dollar invested is wasted through poor project performance; organizations completing 80 percent or more of their projects on time, on budget and in line with business intent reach a 92 percent success rate — versus 32 percent for underperformers. And the downside of a single project is real: in 2011, Bent Flyvbjerg and Alexander Budzier documented in Harvard Business Review an IT project budgeted at under 5 million US dollars that ended in a 192.5 million US dollar write-off. Whoever sugarcoats an escalated project is not negotiating about weeks, but about orders of magnitude.

What project leaders should do now

The warning signs usually appear early: milestones slip repeatedly, the forecast becomes a matter of negotiation, the team stops reporting risks. At that point, an independent assessment by someone without history in the project pays off. Then: treat the re-baseline as a deliberate leadership decision, keep the steering committee small and able to decide, and reward transparency instead of punishing it — those who sanction bad news stop receiving any. The metric that matters is not the completion percentage on the status slide, but the number of weeks since the last honest assessment.