Funding authority and delivery-risk accountability split

Research Question

What governance and commercial structures best preserve delivery velocity, delivered quality, delivered risk control, delivery cost, and total cost of ownership when funding authority sits with a party that lacks delivery capability while delivery and operational risk accountability sit with a separate party that has delivery capability but no funding authority?

Findings

Executive Summary

The strongest supported structure is a product or service-aligned delivery team that holds routine delivery and operating authority together with a defined delivery budget, while a small central integrator retains portfolio-allocation and exception rights instead of approving every change.

When funding authority remains external and committee-heavy, delivery speed, reliability, and total cost of ownership usually worsen because the team carrying operational risk cannot close trade-offs about scope, reliability, technical debt, and spend in real time.

The evidence points away from abolishing central governance and toward relocating it, so that central actors own guardrails, portfolio pacing, and escalation while delivery-capable teams own routine engineering, service, and cost decisions inside those guardrails.

Key Findings

1. When funding authority, prioritisation, and exception handling are separated from the team that carries delivery and operational risk, delivery usually slows because decisions queue in external forums that modern DevOps guidance and recent government reviews both describe as poorly suited to flexible digital work.
2. Delivered quality and operational risk control weaken when the accountable operator cannot directly fund reliability work, because service-level trade-offs, incident readiness, and technical-debt reduction then depend on a budget holder who does not experience the operational consequences first-hand.
3. Total cost of ownership increases under split-authority models when cost accountability is detached from engineering decisions, because the teams that determine architecture and usage patterns do not control enough of the operating budget to optimize spend continuously.
4. Milestone-based and outcome-aware funding releases are one credible way to keep central investment control while allowing delivery-capable teams to learn, adapt scope, and draw money incrementally as measurable progress is demonstrated.
5. The strongest supported substitute for full structural co-location is a named integrator with explicit authority over portfolio allocation, exception handling, and escalation, combined with a named accountable contact inside each participating unit that can turn central decisions into local action quickly.
6. Commercial arrangements should budget for both build and run costs and permit changing scope, because rigid capital-heavy or specification-heavy models systematically underfund the ongoing maintenance, resilience, and integration work that determines long-run service performance.
7. Split-authority governance becomes counterproductive when control intensity exceeds the actual risk profile and reversibility of the work, because the result is queueing, proxy compliance, and escalation traffic rather than materially better risk reduction or faster learning.
8. A well-supported operating pattern combines delegated delivery authority, central guardrails, shared outcome metrics, and central review focused on exceptional or higher-risk cases, which keeps central review off routine local technical and operational choices.

Assumptions

• Assumption: The delivery-capable party is also the party best placed to optimize a meaningful share of operating cost. Justification: Architecture, service-level, and reliability choices drive a large share of ongoing spend.
• Assumption: Public-sector digital-governance evidence is structurally informative for enterprise delivery-governance design. Justification: The reviewed government sources explicitly document the same separation between budget holders, central controls, and accountable delivery teams that the present item studies.
• Assumption: Ring-fenced delivery envelopes can exist inside centrally controlled funding structures. Justification: The reviewed funding and governance models show central investment control coexisting with delegated execution and milestone-based release.

Analysis

The evidence is strongest on decision-right placement rather than on abstract calls for collaboration, because the most concrete sources all specify who should decide routine change, cost, investment, and exception questions.

Speed, quality, risk, cost, and total cost of ownership are linked in this problem rather than separable, because the same misplaced authority determines whether those trade-offs are closed locally by the accountable team or escalated outward into queueing and delay.

The most credible commercial compromise is staged delegation rather than full centralization or full decentralization, because central funders still need portfolio pacing and visible control while delivery-capable teams need enough budgetary and operational discretion to learn without re-opening the whole business case every time.

The adjacent repository items sharpen the boundary condition rather than changing the answer: explicit integrator rights can work, but only when they are backed by real authority, measurable service outcomes, and proportionate review instead of another committee layer.

Risks, Gaps, and Uncertainties

