How to rescue a failing project in the first 48 hours

Being asked to rescue a failing project can feel daunting. Deadlines have been missed, stakeholders are frustrated and confidence is low. The instinct is often to jump straight into fixing the technical problems.

In my experience, that's usually the wrong place to start. 

Technology projects rarely fail because of the technology itself. More often, they fail because communication breaks down, business objectives become blurred and teams are no longer working from the same understanding of success.

The first 48 hours are about restoring clarity. These are the five things I focus on when I'm asked to turn a project around. 

Get absolute clarity on where a project stands

Before you can fix a project, you need an accurate picture of its current state.

Often, when things have failed it is down to poor communication. People haven't articulated where things are in the project plan and what is left to go. Different stakeholders often have different understandings of progress, priorities and the work that remains.

Don't rely on status reports alone. Talk to the people doing the work, compare perspectives and establish a single, shared view of where the project actually stands.

Reconnect the project to the business problem 

Once you understand where the project stands, the next step is to remind everyone why it exists.

Projects often drift away from their original purpose. Teams become consumed by system features, technical limitations and implementation decisions, while losing sight of the business problem they were trying to solve. 

Technology is rarely perfect. Successful projects find the balance between what the platform can realistically deliver and how the business adapts its processes to achieve the desired outcome. That requires business and technology teams to work together, rather than expecting one side to simply accommodate the other.

When everyone is focused on the same business outcome, it's much easier to make good decisions about priorities, trade-offs and what success should ultimately look like. 

Bring business and technology back together 

With the project objectives clear, it's time to bring the people responsible for delivering them back into the same conversation.

Long email chains rarely solve complex problems. Rather, they often create misunderstandings, reinforce silos and make disagreements seem bigger than they really are. A face-to-face conversation, whether in person or over video, allows people to ask questions, challenge assumptions and resolve issues far more quickly.

The priority is to bring business and technology teams together early. Both sides need to align on the desired outcome, the project's constraints and their respective responsibilities. When those conversations happen openly and regularly, problems are identified sooner and decisions are made with the project, rather than individual priorities, in mind. 

Build the recovery plan with the team 

The next step is agreeing on how to get the project back on track. 

The recovery plan shouldn't be built for the team - it should be built with them. Involving people in developing the plan helps rebuild ownership, confidence and accountability. Even if the final decision isn't everyone's preferred option, they've had the opportunity to contribute, understand the rationale and commit to moving forward together.

Once the plan is agreed, it's important to re-establish a consistent operating rhythm. Daily stand-ups, weekly progress reviews and regular steering committee meetings create accountability, identify risks early and keep everyone focused on the same priorities.

Be honest about what is - and isn't - possible

Turning around a project isn't about promising the impossible. It's about helping stakeholders understand what can realistically be achieved from this point forward.

Every project is constrained by scope, budget and time. If one changes, another usually has to move as well. That may mean extending deadlines, increasing investment or reducing scope.

Sometimes, however, the right decision is to stop altogether. If a project is no longer delivering sufficient value to justify the cost or effort required to complete it, continuing simply because work has already been invested rarely makes sense.

There's no magic to turning around a project. It comes down to restoring clarity, aligning the team and making deliberate decisions about what success now looks like.