Digital project recovery and supplier oversight

Recovery starts with a usable baseline

I work on the business side of the delivery problem while understanding the technical constraints. That can mean clarifying an incomplete scope, checking whether a proposed solution fits the need, coordinating suppliers or turning a vague completion claim into demonstrable acceptance criteria.

Before taking responsibility for recovery, I need a credible view of what exists. The Digital Project Health Check is the defined diagnostic service. Continuing recovery and oversight are a separate engagement, agreed after the situation is understood.

Create a recovery decision, not another wish list

We identify the minimum useful outcome, the work needed to reach it and the decisions blocking progress. Some features may need to wait. Some requirements may need clarification. Some assumptions may need a short technical investigation before anybody can responsibly promise a delivery date.

A recovery plan should show options: complete with the current supplier, add specialist support, reduce scope, replace a component or arrange a controlled handover. Changing suppliers is one option, not an automatic recommendation.

What I can take responsibility for

• Translating business priorities into clear delivery requirements.
• Reviewing milestones against working software and documented acceptance criteria.
• Coordinating technical, content, search and analytics dependencies.
• Maintaining an issue, risk and decision log with named owners.
• Challenging unsupported completion claims and resolving avoidable ambiguity.
• Planning testing, launch readiness and a usable support handover.

The agreed role must match the access and authority available. Oversight cannot replace a supplier doing its contracted work.

How progress is judged

Useful reporting answers four questions: what now works, what remains, what is blocked and what decision is required. Demonstrations should follow representative business tasks, including errors and exceptions, rather than just show attractive screens.

For example, an enquiry form is not complete merely because its layout exists. Delivery may also require validation, reliable message handling, appropriate data access and an agreed way of checking enquiries reach the right people. Those expectations belong in the acceptance criteria.

Commercial boundaries and next steps

I can work with your existing developers and agencies, implement appropriate technical work directly, or coordinate specialists where required. The responsibilities, time allocation, deliverables and fees are agreed for the recovery engagement. Third-party development and licensing are identified separately.

Send the original brief, current plan, supplier proposal, demonstrations, issue list and the outcome that matters most. I will explain whether a health check, continuing leadership or another form of support is the right first step.