← Insights

IT project turnaround framework: diagnose the real breakdown

IT team analyzing diagnostic metrics and project workflows on digital screens during a project turnaround review

A slipping schedule is a signal, not a diagnosis

An IT project turnaround framework investigates a missed milestone without assuming the delivery team caused it. Project management should pursue the client’s business goals in an objectively optimal time frame rather than minimise slippage against an initial schedule that is most often unrealistic.

The initial enthusiasm of signing a new contract often obscures the reality of what the work actually requires. Hard work can coexist with unresolved commitments. Delays are generated by ambiguous scope, divergent interpretations of scope between client and supplier, analysts lacking sufficient domain knowledge, and too many inexperienced team members.

Small, unrecorded changes and delays at the task level accumulate over a month, two or a quarter into delays that are significant from the client’s perspective and hard to explain. Developers and architects are not project managers; if they lack a clear understanding of the project’s context and high-level business goals, their daily priorities will naturally diverge from the management’s timeline.

What my project stories reveal beneath the delay

The warning sign and my initial interpretation

In the project that had already been running for two years when I took it over, the client escalated delays while refusing to acknowledge scope extensions and changed agreements. The team struggled to keep up with shifting expectations. My initial interpretation focused on the immediate operational friction rather than the disagreement over scope.

We worked to prepare a recovery plan for the upcoming steering committee. The customer pressed us to extend the schedule by one year, then stopped the project and terminated the contract at the steering committee; the official reason they gave was an expected one-year delay.

The delay was the weaponised symptom. The underlying cause was a refusal to align the contractual baseline with the evolving scope. The whole situation was arranged, most likely because the client had run out of budget for the initiative. After cancelling the contract, the client failed to prove the vendor’s guilt in court. A CEO reviewing such a situation should ask whether the delay stems from delivery capability or an unsupported scope expansion that no one has authority to approve.

The underlying problem and the management response

In another case, a project was delivered exactly as agreed, but the client refused to pay because they misunderstood how to configure and use the solution. Pushing the team harder would not have fixed that. A turnaround has to address the acceptance conditions and usage gaps behind such a dispute.

A programme sponsor should check whether delivery promises rely on external dependencies or subjective approvals that the vendor cannot control. We should verify what evidence is required for acceptance and who holds the authority to confirm it.

An IT project turnaround framework built around the 10 Rules Diagnostic

What the 10 Rules Diagnostic examines

The 10 Rules Diagnostic is my method for diagnosing projects in trouble: examining them against the ten rules described in my book, 10 Rules for Impossible Projects. It identifies where those rules are not being followed and what needs closer investigation. It is the basis of my IT project turnaround framework.

Two relevant rules direct attention beyond the schedule:

  • Rule 1 states that we must get involved in the contract negotiations. This includes the future delivery team and departments whose work will be needed, not just those negotiating the sale.
  • Rule 2 requires us to define what it means to deliver the project. Contractual scope and the client’s actual business needs can diverge; client and supplier definitions of success can also evolve in different directions. The longer a project lasts, the more the definition of delivery deviates from the initial contract.

When a project struggles, we check if these rules were compromised. We investigate whether accountability for a deliverable is assigned to one person rather than a group, because group accountability leads to chaos when difficulties arise. We also examine the management environment. Decision delays caused by fear, avoiding responsibility, complex processes, bureaucracy, decision-making paralysis, or lack of communication are harmful to both the client and the vendor.

How project evidence points to a management decision

Project evidence should point to a specific management decision rather than a generic schedule revision. In the projects above, a disputed scope and a solution the client could not use pointed to scope decisions and acceptance conditions, not to the delivery team’s effort.

Rule 7 instructs us to consciously manage information flow. Telling the client everything without a deliberate strategy can lead to immediate contract termination, so communication must be meticulously planned. Rule 6 reminds us to exert pressure and use our position to force necessary decisions. When informal talks fail, we must switch to formal communication, explicitly detailing the consequences and financial losses caused by the client’s avoidance of making decisions.

