How to Recover a Failing Project

The most expensive mistake executives make with a failing project is waiting too long to admit it is failing.

I’ve spent more than 37 years working with complex projects and strategic initiatives across Fortune 500 companies, government organizations, and international operations. One lesson keeps repeating itself: projects rarely fail overnight. They fail quietly, sometimes for months, while leadership continues receiving reassuring reports.

By the time someone calls for help, the original deadline is often impossible, the budget is compromised, and the team has stopped believing the plan.

The first question isn’t how to fix the schedule.

It’s how to restore executive control.

Why Project Recoveries Start Too Late

I’ve walked into programs that had been reporting green for eleven months. By month twelve, everyone knew there was a problem.

Except, apparently, the executives reading the reports.

The delivery team knew. The vendors knew. Middle management suspected. But nobody wanted to deliver the bad news.

This is the classic watermelon project: green on the outside, red on the inside.

Status reporting becomes an exercise in defending yesterday’s commitments instead of describing today’s reality.

Executives need to understand something uncomfortable: if your organization punishes bad news, you aren’t eliminating problems. You’re eliminating visibility.

And invisible problems are expensive.

Hour Zero: Stop the Clock

When a critical initiative is failing, the instinct is to demand a revised plan immediately.

That’s usually the wrong first move.

Before committing to another deadline, stabilize the situation.

Stop making new promises. Suspend unnecessary scope changes. Avoid approving additional spending simply to preserve the appearance of progress.

This doesn’t mean shutting down the entire operation. It means establishing control over decisions that could make the situation worse.

Identify contractual obligations, operational dependencies, and immediate business risks that cannot wait.

Then establish one rule:

No new commitments without verified information.

You cannot recover a project while continuing to manufacture obligations against a schedule nobody believes.

Day One: Find the Real Status

Forget the PowerPoint presentations.

I want conversations.

Meet individually with the people doing the work, the people managing dependencies, and the people responsible for delivering results.

Ask direct questions.

What is actually finished? What remains incomplete? Which assumptions have failed? What is preventing progress? Would you personally bet on the current completion date?

Compare the answers.

Disagreement between the official report and the people executing the work is itself a significant finding.

Look for hidden dependencies, overloaded personnel, unresolved decisions, and deliverables being reported complete that aren’t usable.

Don’t begin by assigning blame.

Begin by establishing facts.

An executive cannot make sound decisions using information filtered through layers of organizational self-protection.

Day Two: Establish One Accountable Owner

Failing projects often have plenty of responsible people and nobody truly accountable.

Committees meet. Steering groups review. Vendors explain. Project managers update schedules.

Meanwhile, decisions wait.

Recovery requires one accountable executive or designated recovery leader with clearly delegated authority to make decisions, escalate obstacles, and recommend stopping workstreams.

That person must have direct access to executive leadership.

Accountability without authority is theater.

The recovery leader also needs explicit decision rights, a clear escalation path, and a defined reporting cadence.

The objective isn’t another layer of governance.

It’s restoring the organization’s ability to act.

Day Three: Rank Everything

Now comes the uncomfortable part.

Not everything deserves to survive.

Every workstream, deliverable, and commitment must be evaluated against business value, urgency, remaining cost, and probability of successful completion.

Separate the work into three categories:

• Must survive: Essential to achieving the business outcome.
• Can pause: Valuable, but not immediately necessary.
• Should stop: No longer justified by its cost, risk, or contribution.

Executives must be willing to terminate work that no longer makes business sense.

Sunk costs aren’t a strategy.

Continuing a failing workstream because the organization has already invested millions doesn’t protect that investment. It can compound the loss.

Recovery sometimes means delivering less to accomplish more.

The First 72 Hours Are About Decisions

At the end of three days, you probably won’t have a perfect recovery schedule.

You should have something more valuable.

A credible understanding of reality, one accountable leader, a prioritized portfolio of work, and executive agreement on what happens next.

Only then should the team build a recovery plan grounded in actual capacity, validated dependencies, and achievable outcomes.

Recovery isn’t a better-looking project plan. It’s executive decision-making restored.

The plan follows.

If your critical project or strategic initiative is slipping, don’t wait for another reporting cycle to confirm what your people already know.

At Project Victories, I help executives independently assess troubled initiatives, establish accountability, and determine the practical path forward.

Your first decision is whether you’re ready to hear the real status.

Book a confidential conversation.

Let’s Git-R-Done this week!