Governance designs where explicit integrator rights substitute for co-location…

Research Question

Under which governance designs do explicit integrator rights fully substitute for structural co-location of risk, cost, and benefits, and under which conditions do these designs fail?

Findings

Executive Summary

Explicit integrator rights fully substitute for structural co-location only when governance gives one cross-unit decider enforceable authority over prioritisation and exceptions, direct enough information to judge execution, and consequence mechanisms through budget, standards, or escalation. Shared-services boards and platform-governance models come closest to satisfying that condition because they formalise provider-user interfaces, performance metrics, reusable standards, and dispute-resolution paths. Rights weaken when the integrator cannot move resources, when affected units still optimise for local incentives, or when visibility is mediated through external providers rather than direct telemetry. Standardisation, change-management quality, and stakeholder support still matter, but the strongest reading of the shared-services and platform evidence is that those complements make formal rights usable rather than replacing the need for named authority and escalation. The best-supported boundary condition is therefore that rights-based substitution works for bounded, recurring coordination problems with explicit service interfaces and exception routes, but it does not fully replace structural co-location for opaque, delayed, or politically contested cost-benefit-risk trade-offs.

Key Findings

1. Explicit integrator rights only become a true substitute for structural co-location when one named decision owner can resolve what-versus-how, investment-prioritisation, and exception trade-offs without committee ambiguity or diffuse veto power.
2. Rights-based substitution also requires governing-body accountability, delegated resources, and transparent reporting, because authoritative governance sources treat rights as operable only inside a broader system of checks, balances, and independent assurance.
3. Shared-services governance can substitute for structural co-location when a neutral board or equivalent body links provider and user through metrics, benchmarks, investment review, and escalation, making recurring cross-unit disputes governable without a reorganisation.
4. Platform-governance regimes substitute successfully when central teams own reusable standards and preapproved blueprints while local delivery teams retain execution authority, but they fail when the platform team becomes a reactive bottleneck or imposes tools without consultation.
5. Vendor-mediated or outsourced governance supports full substitution only when contracts recreate direct enough access, audit, monitoring, termination, and exit rights to approximate the visibility that internal governance gets from direct operational control.
6. Rights fail in practice when the nominal integrator cannot shift funding, enforce standards, or trigger consequences, because local units then keep optimising for their own incentives while the integrator remains a coordinator without real leverage.
7. The strongest evidence therefore supports full substitution only for bounded and repeatable coordination problems with explicit interfaces, while delayed-benefit capability investments and opaque multi-party trade-offs still favour structural co-location or a materially stronger authority bundle.

Assumptions

• Explicit integrator rights are treated as the combined authority to prioritise, recommend investment, handle exceptions, and escalate unresolved trade-offs, even though different sources distribute those actions across different named roles.
• Shared services and platform governance are treated as comparable substitute cases because both intentionally separate central standards from local execution and therefore expose the same coordination problem in a repeatable form.
• Contract rights in outsourced settings are treated as a functional substitute for direct control only to the extent that they recreate comparable visibility, challenge, and exit surfaces.

Analysis

The evidence weighs most strongly toward governance patterns that make the integrator's authority concrete at the decision point rather than symbolic at the committee level. Shared services provide the clearest substitution case because they formalise provider-user separation and then add boards, metrics, funding advice, and escalation to make that separation governable. Platform governance reaches a similar result, but only when the central team limits itself to standards, reusable products, and exception frameworks rather than reclaiming every downstream execution decision. A plausible rival explanation is that the strongest shared-services and platform cases succeed mainly because they standardise interfaces, invest in change management, and concentrate stakeholder support, not because of the rights bundle itself. The evidence best fits a complementary reading rather than a rival one, because the same sources still treat clear governance structure, named responsibilities, and explicit exception paths as the mechanisms that make standardisation and change-management effort durable. The outsourced case is materially weaker because even strong contracts recreate visibility imperfectly, and the underlying economic and informational surfaces remain mediated by the provider. That pattern explains why explicit rights are a credible substitute for recurring service-governance interfaces but a weaker substitute for delayed, investment-heavy, or politically contested trade-offs where only structural co-location or a much stronger authority bundle can reliably align incentives.

Risks, Gaps, and Uncertainties

