When a project is in trouble: what recovery actually involves

By the time a project is described as ‘in trouble’, it has usually been in trouble for a while. Deadlines have slipped quietly, the budget has stretched and the same decisions keep coming back to the table. The usual reaction — more people, more meetings, more reporting — adds load without fixing the cause. Recovery is a structured process, and it follows a predictable shape.

Why projects get into trouble

Troubled projects rarely have a single cause. More often several small weaknesses compound: an optimistic plan, unclear ownership of decisions, unmanaged supplier dependencies and a team stretched across day jobs. Each one is manageable. Together, they create a project that can no longer see itself clearly — which is why the first job of recovery is to restore an honest view.

Stage 1: Assess the real position (1–3 weeks)

An independent assessment looks past the status reports to the evidence. The aim is one truthful picture that leaders and the team can agree on. Focus on:

• Delivery: what has actually been completed and accepted, not what is ‘nearly done’.
• Money: spend to date, committed costs and a realistic forecast to finish.
• Plan: which milestones are achievable and which are aspirational.
• Decisions: what is blocked, who needs to decide, and for how long it has waited.
• People: capacity, morale and where key knowledge sits.
• Suppliers: what has been contracted, what is being delivered and where the gaps are.

Stage 2: Reset the plan and governance

With the facts agreed, leaders can make the choices that were previously avoided: reduce scope, re-phase delivery, add funding or, occasionally, stop. The reset produces a re-baselined plan the team believes in, a short list of priorities, risks owned by named people, and a decision path that is quick and clear. Governance should be lighter after a reset, not heavier — fewer meetings, with better information.

Stage 3: Rebuild confidence

Teams on troubled projects are often tired and wary. Confidence returns through honest communication, a few visible early wins and reporting that matches what people experience on the ground. Stakeholders need a consistent rhythm of updates, so bad news arrives early and in context rather than as a surprise.

A typical scenario

Consider an illustrative example: a systems programme is four months late, with three versions of the plan in circulation. A two-week assessment shows that most delay traces back to two unresolved design decisions and a supplier waiting on data. The reset splits go-live into two phases, assigns each decision to a named owner with a date, and introduces a fortnightly supplier review. Within six weeks the first phase is back on a credible path, and steering meetings get shorter because the information is trusted.

Recovery checklist

• Do we have one agreed view of progress, cost and risk?
• Is every blocked decision assigned to a named person with a date?
• Is the plan something the delivery team would sign up to?
• Have we deliberately reduced or re-phased scope where needed?
• Do stakeholders hear about issues early, from the project itself?

The earlier a drifting project is reviewed, the cheaper it is to fix. A short health check is often the best-value step any sponsor can take.