Five Crucial Steps for Project Recovery: Insights from Richard Keenlyside

When projects falter, the stakes rise quickly, leaving businesses exposed to delays, cost overruns and strategic setbacks. In my experience spanning 25 years across diverse industries, I have observed that over 30% of technology and business transformation programmes encounter significant difficulties that threaten their success. Understanding the steps for project recovery is essential to reversing course effectively. Here I share five critical actions based on real-world insights that leaders can rely on to rescue troubled initiatives.

Why Project Recovery Matters

Organisations invest considerable resources into projects aimed at driving growth, compliance and innovation. However, complexity, shifting priorities and unforeseen risks can derail even well-planned initiatives. When projects stall, businesses face cascading problems such as resource wastage, lost market opportunities and diminished stakeholder confidence. Recovery is not just about fixing what has gone wrong but ensuring the project delivers its intended business value.

This knowledge is crucial for transformation leaders, programme directors, CIOs and board members. Without a clear, structured approach to recovery, efforts tend to be reactive and fragmented, leading to repeated failures or abandonments. Having defined steps for project recovery allows leadership to move decisively and with control, minimising disruption and safeguarding investment.

Five Essential Steps for Project Recovery

• 1. Conduct a Rapid, Independent Health Check
  The first step is to gain an objective, comprehensive understanding of the project’s current state. This should include assessment of scope, budget, timeline, resource capability, governance, risk and deliverables. Engage experienced advisors or internal auditors who have no prior involvement to avoid bias. The health check must identify root causes, hidden issues and critical dependencies quickly to inform targeted interventions.
• 2. Re-Establish Clear Governance and Accountability
  Recovery demands rigorous governance with clearly defined roles, responsibilities and escalation paths. Often, initiatives fail because ownership becomes diluted or unclear between business and IT teams or across vendor boundaries. Establishing a programme recovery steering group, chaired by a senior accountable executive, is vital. This team must regularly review progress, mitigation plans and change controls to avoid scope creep or unmanaged risks.
• 3. Re-Define and Prioritise the Project Scope
  In troubled projects, uncontrolled scope expansion or unclear requirements are frequent contributors. A critical recovery step is to revisit the original business case and work with stakeholders to prioritise remaining deliverables. Adopt a phased or minimum viable product approach where possible to realise early benefits and restore confidence. Avoid attempting a full scope delivery when resources and time are constrained.
• 4. Optimise Resources and Skills Deployment
  Resource misallocation or skill mismatches often exacerbate issues. Evaluate if the current team has the right expertise, capacity and motivation. Consider supplementing with external specialists, interim leaders or fractional CIO/CTO roles, especially where leadership gaps exist. Clear onboarding and knowledge transfer protocols accelerate stabilisation. Continual skills development aligned with recovery goals helps rebuild team morale and performance.
• 5. Implement Rigorous Risk Management and Communication
  Early warning systems and transparent communication are indispensable during recovery. Establish risk registers with real-time updates and assign owners for prompt mitigation actions. Regular, honest progress reporting to all stakeholders, including the board, maintains trust and enables timely decision making. Avoiding complacency or sugar-coating issues prevents surprises and reinforces collective ownership of success.

In-Depth Look: Re-Defining Scope and Prioritisation in Practice

One common pattern I encounter is projects attempting to 'do everything' after recovery begins, unintentionally setting themselves up for further failure. For example, in a recent engagement with a mid-sized enterprise undergoing a critical ERP implementation, the project was six months behind and well over budget. The initial recovery focus was on identifying quick wins by slicing the scope into manageable, business-critical releases aligned with user readiness and compliance deadlines.

This prioritisation reduced pressure on delivery teams and allowed early return on investment through functionality that users could adopt immediately. Moreover, it helped rebuild stakeholder confidence when tangible progress became apparent. Subsequently, the project governance adapted to this incremental delivery model, focusing tightly on scope control for each phase and preventing unnecessary feature additions that would have caused delay.

Such practical, outcome-driven scope redefinition ensures that recovery is not simply a race to completion but a structured journey back to project health and value delivery. It also aligns with wider organisational constraints and market conditions, which sometimes change during lengthy projects but are overlooked in the original plans.

Common Mistakes to Avoid During Project Recovery

• Relying solely on the original project team without bringing fresh perspectives or skills.
• Delaying the health check, resulting in loss of crucial time to contain damage.
• Ignoring governance gaps that allow ambiguity around decision making and accountability.
• Trying to salvage the entire original scope without adjustment or prioritisation.
• Failing to communicate honestly with stakeholders about real risks and progress.
• Underestimating the emotional and motivational impact of failure on project teams.

Frequently Asked Questions

How soon should a project recovery process start once issues are identified?

A project recovery effort should begin immediately after the first clear signs of distress are recognised. Delaying assessment and intervention typically compounds problems, increasing the risk of failure and cost overruns. Early health checks allow faster containment and more options for corrective action.

What role does leadership play in successful project recovery?

Leadership is critical in setting tone, clarifying accountability and securing resources during recovery. Without visible, committed senior leadership, projects often struggle to regain momentum. Leaders must be directly involved in governance, risk oversight and clear communication to both teams and stakeholders.

Can a phased approach really save a failing project?

Yes, adopting a phased or minimum viable product approach often prevents overreach by breaking delivery into smaller, manageable chunks. This reduces complexity, allows earlier benefits, and rebuilds confidence systematically. It is a pragmatic strategy to align scope with available capacity and organisational priorities.

In conclusion, the steps for project recovery outlined here represent a tested roadmap to stabilise and restore troubled initiatives. From comprehensive health checks to governance reinforcement, scope redefinition, resource optimisation and rigorous risk management, these actions are pivotal. Applying such an approach, as I have witnessed across multiple industries, provides organisations with the clarity and control required to transform failure into success confidently.