Identifying a rule that is not being followed focuses a sponsor’s questions on a specific decision. We use resource scarcity as a way to distinguish phases when management decisions can be expected, so teams can prepare for them in advance.

The following checks help gather evidence about these management gaps. They are not a separate formal diagnostic procedure or scoring model.

What a CEO or programme sponsor can check this week

Compare the original promise with the current agreed scope

A sponsor should compare the original commitment, the current agreed scope, and the plan now being used to deliver it. We look for additions, unresolved assumptions, or dependencies that have not been reflected in an explicit decision about timing or resources. We ask who accepted each material change and whether those responsible for delivery are working to the same agreement.

This is a document comparison, not proof in advance that scope change caused the delay. In one project that delivered one of three planned phases after two years, barely 30% of the planned scope was enough to meet virtually all of the client’s expectations.

The aim is to reconcile the current plan with the actual business requirement.

Ask what evidence supports the next milestone

Leaders should inspect the work that supports the next milestone rather than relying on a reassuring status label.

We ask to see the relevant acceptance criteria, demonstrable work, unresolved dependencies, and remaining decisions. We should ask who confirms acceptance, what evidence is required, and how objections are handled. Status information and reporting must be a tool for the teams to manage their work deliberately, rather than just slide engineering for the management. Each piece of information must be described by four dimensions: who, what, why, and when.

Where the evidence is incomplete, we ask which technical or operational uncertainty needs resolving before another delivery commitment. The point is to make that uncertainty explicit rather than treat an unsupported deadline as a reliable commitment.

Establish who can make a binding decision

The next step is to identify who can settle an unresolved decision affecting delivery. We check whether the named owner has actual authority over the relevant scope, acceptance condition, or competing priority. We should distinguish consultation and meeting attendance from the authority to make a binding decision.

We clarify the specific decision needed, its accountable owner, and how its consequences will be reflected in the revised plan.

Steering committees must be utilised to secure these binding decisions from top executives. Instead of presenting a general status update, the project manager should devote the majority of the meeting to discussing critical impediments and securing approval for the proposed solutions.

Choose the first correction from the evidence

We select an initial corrective decision that addresses a supported cause and falls within the sponsor’s authority, rather than automatically demanding a new date. Steering committees should be used to solve problems, where the project manager brings proposals and uses the time to secure approval for the option considered most beneficial. The focus must shift from finding a guilty party to pragmatically seeking solutions.

Evidence Observed Initial Corrective Decision Follow-up Check
Scope evidence shows mismatch Reconcile conflicting commitments Verify plan reflects agreement
Decision is blocked Assign binding authority Verify decision in plan
Unsubstantiated progress claims Require demonstrable acceptance evidence Verify against acceptance criteria
  1. If scope evidence shows a mismatch, reconcile the conflicting commitments. Then check that the delivery plan reflects the agreement.
  2. If a decision is blocked, clarify and assign binding authority. Then check that the decision is made and its consequences appear in the plan.
  3. If progress claims cannot be substantiated, require demonstrable acceptance evidence. Then verify the result against the agreed acceptance criteria.

These are practical follow-up checks, not documented project results. Where explanations remain uncertain, we choose a focused investigation before imposing a corrective action.

Find the breakdown before resetting the promise

The signals to examine are commitments that no longer match the agreed scope, milestone claims without supporting evidence, and unresolved decisions without clear authority. Another revised date does not itself address these problems.

In one fixed-price project, the client’s termination attempt was intended to shake the supplier into presenting a reliable action plan. The client suspected resource shortages but needed the vendor to initiate an honest dialogue about the problems. After open discussion, the client accepted the recovery plan and actively participated in it. We switched to full transparency, reporting hours and tasks in detail despite the fixed-price contract, which ultimately removed the pressure from the team and allowed them to openly discuss their concerns.

If your project is struggling, request a strategy session or a Project Rescue Review through the contact form.