Getting troubled programmes back to reality, control and delivery
Technology and transformation programmes rarely fail suddenly. They usually drift first. Scope becomes unclear. Costs move. Timelines slip. Supplier confidence weakens. Key people leave. Governance meetings continue, but the underlying issues remain unresolved. Reports may still show progress, while the board, executive management, client teams, vendors and delivery teams all sense that confidence is being lost.
When that happens, the first requirement is not optimism. It is an honest assessment of reality.
Project recovery starts by establishing where things actually stand: what was promised, what has been delivered, what is still unclear, what risks are being carried, what commitments have been made, what the commercial position is, and whether recovery is still the right objective. In some cases, the answer is to recover and continue. In others, the better decision may be to re-scope, pause, renegotiate, replace a supplier, strengthen governance or close out a failed initiative properly.
My work helps organisations bring structure, challenge and practical delivery discipline to programmes that have gone off track.
Where this helps
Project recovery support is particularly useful where an organisation is:
- facing a programme that is behind schedule, over budget or unclear in scope
- losing board, executive management or stakeholder confidence
- struggling with supplier performance, contract pressure or delivery disputes
- dealing with weak governance, poor reporting or unclear accountability
- managing ERP, platform, cloud, AI, data, healthcare or operational systems change
- concerned that the business case is no longer credible
- unsure whether to continue, re-scope, pause or close the project
- experiencing poor adoption, weak business readiness or unresolved process issues
- dealing with loss of key people or knowledge on the client or vendor side
- needing an independent view before committing further funding
- trying to turn a distressed programme into controlled delivery
The issue is often not just project management. It is the combination of governance, business ownership, supplier control, financial discipline, technical complexity, contractual position, people, trust and operational readiness.
Practical recovery experience
I have practical experience recovering and closing out troubled projects across financial services, construction and FMCG, in both local and international environments. These situations often involve more than a missed deadline. They can involve unclear scope, strained supplier relationships, weak governance, contractual pressure, budget exposure, poor adoption, loss of knowledge and a loss of confidence between the board, executive management, delivery teams and external partners.
The first step is to get a clear understanding of the situation. That means looking beyond status reports to understand what has actually been delivered, what remains unresolved, what the commercial position is, what commitments have been made, what legal or contractual issues may exist and what level of confidence can realistically be restored.
Successful recovery also depends on people. The right individuals need to be in the right roles, with clear ownership, decision rights and authority. In many cases, progress starts by simplifying the plan, focusing on the few actions that matter most and rebuilding confidence through consistent, visible, small wins.
Where contractual or legal issues are material, I work alongside legal advisers with a clear practical focus: understanding the position, protecting the organisation’s interests, and supporting a route forward that recognises the commercial and operational realities. The aim should be mutual success where possible, but with enough clarity to close out poorly scoped, late or over-budget projects responsibly where recovery is no longer realistic.
Project recovery is not for the faint-hearted
By the time support is needed, confidence may already be low, relationships may be strained, money may have been spent and people may be cautious about saying openly what has gone wrong.
Typically, by the time project recovery support is needed, a number of people will already have left, on the client side, the vendor side, or both. Some of the knowledge needed to understand the original decisions may have disappeared, and some of the people you most want to retain may already be considering whether they want to stay involved.
That is why stakeholder support matters. Recovery is not achieved by one person producing a plan. It requires enough backing from the board, executive management, delivery teams, suppliers and advisers to stabilise the situation, retain or re-engage the right people where possible and create the conditions for progress.
Building trust from the bottom to the top is essential. The people closest to the work often know where the real issues sit, but may have stopped saying so clearly if previous warnings were ignored. Recovery depends on listening carefully, being honest with senior stakeholders and creating a practical route forward that people can believe in.
The work requires directness, but also judgement. It is usually not helpful to start with blame. The priority is to understand the facts, the commercials, the delivery reality, the contractual position, the people issues and the options available. From there, it becomes possible to build a feasible plan, put the right people in the right roles and rebuild confidence through consistent, visible, small wins.
What my experience brings
I bring practical experience leading and recovering complex technology and business change as CIO, CFO, Chartered Accountant, computer engineer and transformation lead. That combination matters because distressed programmes usually have more than one cause.
A technology project may actually be suffering from a weak business case, unclear ownership, poor supplier management, underdeveloped operating model, unrealistic timeline, inadequate budget, poor data, weak testing, lack of change readiness or insufficient executive challenge.
My experience includes ERP and business process transformation, Microsoft Dynamics and Salesforce platform delivery, cloud adoption across Azure and AWS, RIS/PACS and healthcare systems, technology refreshes, IT outsourcing, analytics capability development, supplier management, commercial contract renegotiation, failed project close-out and major programme oversight across financial services, construction, FMCG, pharma, AEC, healthcare, distribution, public/semi-state environments, start-ups and fast-growth companies.
I have also managed through situations where projects were under real pressure: security breaches, supplier issues, contract renegotiations, failed initiatives, delivery loss of confidence and board-level concern. That experience helps separate symptoms from causes and determine what action is needed.
How I help
Support can include:
- independent review of programme status, scope, budget and delivery confidence
- assessment of governance, reporting, accountability and decision-making
- review of supplier performance, contract position and delivery obligations
- review of the commercial position and funding exposure
- challenge and refresh of the business case
- identification of critical risks, blockers and unresolved decisions
- review of technical, data, integration, testing and business-readiness issues
- assessment of people, knowledge-retention and capability risks
- development of a realistic recovery plan
- re-prioritisation of scope, milestones and resources
- support for board and executive management reporting
- facilitation between business, technology, finance, supplier, legal and delivery teams
- commercial renegotiation support where supplier or contract issues are material
- support in working constructively with legal advisers where needed
- recommendation on whether to continue, re-scope, pause or close out the project
- hands-on support to restore delivery discipline and stakeholder confidence
The work is practical and direct. It is not about producing a long review that confirms what people already suspect. It is about clarifying the position, identifying the choices and putting the delivery structure around the agreed way forward.
Recovery, re-scope or close-out
Not every project should be recovered in its original form.
Sometimes recovery means getting the programme back under control and continuing with renewed discipline. Sometimes it means reducing scope, changing the delivery model, replacing governance, strengthening business ownership, changing the team, renegotiating supplier commitments or resetting stakeholder expectations. Sometimes it means recognising that the original objective is no longer realistic and closing the project properly before more money, time and confidence are lost.
Closing out a late, over-budget or poorly scoped project is difficult. There may be contractual sensitivities, sunk cost, stakeholder disappointment, supplier defensiveness, internal embarrassment and concern about what the decision says about previous governance. But avoiding the decision can create greater damage.
A good recovery process should give leadership a clear view of the options and consequences: what can be saved, what should stop, what must be decided now, what further investment is justified, what risk remains and what confidence can realistically be restored.
This is where independent challenge matters. When a programme is already under pressure, internal teams and suppliers may each have reasons to defend the current position. An independent view can help the organisation make better decisions based on evidence, not hope.
Why this matters
Business Advantage through Technology is only achieved when programmes deliver outcomes that the organisation can use.
When projects drift, the cost is not only financial. Confidence is lost, teams become frustrated, suppliers become defensive, stakeholders disengage and the business benefit becomes harder to realise. Continuing without a clear recovery plan can make the situation worse.
Project recovery helps restore clarity, control and confidence. It gives boards and executive teams a practical basis for deciding what to do next, and helps ensure that technology investment is either brought back to value or stopped responsibly.