Your project is red. Leadership is asking hard questions. Stakeholders are losing confidence. The timeline that seemed aggressive but achievable three months ago now looks like fiction.

You have a narrow window to turn this around. Not weeks. Days.

Most project managers respond to crisis by working harder. More hours. More status meetings. More pressure on the team. But effort without strategy just accelerates failure. You end up exhausted and still behind.

What you need is triage. A systematic approach to stop the bleeding, diagnose the real problem, and reset expectations before the project collapses entirely.

This is the framework I use when clients call me in crisis. It works for IT implementations, digital transformations, ERP rollouts, and virtually any complex initiative that’s gone off the rails. The timeline is 72 hours. Here’s how to use them.

Hour 0-24: Stop the Bleeding

The first 24 hours are about stabilization, not solution. You can’t fix what you don’t understand. And you can’t understand the problem if everyone is still running in six different directions.

Pause all non-critical activity.

This feels counterintuitive when you’re behind schedule. But continuing to execute a broken plan just digs the hole deeper. Call a tactical pause. Stop all work that isn’t directly related to keeping the lights on or preventing immediate disaster.

Identify the three biggest immediate risks.

Not ten risks. Not everything that could go wrong. Three. The ones that will cause the most damage in the next two weeks if not addressed. Write them down. These become your focus.

Establish emergency communication cadence.

Daily standups. Fifteen minutes. Same time every day. No exceptions. This isn’t about status reporting. It’s about rapid problem identification. What’s blocked? What changed overnight? What do you need in the next 24 hours?

Get honest status from the team.

Not the status report. The real status. Talk to people individually. Ask what they’re not telling you in meetings. Ask what they would do differently if they were in charge. You’ll hear things that never make it into the weekly update.

By the end of hour 24, you should know what’s actually happening. Not what the project plan says should be happening. What’s real.

Hour 24-48: Diagnose Root Cause

Now that you’ve stopped the chaos, you can think clearly about what went wrong and what’s recoverable.

Determine the category of failure.

Most failing projects fall into one of three categories:

• Scope problem: You’re trying to deliver more than the timeline and budget allow. The plan was never realistic.
• Resource problem: You don’t have the right people, enough people, or people with enough time allocated.
• Governance problem: Decisions aren’t getting made. Escalations go nowhere. Politics are paralyzing progress.

Often it’s a combination. But one is usually the primary driver. Identify it.

Separate symptoms from causes.

“The team is demoralized” is a symptom. “We’ve changed direction three times in two months” is a cause. “Testing is behind schedule” is a symptom. “We don’t have a dedicated test environment” is a cause. Keep asking why until you hit something structural.

Identify what’s recoverable versus what needs to be descoped.

Be honest. Some things can be accelerated with more resources or better processes. Some things cannot. If you’re three months behind on a six-month project, you’re not going to make it up with overtime. Something has to give.

Create your “must have” versus “nice to have” list.

What absolutely must be delivered for this project to be considered a success? What was in scope but could be deferred to a future phase? This list becomes the foundation for your reset conversation with leadership.

Hour 48-72: Reset Expectations

This is the hardest part. You have to tell leadership that the current plan isn’t working. But you’re not just delivering bad news. You’re presenting a path forward.

Prepare your executive briefing.

This is not a status update. It’s a decision meeting. Structure it clearly:

• Current state (honest assessment, no spin)
• Root cause (what actually went wrong)
• Options with tradeoffs (not just one path)
• Recommendation
• Decision needed

Present options, not excuses.

Executives don’t want to hear why it went wrong. They want to know what happens next. Give them choices:

• Option A: Reduce scope to meet original timeline
• Option B: Extend timeline to deliver full scope
• Option C: Add resources to accelerate (with realistic assessment of impact)

Each option should include timeline, budget, and risk implications. Let leadership make an informed decision.

Propose a revised baseline and get formal sign-off.

Once leadership chooses a direction, document the new plan. New scope. New timeline. New budget if applicable. Get explicit approval. This becomes your new baseline. Everything from this point forward is measured against the reset plan, not the original fantasy.

Week 1-4: Stabilization

You’ve stopped the bleeding and reset expectations. Now you need to rebuild momentum.

Maintain daily standups.

Don’t relax back into weekly status meetings. Keep the daily cadence for at least 30 days. Problems surface faster. Course corrections happen sooner. The team stays aligned.

Establish exception-based reporting.

Leadership doesn’t need to see everything. They need to see variances. What’s off plan? What’s at risk? What decisions do you need? Create a simple dashboard that highlights exceptions rather than drowning executives in detail.

Remove blockers with executive air cover.

You just had a reset conversation with leadership. Use that capital. When something is blocked, escalate fast. Get decisions made. This is not the time for patience with organizational friction.

Generate quick wins to rebuild confidence.

Find something you can deliver in the next two weeks. Something visible. Something that demonstrates progress. Momentum matters. A team that has been failing needs evidence that success is possible.

The Recovery Dashboard

During recovery, you need different metrics than normal project tracking. Focus on these:

• Variance from reset baseline: Are you tracking to the new plan?
• Blocker aging: How long do issues stay unresolved?
• Decision velocity: How quickly are escalations getting resolved?
• Team confidence: Do people believe recovery is possible?
• Stakeholder trust: Is leadership confidence improving or declining?

Track these weekly. Report honestly. The goal isn’t to show everything is fine. The goal is to show trajectory. Are things getting better or worse?

When to Kill the Project Instead

Sometimes rescue isn’t the right answer.

The sunk cost fallacy is powerful. You’ve already invested six months and two million dollars. Walking away feels like admitting failure. But continuing to invest in a fundamentally broken initiative isn’t strength. It’s denial.

Consider termination when:

• The business case no longer holds (market changed, strategy shifted, ROI no longer justifies investment)
• The minimum viable scope doesn’t deliver meaningful value
• Political dysfunction is so severe that no amount of process improvement will overcome it
• The technology choice was fundamentally wrong and recovery requires starting over anyway
• Key sponsors have lost confidence and won’t provide the support needed for recovery

Making the kill recommendation takes courage. But sometimes the best thing you can do for an organization is help them stop wasting resources on something that will never succeed.

We’ve Been Here

Project rescue is where I’ve spent a significant portion of my 18+ years in PMO transformation. Financial services firms with ERP implementations gone sideways. Healthcare systems with clinical system rollouts that missed every milestone. Government agencies with modernization projects that lost stakeholder confidence.

The pattern is remarkably consistent. The problems that seem unique to your situation usually aren’t. The solutions that work follow predictable principles. Triage. Diagnosis. Reset. Stabilization.

The organizations that recover are the ones willing to face reality early, make hard decisions fast, and commit to a realistic path forward. The ones that fail are usually still debating whether there’s really a problem while the project burns.

Is Your Project in Trouble?

If you’re reading this article because you have a project in crisis, you already know something has to change. The question is what.

Download our Project Triage Assessment Template. It walks you through the diagnostic process described in this article. Use it to structure your analysis and prepare for the reset conversation with leadership.