The bridge

Large IT outsource deals get most of their attention in two places: procurement, when the contract is being shaped and the supplier is being chosen, and steady state, two or three years in, when the service is running and the metrics are mostly green. The phase in between, transition, is the phase that decides whether the outsource actually works. It also explains why so many deals take longer to reach steady state than the business case promised and why some never quite get there at all.

Having worked on a number of outsource transitions, what strikes us most is how little of the difficult work is about the contract or the technology. The work is about people, on both sides, finding each other, trusting each other and slowly building the daily habits that let two organisations operate as one. The role that holds that work together, and the role we want to describe here, does not sit neatly on either side’s organisation chart. It is not a new layer of governance, and it is not simply another name for transition management. It is the role we have come to think of as the bridge.

Why transitions slip

Most outsource transitions slip for the same structural reason, and it is not a failing of any party. The contract is the wrong instrument for the work that delivery actually requires. No matter how well it is drafted, how favourable the terms are to the client, or how carefully the clauses were negotiated, the contract operates at a level of abstraction that day-to-day delivery does not. The application of the work brings every clause down to a granular level of detail that no contract can fully cover, and the granularity is where the friction lives.

When something hits a gap or an ambiguity, the parties naturally default to checking what the contract says. The contract often says something incomplete, or each side has read it differently, and what was a working question becomes a contractual one. That triggers a sequence: a formal request for clarification, a response from the other side’s legal or commercial team, a delay while both organisations navigate their own internal positions, and a defensive posture that takes weeks to dissipate. Multiply that by the hundreds of granular moments a complex transition produces, and the schedule does not slip because anyone failed. It slips because the machinery the parties keep falling back on is not designed for the resolution speed the work demands.

Good RFP work, ideally with an independent voice helping the client shape requirements and terms, can reduce the size of the gaps. It cannot eliminate them. The contract is a snapshot of what could be foreseen at signature. Delivery is everything that could not be foreseen, and large organisations are particularly good at producing situations that nobody foresaw. The bridge is what navigates the gap between the two.

Where the gaps actually open

The day-to-day surface of a transition is full of small decisions the contract did not anticipate. How the joint governance forums actually run when they are not in front of the contract. Who really owns the parts of the service that sit between the new provider’s scope and the client’s retained organisation, where the honest answer is that the client owns whatever the contract did not assign and where both parties usually started by assuming the other would cover it. What happens when something goes wrong on a Tuesday afternoon and the relevant page of the contract is silent or ambiguous.

These are not edge cases. They are the substance of the outsource. The question is whether the parties have someone with the time, the standing, and the institutional memory to make sure those resolutions actually happen, get recorded, and accumulate into a working relationship rather than a series of ad hoc decisions that nobody can later reconstruct. In most cases that role will sit on, or be commissioned by, the client side, but its value depends on being able to work credibly across the table.

What the bridge actually does

The role is hard to describe in a single sentence because it is constituted by a particular collection of small things, none of which is glamorous and most of which look optional from a distance. That is also why it is easy to confuse with other roles around a transition. The bridge is not the whole client-side transition function, and it is not a substitute for retained service ownership, SIAM, vendor management or formal governance. It exists to do the connective work between them.

It is sitting in the supplier governance forums as the client’s voice, week after week, so that the supplier is talking to a familiar face rather than a rotating cast of stakeholders. It is the patience to maintain the dependency map between the new provider, the incumbent, the network and security services, the internal teams and the remaining third parties and to update that map every time one of the conversations in the room shifts a boundary. It is being available for the off-record call from the supplier’s service director who needs a sanity check, and the equally off-record call from the client’s programme lead who wants a view from someone who knows the supplier well enough to predict how they will react. And it is the slow, persistent work of writing things down: what was decided, why the service description was amended, what the implicit expectations are around an interface that the contract treats as both parties’ responsibility. The institutional memory of a transition lives in those notes, and it lives with the bridge, because the bridge is the only role still in place late in transition with the same view it had on day one.

Three funding models, one role

A reasonable objection at this point runs as follows. The bridge sounds like a client-side transition manager with a different name, and if the role is funded by the client, how can it be the fair broker the argument has been describing? It is worth being explicit about the commercial model, because that is where much of the scepticism naturally sits. Who funds the role, what it is accountable for, and what it is not there to do should be clear from the outset, even when those points do not change the substance of the work.

In practice the bridge can be funded three ways. The client pays, which is the most common arrangement and the one this piece has so far implied. The supplier pays, where the supplier judges that an honest broker accelerates its own path to steady state and helps establish a relationship worth developing. Or a hybrid model, where both parties contribute and the role is explicitly set up to support the transition as a shared commercial objective. Nobody is keen to pay extra for a role that does not appear in the original deal. But the economics across all three models reward the same thing: a transition that lands faster, with less rework, fewer avoidable disputes and a relationship that sets in a way that supports a longer-term outsource rather than a contested one.

The case is similar from each side, though not identical. The client wants the work done faster and better, with less of its own leadership time consumed managing exceptions and with less risk that transition friction erodes the value of the deal. The supplier wants to reach steady state, build credibility and earn the right to develop the relationship further, none of which happens easily if the transition is fraught. Whoever pays, the underlying logic holds: the client’s best interests are served by the supplier performing well, and the supplier’s best interests are served by a transition the client trusts. The bridge’s fairness across the table is not a concession from either side. It is the operating principle that gives the role commercial value for both. If the client is not seeing the value clearly enough to fund it, there is a real argument for the supplier to do so as an investment in smoother delivery and the future of the account.

