"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.
- Orphan interfaces. Flows between lots belong to no one: every defect turns into a debate about where it came from.
- A lead partner who is judge and party. The prime contractor steers the consortium, and its own commercial interests too.
- 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:
- Consulting vs integration: separate strategy and steering from execution.
- The art of the RFP: proof before promise.
- Independent testing & PMO: the shields of your budget.
- Licenses & contracts: the hidden price of Day 1.
- Large consortiums: one conductor.
The series "Selecting and choosing IT solutions"
Digital transformation: insights on selecting and choosing IT solutionsEpisode 1
Consulting vs integration: why handing governance to your integrator is a strategic mistakeEpisode 2
The art of the RFP: proof before promiseEpisode 3
Independent testing & PMO: the shields of your budgetEpisode 4
Licenses & contracts: the hidden price of Day 1Episode 5
Large consortiums: one conductor
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
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.