• The public evidence base is stronger on mechanisms and operating-model patterns than on direct comparative studies that isolate this exact funding-versus-delivery split from all other organisational variables.
• Two seeded foundational sources, Jensen and Meckling's original article and the full Accelerate book text, were not directly accessible in this session, so their influence appears only through accessible official or repository-adjacent sources.
• Government evidence is highly relevant to split authority, but some public-finance and legacy constraints may overstate how severe the same problem is in firms with simpler capital-allocation paths.

Open Questions

• How far can delegated budget envelopes be pushed in heavily regulated sectors before legal or prudential constraints require a different authority pattern?
• Which service-level metric bundle best predicts when review focused on exceptional or higher-risk cases should tighten back into pre-execution review?
• What contractual clauses most effectively tie supplier incentives to long-run service reliability instead of short-run milestone completion?

sources

• [ ] Jensen and Meckling (1976) Theory of the Firm: Managerial Behavior, Agency Costs and Ownership Structure - seeded source checked; the Social Science Research Network (SSRN) page returned 403 in this session, so downstream claims use accessible governance and audit sources instead of this blocked landing page.
• [ ] Forsgren, Humble, and Kim (2018) Accelerate: The Science of Lean Software and DevOps - seeded source checked; the product page is accessible, but downstream claims rely on the public Google Cloud DevOps and DevOps Research and Assessment (DORA) pages that expose the relevant findings directly.
• [x] Google Site Reliability Engineering Book - consulted as the canonical book entry for operational ownership and risk trade-offs.
• [x] Google Site Reliability Engineering Book: Embracing Risk - consulted for the direct risk, speed, and cost trade-off framing.
• [x] Google Site Reliability Engineering Book: Service Level Objectives - consulted for the metric and accountability framing for service outcomes.
• [x] Google Cloud Architecture Center DevOps capabilities - consulted for the explicit guidance to replace heavyweight change approval with peer review.
• [x] Google Cloud (2024) Announcing the 2024 DORA report - consulted for the current DORA framing on software delivery performance and developer workflow.
• [x] MIT Center for Information Systems Research (MIT CISR) Classic Topics: Decision Rights - consulted for the definition of governance as the allocation of decision rights and accountabilities.
• [x] MIT Center for Information Systems Research (MIT CISR) (2023) Simplifying decision rights for growth - consulted for the key decision-right categories, especially investment prioritisation and exception handling.
• [x] FinOps Foundation Framework Overview - consulted for the FinOps operating-model baseline.
• [x] FinOps Foundation Principles - consulted for decentralized cost accountability and central enablement.
• [x] FinOps Foundation Personas - consulted for the required cross-functional collaboration between engineering, finance, and service-management roles.
• [x] National Audit Office (2023) Digital transformation in government: addressing the barriers - consulted for systemic delivery barriers, capability constraints, and central-versus-department governance issues.
• [x] National Audit Office (2021) Six reasons why digital transformation is still a problem for government - consulted for flexible contracting, governance, coordination, and funding lessons.
• [x] Government of the United Kingdom (2025) State of digital government review - consulted for evidence on funding-model mismatch, fragmented delivery, legacy burden, and role-mix imbalance.
• [x] Technology Modernization Fund Homepage - consulted for milestone-based funding release and return-on-investment gating.
• [x] Technology Modernization Fund Board - consulted for the board's investment-evaluation and performance-monitoring role.
• [x] United States Shared Services Management Governance ecosystem - consulted for the explicit escalation, coordination, and accountable-point-of-contact model.
• [x] Mitchell (2026) Organisational failure modes: risk, operational cost, and benefits accountability in separate business units - consulted as the closest prior repository item on the missing-integrator failure mode.
• [x] Mitchell (2026) Governance structures that support investment in delivery capability without one owner for risk, cost, and benefits - consulted for the earlier synthesis on minimum authority bundles.
• [x] Mitchell (2026) Governance designs where explicit integrator rights substitute for co-location of risk, cost, and benefits - consulted for the conditions under which explicit integrator rights work.
• [x] Mitchell (2026) Conditions under which internal governance controls minimise coordination costs in regulated enterprises - consulted for the proportionality and ownership qualifier.