Technology Services
Delivery management and governance across multi-vendor programmes.
The problem
Large programmes rarely fail suddenly. They fail through a series of status reports that were technically accurate and collectively misleading, until the gap between the plan and the position is too large to close quietly.
The mechanism is almost always the same and it is not dishonesty. Each vendor reports accurately on its own scope. Each report is green because each vendor is doing what its contract says. What nobody reports on is the space between the contracts, which is where the dependencies live, and a dependency with no owner is a dependency that will be discovered at integration.
Reporting drifts by increments rather than by lies. A milestone gets redefined slightly to reflect what was actually achievable. A risk moves from red to amber because it is being managed, which is true, without the underlying exposure changing. None of these is a misrepresentation and the cumulative effect is a status pack that describes a programme nobody would recognise from the inside.
The sponsor is usually the last to know, and structurally so. Bad news travels slowly upward because each layer reasonably hopes to have resolved it before it needs escalating. By the time the gap is undeniable, the options that were available six months earlier, rescope, resequence, renegotiate, have expired, and what remains is expensive.
Multi-vendor programmes concentrate all of this. Each vendor has commercial reasons to hold its position, a different reporting cadence, and a different definition of done. Without a single plan and a single dependency register, integration becomes the moment when four accurate accounts of progress turn out to be incompatible.
And there is a specific failure that is worth naming because it is so common: the programme where everyone senior privately knows the date will not hold, and nobody will say it, because the person who says it first owns the consequence. That is a governance failure rather than a delivery one, and it is fixable by giving the assessment to someone whose job is to make it.
Recognise any of these
If three or more of these are true, this page is about your estate.
What we build
Named platforms, not categories. If you run one of these, this is the conversation.
A single integrated plan with each vendor’s commitments in it, and one dependency register that crosses contract boundaries. The value is not the artefact; it is that the space between contracts acquires an owner. Nearly every multi-vendor integration failure traces back to a dependency that was inside nobody’s statement of work.
Governance designed so that an early warning is rewarded rather than punished, and so that the escalation route does not require the person raising it to also own the fix. Concretely: a standing item for what changed since last time, a named owner per risk, and an explicit route for a delivery lead to flag a date they no longer believe in.
Every dependency has an owner, a date, and a stated consequence if it slips. "Owned by the programme" is not an owner. This is the least glamorous part of the discipline and the one that most reliably prevents the failure this page is about.
Reporting built around decisions the sponsor needs to make, not around activity completed. A status pack that requires no decision is a status pack that will be filed, and a filed pack is one nobody will remember reading when the position deteriorates.
For programmes already in trouble, the work starts with a position assessment: what the plan says, what is actually true, and what has not been said out loud. That is deliberately uncomfortable and it is the only place recovery can start from. It is also the part an incumbent usually cannot deliver, because they are part of what needs assessing.
How the engagement runs
Scope, schedule and cost committed, the plan variance is measured against.
VSI delivers
An integrated master schedule with dependencies and resource loading that survives contact with reality.
Work proceeds; status is a number, not a narrative.
VSI delivers
Earned-value tracking and risk-register discipline, reported the same way every period.
Variance triggers action while recovery is still cheap.
VSI delivers
Corrective plans with owners and dates, and the escalation made before the sponsor finds out another way.
Benefits measured, lessons captured, capability retained.
VSI delivers
Closure against the business case, and the delivery playbook handed to your team.
How it deploys
And what we need from you at each step. A timeline with no client obligations in it is a timeline that slips.
Position assessment: plan, actuals, risks and what is unsaid.
Replanned baseline with dependencies and owners named.
Delivery management, governance and reporting.
How this goes wrong
Published because it is only writable by somebody who has had the failure. Each of these has happened on this kind of work, and each has a specific thing that prevents it.
Return on investment
Every lever names the mechanism and how it is measured against your own baseline, captured before the work starts. That is how the return stays a number your finance team can audit rather than a promise on a slide.
Late programmes cost in extended teams, delayed benefits and remediation. Earned-value discipline, schedule and cost performance indices tracked from a baselined plan, surfaces the slip while it is still recoverable, measured as variance caught early versus discovered late.
The cheapest project to fund is the failing one you rescue: the spend is sunk and the benefit is still on the table. Recovery starts with an honest re-baseline, and the measurement is delivery against that re-baseline, published to the sponsor, every period.
The largest saving in most portfolios is the project that should stop. Stage gates with real criteria free that budget deliberately, measured in funds reallocated from stopped work to work that clears the gate.
Training and mentoring move delivery capability in-house, so the return compounds after we leave. Measured in the client’s own delivery statistics, on-time rates by their PMs, on their projects, after handover.
Timing
Most of the value in this decision is in when, not whether. Find the row that matches your situation.
| Criterion | Verdict | Why |
|---|---|---|
| Integration between vendors is approaching and dependencies have no owners | Now | Integration is where unowned dependencies become visible, and by then the options are expensive. |
| Senior people privately doubt the date | Now | The gap between what is known privately and what is reported is the exact failure mode this addresses, and it only widens. |
| A programme is already late and the position is disputed | Now | Recovery cannot start from a disputed position, and establishing an agreed one is a two-week piece of work. |
| A large multi-vendor programme is being mobilised | Soon | Cheapest point to establish one plan and one dependency register is before any vendor has started reporting separately. |
| Single vendor, single team, delivering to plan | It can wait | You do not need this. If someone tells you otherwise, ask what it would fix. |
Public-sector programmes add reporting obligations that are external rather than internal, to an oversight body, an appropriations cycle, or a milestone published in a way that makes it politically expensive to move. That changes the calculus on early warning: the cost of surfacing a slip late is far higher, because the options for absorbing it quietly do not exist. Governance therefore gets designed around the external reporting calendar rather than around a monthly internal cadence, and the dependency register has to include the client-side obligations, approvals, access, accreditation, third-party sign-offs, which in government work are more often the critical path than any vendor’s delivery is.
Objections
Questions
Occasional updates across every VSI service, new capabilities, new offerings, and what changed. No sales sequence; leaving is one reply.
Used only for these updates, see the privacy statement.
What it costs
Position assessment is fixed-price and two weeks. Ongoing management is scoped from what it finds.
Book a 20-minute assessment
