Improvement Without a Single Owner

Governing continual improvement across a multi-supplier SIAM ecosystem

Consider a degradation that spans three towers: a network provider, a hosting provider and an application maintenance supplier. Each meets its service levels and closes its tickets. Users, meanwhile, endure a fault that recurs every few weeks because it originates in one domain, surfaces in another and resolves in a third. The fix that would end it — a monitoring threshold adjusted here, a data-sharing agreement there — benefits the whole chain and sits in no supplier's remit.

This is the defining improvement problem in Service Integration and Management (SIAM).[1] The value left unclaimed lies between providers, in the seams where end-to-end service is produced but no single party is accountable for it. Improvement in a SIAM ecosystem is therefore a coordination and governance challenge before it is a technical one — a point practitioners echo in the Global SIAM Survey 2025, where integration was the single most-cited challenge, named by 74% of respondents.[3] The methods are well understood; the open questions are who convenes the parties, who funds the work, and whose incentives reward the result.

Why improvement is structurally harder under SIAM

In a single-supplier arrangement, one provider owns the end-to-end service and internalises the cost and benefit of improving it. SIAM deliberately dismantles that arrangement, distributing delivery across specialist towers to gain flexibility and competitive pricing.[1] The trade-off is fragmented accountability. Each provider holds a contract scoped to its own domain, with service levels, reporting and improvement commitments bounded by that scope.

A cross-tower improvement violates those boundaries by design. It asks one supplier to spend effort whose benefit accrues to another, to the customer, or to an aggregate experience no contract names. Rational commercial behaviour is to decline, defer, or bill for it. Nothing in the operating model corrects this on its own, because the seam between contracts is exactly where no obligation has been written.

Where cross-tower improvements stall

Cross-tower improvements stall under predictable conditions. The first is a benefit that lands outside the tower bearing the cost, so the provider asked to act sees only expense. The second is ambiguous root cause, where an issue crosses domains and each party can reasonably attribute it elsewhere. The third is funding: an improvement that serves everyone is budgeted by no one, so it waits.

A fourth condition is measurement. When each tower reports against its own service levels and all report green, the end-to-end problem is invisible in governance. Without a single view of end-to-end performance and a single accountable party, the improvement has no sponsor and no home.

A shared mechanism the integrator owns

The service integrator — whether retained by the customer, delivered by an external party, or fulfilled through a lead supplier — exists to hold what the towers cannot.[1] Continual improvement is one such responsibility, and it needs an explicit mechanism rather than goodwill.

That mechanism starts with a single continual improvement register, owned by the integrator and spanning every tower.[2] Each entry records the opportunity, the towers involved, the expected end-to-end benefit, the estimated effort and, critically, the accountable owner. Prioritisation happens across the portfolio rather than within any one contract.

Governance gives the register force. The SIAM governance model already convenes providers through operational, tactical and strategic boards; improvement belongs on their agendas as a standing item with decision rights.[1] The integrator chairs, arbitrates ownership, and escalates the funding calls the towers cannot settle alone.

Incentive and contractual alignment make the mechanism durable. Contracts and schedules should oblige providers to join cross-tower improvement, contribute data, and share in outcome-based measures that reward the end-to-end result. Where a shared improvement needs funding, the model must name who pays — often the customer, who captures the aggregate benefit.

The behaviours that decide the outcome

Structure sets the conditions; behaviour decides the result. Suppliers who compete elsewhere must collaborate here, and they will do so only where the culture makes it safe. A blame culture, in which root-cause discussion becomes a contest to allocate fault, teaches providers to defend their boundaries and withhold information. Improvement dies in that climate, whatever the register's design.

The integrator sets the tone. Joint problem reviews framed around the end-to-end service, blameless investigation of cross-tower incidents, and visible recognition when providers act beyond their contracts build the trust that makes shared improvement routine. These are governance responsibilities, not soft extras.

Trust compounds. Each cross-tower problem solved without recrimination lowers the guard for the next, and providers begin to surface opportunities rather than conceal weaknesses. The integrator cannot mandate this, but it can design the forums, language and recognition that make collaboration rational for parties who owe one another nothing.

Left alone, a SIAM ecosystem optimises locally and stagnates overall: every tower green, the whole no better. The gaps between towers do not close themselves. End-to-end improvement needs an owner even when no supplier owns the end-to-end service, and only the integrator can be that owner.

That ownership is a design choice: a register the integrator controls, boards empowered to prioritise and fund across towers, contracts that reward collective outcomes, and a culture that treats a cross-tower fault as shared work rather than contested ground. The disciplines of continual improvement are not in doubt; whether anyone is accountable for applying them across the whole chain is the question SIAM leaders must answer.

References & Further Reading

[1] Scopism — Service Integration and Management (SIAM®) Foundation Body of Knowledge (the service integrator role — retained, external or lead-supplier; the operational, tactical and strategic governance boards). https://www.scopism.com/learn/siam-body-of-knowledge/

[2] AXELOS / PeopleCert — ITIL® 4 continual improvement practice and the improvement (CSI) register. https://www.peoplecert.org/browse-certifications/itil

[3] Scopism — Global SIAM Survey 2025 (integration cited as the leading challenge by 74% of 232 respondents across 34 countries). https://www.scopism.com/