Project Rescue

Your Project is in Trouble. That's Exactly Where I Come In.

It happens to the best organisations. A high-priority initiative stalls. A complex implementation drifts off-course. A technical re-platforming becomes a black hole for budget and resources. Deadlines pass. Stakeholders lose confidence. The team loses momentum.

When a project is over budget, behind schedule, or simply failing to deliver what was promised — you don't need another status update. You need someone who has seen this before, knows exactly what to look for, and can chart a clear path back.

That's what I do.

Why Projects Fail

In 30 years across the full software development lifecycle — as a developer, tester, analyst, and project manager — I've seen the same patterns repeat themselves across industries and organisations of every size. Projects rarely fail for one dramatic reason. They fail because of an accumulation of smaller, fixable problems that were never caught early enough:

• Unclear or undocumented requirements that were never properly challenged

• Testing gaps that allow critical defects to survive deep into the delivery cycle

• Stakeholder misalignment that quietly derails priorities

• Teams operating without a coherent product vision

• Governance structures that generate reporting but not accountability

• Scope creep that nobody felt empowered to push back on

The good news? Every one of these is diagnosable. And most are recoverable — if you act before it's too late.

Signs You May Need a Project Rescue

• Your project has missed multiple milestones and the team has stopped believing the plan

• Stakeholders are losing confidence and asking uncomfortable questions

• Scope has grown significantly without a corresponding adjustment to timeline or budget

• Testing is being compressed or skipped to try to recover lost time

• Key team members are disengaged, leaving, or in conflict

• You've recently received a delivery that didn't match what was promised

• A vendor or internal team has gone quiet

If any of these sound familiar, the sooner you act the more options you have.

What a Project Rescue Looks Like

No two failing projects are the same, so no two rescues look identical. But my approach follows a consistent structure:

1. Rapid Diagnostic

I come in without assumptions and without an agenda. I review the documentation, talk to the team, talk to the stakeholders, and form an independent view of where the project actually stands — not where the last status report said it stood. I look at scope, resourcing, testing coverage, team dynamics, and governance. Within a short, defined window I will tell you plainly what is working, what isn't, and what needs to change.

2. Recovery Roadmap

Once I understand the real picture, I build a realistic recovery plan. This isn't a re-skinned version of the original project plan — it's an honest reassessment of what is achievable, by when, and at what cost. I work with your team to set expectations with stakeholders that are credible rather than optimistic.

3. Stabilisation

I step in at the level the project needs. Sometimes that means working alongside an existing PM to provide structure and oversight. Sometimes it means taking the lead directly. Either way, I focus first on stopping the bleeding — stabilising the team, clearing blockers, and restoring confidence that someone is in control.

4. Delivery

With the project stabilised, I drive it to a successful conclusion — on time, within the revised scope, with proper documentation and a clean handover. The goal is not just to finish the project, but to leave your organisation in a stronger position than when I arrived.

What You Get

• An honest, independent assessment of where your project actually stands

• A credible, realistic recovery plan — not a wishful one

• Hands-on leadership at whatever level the situation demands

• Clear, jargon-free communication with your stakeholders throughout

• A team that has been re-energised and re-focused around achievable goals

• A clean, documented handover at the end

Proven in the Field

This isn't theoretical. I've been parachuted into troubled projects at some of the world's most demanding organisations.

At Yara International, one of the world's largest agricultural companies, I identified a critical structural weakness in a major product programme's testing setup that had gone undetected — and was asked to lead the entire end-to-end testing operation as a result. Hundreds of issues were uncovered and resolved before they could impact launch. Yara trusted me enough to invite me back on two further occasions — including specifically to rescue a project that had gone off the rails.

At AstraZeneca, across three separate engagements in the rare diseases division, I helped restructure and improve project management practices in one of the most high-stakes delivery environments in the pharmaceutical industry.

Being asked back, repeatedly, by organisations of this calibre is the most honest measure of results I can offer.

Let's Talk

The longer a struggling project continues without intervention, the fewer options remain. If you're concerned about a project — even if you're not yet sure whether it qualifies as "in trouble" — I'm happy to have an initial conversation at no obligation.

Want to know more? keep reading, want to know how I can assist with Monday.com click here.