How do you recover a project that is already off track?

What is happening

The project is late, the reporting has lost credibility, and the team is working hard. That combination is the signature of a system problem, not an effort problem. The work around the work — decisions, dependencies, ownership, and scope control — has stopped functioning.

Why it happens

• Scope changed incrementally without a corresponding change to time, budget, or expectations.
• Decisions were escalated but never resolved, and the team kept moving on assumptions.
• Dependencies on other teams were tracked as risks rather than managed as commitments.
• Status reporting rewarded optimism, so problems surfaced late.
• The sponsor changed, or several sponsors want different outcomes.

What to do first

1. Establish the baseline

Independently confirm what is complete — not what is reported as complete. Complete means accepted against a definition someone agreed to. Everything else is in progress.

2. Build the decision log

List every open decision with an owner and a due date. In most recovery situations this list, not the task plan, is the critical path.

3. Re-scope to a defensible minimum

Define the smallest outcome that delivers real business value, and move everything else to a later phase explicitly and in writing.

4. Restore a working cadence

• A short weekly session that closes decisions rather than reviews status.
• One reporting format that the sponsor, the team, and any vendor all work from.
• A named accountable owner with authority to say no to scope.
• Explicit dependency commitments from other teams, with dates and owners.

What not to do

• Do not add people before you understand whether the constraint is capacity or decisions.
• Do not replan first. A new date built on unverified progress fails faster.
• Do not run a blame review at the start — it stops people telling you the truth you need.
• Do not keep reporting green to protect confidence. Recovery depends on an honest reset.

Questions to ask

• What is genuinely accepted as complete, and by whom?
• Which decisions are open, and who owns each?
• What has changed since the plan was approved?
• What is the smallest version of this that would still be worth doing?
• Who can say no to new scope, and have they been doing so?

Warning signs

• Milestones move a few weeks at a time, repeatedly.
• The same risk appears on the register for months without mitigation.
• The team is protecting itself in writing.
• Different stakeholders describe the goal differently.

When internal teams can handle it

When the sponsor has authority, the scope is inside one function, and the organization can tolerate an honest reset without political consequence.

When outside help may be appropriate

When the initiative crosses departments or vendors, when internal reporting has lost credibility, or when the people best placed to assess the situation are the same people accountable for it.