Governance structures that support investment in delivery capability without…

Research Question

Under what governance conditions can investment in building durable delivery capability be made reliably without placing risk, cost, and benefits accountability under one owner, and what minimum authority grant is required for an accountable office to function as an integrator without structural reorganisation?

Findings

(Populated from §6 Synthesis above.)

Executive Summary

Investment in delivery capability can be governed reliably without putting risk, cost, and benefits under one owner only when the organisation substitutes structural co-location with an explicit authority bundle: one named first-line integrator owns the business case, prioritisation, and benefits reporting, while independent risk retains challenge and escalation rights.

The minimum viable authority grant is not full risk ownership but enough formal power to gate or recommend allocation within an approved funding envelope, require outcome reporting, convene binding cross-functional review, and stop or escalate conflicting demands that would displace protected delivery-capability investment.

Milestone-based central funding can strengthen this design by tying capital release to progress and measurable return.

Named accountability documents and escalation rights still need to come from the governance layer rather than from the funding mechanism itself.

If the central office lacks budget leverage and explicit escalation rights, it remains a coordinator and is likely to reproduce the same missing-integrator and queue-fragmentation failures already observed in adjacent completed items.

Key Findings

1. Banking-governance rules allow business-line delivery ownership and independent risk ownership to remain separate, but they require clear responsibilities, direct challenge paths, and management-body oversight so that no material trade-off is left ownerless.
2. Decision-rights research shows that any substitute for structural co-location must assign named owners for prioritisation of spend, choice of what versus how, and exception handling.
3. The Senior Managers and Certification Regime shows one concrete way a separated structure can document answerability, because it requires named responsibility documents and responsibility maps for senior-manager roles.
4. Product and value-stream funding models reduce the cost-benefit split only when standing teams receive stable funding and backlog authority inside an approved envelope while central governance retains strategic reallocation rights at regular review points.
5. Milestone-based central funding can enforce measurable progress and capital discipline when strong central investment governance exists, and this mechanism can partially substitute for structural co-location while still requiring a named owner for milestones and repayment conditions.
6. The best-supported integrator bundle in this evidence base includes budget-gating or budget-recommendation rights, a benefits-reporting mandate, mandatory convening of finance and risk for binding review, and veto or escalation rights when other demands would consume protected delivery-capability capacity.
7. The integrator office does not need to own independent risk sign-off itself, because regulated-governance sources keep second-line challenge separate; the key requirement is guaranteed participation and escalation so that risk objections cannot be bypassed.
8. If the central office lacks budget leverage and documented decision rights, it remains only a coordinator and is likely to reproduce the same missing-integrator, queue-fragmentation, and cost-shifting failures already identified in adjacent completed repository items.

Assumptions

• Assumption: "Investment in delivery capability" means durable product, platform, backlog, and technical-capability investment rather than one-off project spend. Justification: The consulted product-funding literature consistently distinguishes standing-team and lifecycle investment from fixed-scope project funding.
• Assumption: The minimum authority bundle is synthesised from regulatory-governance principles plus cross-sector product-funding evidence because public regulated-bank documents rarely expose the exact internal committee charters used to arbitrate product-funding conflicts. Justification: Accessible financial-services sources in this session were strong on governance principles and weaker on internal portfolio-operating detail.

Analysis

The evidence weighs against a simple choice between total co-location and hopeless fragmentation.

The stronger distinction is between separated structures with explicit closure rights and separated structures with only consultative coordination.

Banking-governance sources are especially valuable because they show that regulated firms already accept structural separation between first-line delivery and second-line risk, but only when the accountability map and escalation architecture are concrete.

Product-funding and milestone-funding sources add the missing investment-governance mechanics: standing-team envelopes, periodic portfolio reallocation, outcome tracking, and staged capital release.

The strongest supported recommendation is to give one office enough first-line investment authority and enough cross-functional escalation leverage that risk, cost, and benefit trade-offs cannot remain unresolved.

Risks, Gaps, and Uncertainties

The empirical evidence on product-funding mechanics is stronger in cross-sector transformation literature than in public regulated-bank case studies, so the funding portion of the conclusion remains medium rather than high confidence.