• The shared-services evidence base is rich on governance mechanics and failure patterns but light on matched quantitative outcome comparisons against structurally co-located alternatives.
• Regulatory outsourcing guidance is strong on required rights and safeguards, but it does not quantify how often those rights fully overcome information asymmetry in practice.
• Platform-governance sources are operationally useful but still rely partly on practitioner guidance rather than controlled comparative studies.
• The final boundary condition is therefore well supported directionally, but not by a single cross-sector dataset that ranks substitution strength across all governance regimes.

Open Questions

• Which observable metrics best distinguish a real integrator from a coordinator without leverage before a governance failure becomes visible?
• How often do shared-services customer councils or equivalent boards actually overrule large internal customers, and what escalation design makes that credible?
• Which contract clauses most reliably recreate operational visibility in vendor-mediated automation without excessive monitoring cost?
• Are there published enterprise cases where explicit integrator rights outperformed structural co-location on long-horizon capability investment rather than recurring service delivery?

sources

• [ ] Institute of Internal Auditors (IIA) (2020) Three Lines Model landing page - seeded landing page retained for provenance; the consulted source is the official Portable Document Format (PDF) below.
• [x] Institute of Internal Auditors (IIA) (2020) The IIA's Three Lines Model - governance accountability, management delegation, independent assurance, and alignment requirements.
• [ ] Organisation for Economic Co-operation and Development (OECD) (2023) Principles of Corporate Governance landing page - seeded landing page retained for provenance; the consulted source is the official OECD Legal Instruments PDF below.
• [x] Organisation for Economic Co-operation and Development (OECD) (2025) Recommendation of the Council on Principles of Corporate Governance - governance relationships, information, incentives, and accountability within checks and balances.
• [x] ISACA (n.d.) COBIT resources - high-level evidence that COBIT treats governance over information and technology as a configurable enterprise system.
• [ ] Harvard Business Review (2006) Who Has the D? How Clear Decision Roles Enhance Organizational Performance - seeded preview checked; downstream role-definition claims rely on Bain's accessible pages below.
• [x] Bain & Company (n.d.) Recommend, Agree, Perform, Input, Decide (RAPID) Decision Making Framework - role definitions for Recommend, Agree, Perform, Input, and Decide.
• [x] Bain & Company (2011) Decisions: Who does what? - single-decision-owner design, narrow veto roles, and cross-unit trade-off example.
• [x] Massachusetts Institute of Technology Center for Information Systems Research (MIT CISR) (n.d.) Classic Topics: Decision Rights - governance as the allocation of decision rights and accountabilities.
• [x] Massachusetts Institute of Technology Center for Information Systems Research (MIT CISR) (2023) Simplifying decision rights for growth - core decision categories: what versus how, investment prioritisation, and exception handling.
• [x] Basel Committee on Banking Supervision (BCBS) (2015) Corporate governance principles for banks - board accountability, independent risk challenge, and line-of-defence separation.
• [x] European Banking Authority (EBA) (2019) Guidelines on outsourcing arrangements - management responsibility, audit rights, monitoring, termination rights, and exit strategies for outsourced functions.
• [x] Burns and Yeaton (2008) Success Factors for Implementing Shared Services in Government - governance structure, stakeholder support, metrics, and failure patterns in shared services.
• [x] United States General Services Administration (2026) Governance ecosystem - shared-services governance roles, escalation paths, and senior accountable points of contact.
• [x] United States General Services Administration (2024) Shared Services Governance Board Charter - cross-functional governance board responsibilities, investment-plan review, funding advice, and adjudication rights.
• [x] Team Topologies (2026) Key concepts - platform teams as internal products and X-as-a-Service boundaries.
• [x] Team Topologies (2024) Revisiting Team Topologies: Misuses of Platform Teams - consultation failures, firefighting mode, and siloed platform-team failure modes.
• [x] Amazon Web Services (AWS) (2025) Empower your teams with modern architecture governance - preapproved blueprints, distributed governance, automated controls, and exception-path design.
• [x] Deloitte (2024) Shift from back office to center office - cross-functional service delivery and shared capability provision across silos.
• [x] Mitchell (2026) Governance structures that support investment in delivery capability without one owner for risk, cost, and benefits - prior completed item on the authority bundle needed when accountability is not co-located.
• [x] Mitchell (2026) Visibility and exit outcomes: vendor-supplied versus internally governed temporary operational automation - prior completed item on direct telemetry versus contract-right substitutes for visibility and exit.