Client-side series · Episode 5

Large consortiums: one conductor

Orphan interfaces, a lead partner who is both judge and party, siloed governance: how to drive shared accountability across a multi-party ecosystem.

By Fakhri Essedik · · 2 min read

"Software vendor, integrator, hosting provider, telecom operator: each one masters its own lot. But incidents arise at the interfaces, where no contract names an owner."

The issue: jointly responsible, so no one is?

Large programs are no longer delivered by a single supplier. The more parties involved, the more gray zones appear between their scopes.

Seen from the other side. In a consortium, each member protects its own scope and margin first. The client is left to arbitrate conflicts alone.

The 3 frictions of a consortium: where projects seize up

Three gray zones that turn a partnership into a blame game.

  1. Orphan interfaces. Flows between lots belong to no one: every defect turns into a debate about where it came from.
  2. A lead partner who is judge and party. The prime contractor steers the consortium, and its own commercial interests too.
  3. Siloed governance. One committee per lot, no end-to-end view: delays surface at integration.

The method: end-to-end governance

Four levers to turn joint responsibility into shared accountability.

Contractual RACI: every interface has an owner

A RACI matrix annexed to the contracts, including for flows between lots.

Integration: a designated assembler

A single owner of integration and end-to-end testing, appointed from the start.

Governance: one committee, client-side

All parties at the same table, with a neutral PMO keeping the dashboard.

Commitments: end-to-end SLAs

Shared indicators and joint-liability clauses: the client does not pay for the blame game.

The decision-maker's reflex: one ecosystem, one conductor

In a consortium, technology rarely drifts on its own: the interfaces between parties do. Who in your organization owns what happens between the lots?

The series at a glance

This episode closes the series. Over five episodes, it covered the full cycle of an IT choice, from the client side:

  1. Consulting vs integration: separate strategy and steering from execution.
  2. The art of the RFP: proof before promise.
  3. Independent testing & PMO: the shields of your budget.
  4. Licenses & contracts: the hidden price of Day 1.
  5. Large consortiums: one conductor.
Related offer

Program Management & Recovery

Executive steering of complex programs, PMO, recovery of troubled IT projects and IS modernization.

IT vendor selection, IT governance & program managementHow we help companies and institutions, from choosing a solution to going live.
Fakhri Essedik

Fakhri Essedik

Founder of EDX Advisory

For more than 25 years, Fakhri Essedik has helped executive teams and CIOs steer major Digital, Data & AI programs across Europe, Africa and the Middle East.

Learn more → | Follow on LinkedIn

A project to secure, a next stage to reach?

Let's spend 30 minutes on your situation, in full confidence.