What a project rescue engagement actually looks like

Project rescue is an uncomfortable phrase. Nobody wants to need it. But projects do go wrong. Timelines slip, budgets overrun, teams lose confidence in the direction, and at some point someone has to assess the situation honestly and work out what is still salvageable. That is what this engagement is for.

The first thing we do is listen, not diagnose ¶

When something has gone wrong, there are usually multiple accounts of why. The project manager has one version. The sponsor has another. The team doing the work has a third. All of them are partial. The first job is to collect those accounts without immediately trying to reconcile them.

This takes longer than it looks. People are often guarded when they know an outside person is assessing a failure. The conversations need to be genuinely open. Not an audit, not a blame exercise. Before the useful information starts to come out.

Assessing what is recoverable ¶

Not everything that has gone wrong can be fixed. Some projects are too far off course to rescue within the original constraints. Part of the value of an outside assessment is being able to say that plainly, without the internal politics that make it hard for people inside the organisation to say the same thing.

The assessment covers three things: what has been built or produced that is still useful, what the realistic cost and time to completion would be under different scenarios, and what the organisation's actual appetite is for continuing versus stopping. All three matter.

The output ¶

The output of a project rescue engagement is a short written assessment and a recommendation. The recommendation might be to continue with a revised scope and timeline. It might be to stop and extract what is useful. It might be something in between. The point is that it is honest and specific, not a diplomatic hedge.

Project rescue engagements vary in length and fee depending on the situation. The scoping call is always free and always confidential.