This is also what distinguishes the bridge from a conventional client transition manager. A transition manager tracks the schedule, the milestones and the risks from the client’s side. The bridge may overlap with some of that work, but its distinct value lies elsewhere: in carrying continuity across the phases of the deal, translating intent across the table and investing deliberately in the working relationship because the relationship is often what determines whether the schedule survives contact with reality.

The role also has a defined arc. It properly begins at the RFP, where the client benefits from an independent voice helping shape requirements, terms and the structure of the competition. It continues through the supplier’s bid, where it carries forward the client’s actual intent rather than the procurement document’s wording and into transition, where the work described in the rest of this piece happens. It ends when both sides are in steady state and the relationship is delivering on its own. The bridge is engaged for a phase of the outsource, not the whole life of it, and if it remains indefinitely it has either become part of the operating model or failed to work itself out of a job.

Why the role is hard to fill from either side

Even granted the case for the role, the natural follow-up is that the work should sit with the client’s own people. In principle that is right. In practice the transition is the very moment when the retained organisation is at its smallest, the leadership is at its busiest, and the SIAM function (if one already exists) is under most pressure, or is being designed at the same time as the service it is supposed to integrate. The people who would naturally play the role are absorbed in doing their normal jobs alongside the transition, and the transition is, structurally, more than a normal job. There is also a resourcing asymmetry to acknowledge: large managed service providers arrive with a permanent account structure, experienced from dozens of similar deals. The client, often doing this for the first time in a decade, cannot easily match that on its own side.

The supplier’s team has a different problem. They have the bandwidth, but they are not the right party to play the bridge. Their job, properly, is to deliver the service described in the contract. They cannot be the independent translator between themselves and the client, and the client cannot rely on them to be, however good their intentions. That is not a criticism of the supplier’s relationship managers, who are skilled, experienced and almost always working in their client’s interest. It is a structural fact about the deal, and one reason the bridge needs a clearer mandate than a normal delivery or account role.

The bridge is, in our experience, most often a specialist consultancy or adviser: small enough to commit senior practitioners to a single deal over its transition, independent enough to broker honestly across the table and structurally clear of any implementation revenue that would compromise the role. Large consultancies often struggle to make the economics work for an engagement of this shape. That said, the important point is the function rather than the label. What matters is that the role has enough continuity, standing and commercial clarity to be trusted by both sides. The role then tapers as the outsource matures.

Protecting the people on both sides

The part of the role that has surprised us most is how much of it is about looking after the people, on both sides, who are caught up in the transition.

On the incumbent or in-house side, individuals are often asked to hand over deep, hard-won knowledge to a new provider when their own future is, in many cases, already decided: a role that will end at the close of transition or be substantially changed. The professional thing to do, which most of them try to do, is to transfer everything they know in good faith. That requires a level of trust in how the knowledge is going to be used and valued that the formal structure of a transition does not naturally create. Someone has to be in the room when the handover is happening, without commercial interest in the transfer itself, to make sure it is treated as a knowledge-transfer exercise and not an extraction exercise. That trust matters not only for the morale of the people involved, but for the quality of the knowledge that actually gets transferred. Knowledge given reluctantly is rarely complete.

On the supplier side, the people taking on the service are often arriving into an environment they do not yet fully understand, with senior leaders watching closely on both sides. They need a route into the client organisation that is not always through a formal governance meeting, somewhere they can ask the question they do not want to put in writing. The bridge can be that route, because the bridge is talking to both sides every day and knows where the sensitivities actually sit.

What that produces, when it works, is a transition in which the people involved feel respected by the process rather than processed by it. Knowledge transfers more completely. Relationships set more firmly. The conversations that need to be hard get to be hard in the right rooms, with the right people and not in the wrong ones. And the transition reaches steady state closer to the date it was promised.

The honest-broker function

Every transition produces moments where the supplier and the client see a situation differently and need to talk it through. Sometimes it is a missed service-level target that looks straightforward on paper and turns out to have a real cause neither party fully owns. Sometimes it is a piece of scope that the contract is silent on, and that both parties had assumed the other would cover. Sometimes it is an individual on one side or the other who is struggling with a specific working relationship.

These conversations need to happen, and they need to happen in a way that does not damage the relationship. The supplier’s account team cannot always raise them without it looking like a commercial move. The client’s leadership cannot always raise them without it looking like a contractual one. The bridge can have the conversation that the relationship managers cannot. The aim is almost always the same: get to the real issue, fix it informally if it can be fixed informally and only escalate if it genuinely needs to be escalated. That is the value of the role, and one reason its commercial value is often easiest to see in the disputes and delays that never quite materialise.

How the bridge sits next to the formal model

None of this is a replacement for the formal structures. A well-designed SIAM function provides the integration model. A well-staffed retained organisation provides the service ownership. A capable supplier provides the service. The contract provides the boundaries. The bridge sits alongside all of these, doing the part that none of them is structurally able to do: working the relationships, carrying the institutional memory and being there when the boundaries get tested.

And the bridge knows when to leave. As the retained organisation matures, the working patterns set, and the joint governance becomes self-sustaining, the role tapers and ends. A role that does not know when to leave becomes part of the problem it was set up to solve.

Final thought

The bridge is not a job title that appears on the org chart of any party to a large IT outsource deal. It is a function that, properly filled, can make the difference between a transition that lands on time and one that quietly slips a year while everyone explains why. The visible outcome of the role is that the transition feels smooth, the people on both sides feel looked after, the relationships set in a way that survives the inevitable difficult moments and steady state arrives close to when the business case said it would. None of that looks dramatic, and most of it would not show up in any report.

The clearest sign that the role is doing its job is that nobody on either side feels the need to talk about it. The bridge is most valuable when it is least noticed. That is precisely why it so often goes unfilled, and why that absence is costly.