Regulatory sources define governance principles and control-function independence clearly, but they do not specify the exact portfolio-veto thresholds or capacity-protection rules an integrating office should use in practice.

The inaccessible full text of Weill and Ross and the unparsed seeded PS18/14 PDF did not block the conclusion because accessible official replacements covered the accountability and decision-rights requirements used in the synthesis, but direct quotation from those seeded sources remains unavailable in this session.

Open Questions

What quantitative threshold should trigger the integrator office's veto or mandatory escalation when live-operating demand begins to erode protected delivery-capability investment?

In regulated banks, which committee structure best resolves conflicts between independent risk objections and product-value arguments when both sides have formally valid grounds?

sources

Starting points - papers, articles, videos, repos, docs. Every source must include a URL. Use the display name formats below - they feed the Author (Year) citation labels shown on the generated site:

• [Smith et al. (YYYY) Title of paper](Organisation Title - for papers with named authors

• [Organisation Title](Organisation Title - for documentation, standards, or pages without a named author

• [x] MIT Center for Information Systems Research (MIT CISR) (n.d.) Classic Topics: Decision Rights - consulted for the governance baseline that defines 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 practical decision categories that matter most in digital transformation.

• [ ] Weill and Ross (2004) IT Governance: How Top Performers Manage IT Decision Rights for Superior Results - seeded primary source checked; the accessible page was retrieved but the full primary text was not available in this session.

• [x] Basel Committee on Banking Supervision (BCBS) (2015) Corporate governance principles for banks - consulted for board responsibility, three lines of defence, and separation of business-line and risk-function duties.

• [ ] Financial Conduct Authority (FCA) (2018) Optimising the Senior Managers and Certification Regime and feedback to CP17/25 (PS18/14) - seeded policy Portable Document Format (PDF) checked; accessible official replacement sources below were used for the operative accountability-documentation requirements.

• [x] Financial Conduct Authority (FCA) (n.d.) Senior Managers and Certification Regime - consulted for the regime purpose and the requirement that firms can show who does what.

• [x] Financial Conduct Authority (FCA) (2019) FG19/2 Senior Managers and Certification Regime: Guidance on statements of responsibilities and Responsibilities Maps for FCA firms - consulted for named-accountability documents and responsibility maps.

• [x] European Banking Authority (EBA) (2021) Guidelines on internal governance under Capital Requirements Directive (CRD) - consulted as the current official guidance page replacing the moved seeded URL.

• [x] European Banking Authority (EBA) (2021) Final report on Guidelines on internal governance under Capital Requirements Directive (CRD) - consulted for management-body responsibility, lines of responsibility, and risk-function independence.

• [x] Kersten (2018) Project to Product - consulted for the project-to-product framing used as background context on product-oriented investment.

• [x] Scaled Agile, Inc. (n.d.) Lean Budgets - consulted as a secondary description of funding long-lived flows of value, sometimes called value-stream funding, inside approved budget envelopes.

• [x] Thoughtworks (2025) Funding agility: Moving beyond project budgets - consulted for stable base investment, quarterly governance, and product-owner authority within approved funding.

• [x] Boyd and Miller (2021) Creating a new funding model for product-based Information Technology (IT) - consulted for perpetual funding, lifecycle accountability, and quarterly or annual reallocation logic.

• [x] Technology Modernization Fund (TMF) (n.d.) Homepage - consulted for milestone-based unlocks, measurable return on investment, and repayment flexibility.

• [x] Technology Modernization Fund (TMF) (n.d.) Board - consulted for the board's investment and performance-monitoring role.

• [x] Fiscal Service (2023) Technology Modernization Fund accounting guide - consulted for the incremental-funding and repayment mechanics attached to TMF milestones.

• [x] Research item (2026) Organisational failure modes: risk, operational cost, and benefits accountability in separate business units - consulted as the precursor evidence on the missing-integrator problem.

• [x] Research item (2026) Organisational failure modes: overlapping and absent accountability at strategic and Information Technology (IT) layers - consulted as adjacent evidence on missing or duplicated decision owners.

• [x] Research item (2026) Organisational failure modes: project-based demand with product-based Information Technology (IT) teams - consulted as adjacent evidence on the consequences of separating funding logic from persistent delivery ownership.