Overlapping and Absent Accountability at Strategic and IT Layers

Research Question

What failure modes have been empirically observed in organisations where accountability is either overlapping, two or more parties hold the same accountability, or absent, no party owns a given area, at the strategic leadership level, the information technology (IT) delivery layer, or both simultaneously?

Findings

(Populated from §6 Synthesis above.)

Executive Summary

Organisations with overlapping or absent accountability at strategic and information technology (IT) layers reliably show slower decisions, unresolved risk, and lower realised value than their programme plans imply.

At the strategic layer, the recurring pattern is weak ownership of decision rights, benefit accountability, liability, and escalation authority.

At the delivery layer, the observed symptoms are unresolved issues, change-control churn, backlog growth, and delayed modernization because open decisions remain spread across business, supplier, and operations boundaries.

The strongest supported remedy is a clearly accountable owner for each consequential decision or outcome, together with documented cross-party roles and decision rights.

Key Findings

1. Where strategic accountability is overlapping or absent, organisations repeatedly lose decision speed and benefit ownership because no single senior actor can settle trade-offs across cost, scope, liability, and local implementation constraints.
2. At the information technology delivery layer, accountability failure appears as concrete operational symptoms such as delay notices, unresolved open issues, backlog growth, and modernization work that cannot close cleanly.
3. Shared-service and outsourced operating models are especially vulnerable because authority, contractual control, operational work, and consequences are split across organisations unless hand-offs and escalation rights are deliberately specified.
4. The most severe retrieved cases combine strategic-layer ambiguity with delivery-layer ambiguity alongside legacy-system complexity, contractual friction, or scope expansion, producing a coupled failure pattern in which programmes keep spending money while scope shrinks, liabilities stay unclear, and realised benefits lag far behind plan.
5. Finger-pointing and decision paralysis are structural consequences of duplicated authority or missing ownership, because each actor can rationally defer hard choices to another boundary.
6. The strongest evidenced intervention is explicit accountable ownership for each consequential decision or outcome, together with documented cross-party roles, transition responsibilities, and escalation paths.
7. Control Objectives for Information and Related Technologies and Team Topologies provide usable vocabularies for naming governance objectives, role boundaries, and team interfaces after accountable owners have been defined.

Assumptions

• The inaccessible Weill and Ross source is assumed to align materially with the accessible MIT Center for Information Systems Research decision-rights summary because both sit in the same research stream.
• Accessible primary studies directly isolating the effect of named responsibility matrices are assumed to be sparse relative to broader governance evidence because targeted searches did not yield extractable primary evidence in this session.

Analysis

The evidence weighs most heavily toward accountability defects as a coordination and control problem, not only a competence problem, because the strongest sources define governance in terms of decision rights and then document failure where those rights and responsibilities are fragmented.

Public inquiry and audit reports carry more weight than framework pages for the failure-mode claims because they document realised outcomes such as delay notices, backlog volume, scope reduction, and value-for-money deterioration.

The dual-layer severity judgment is inferential rather than experimentally measured, and it is kept at medium confidence because the largest retrieved failures combine unclear senior ownership with unclear delivery or transition ownership, leaving no stable path for corrective action.

The cited cases also surface alternative contributors, including legacy-system complexity, procurement and contract design, and programme-scope change, so accountability ambiguity is best treated as a recurring amplifier and coordination failure rather than the only causal factor.

Frameworks such as COBIT and Team Topologies are useful because they operationalise the remedy through governance objectives, role naming, and team-boundary design once accountable owners have been defined for the decisions that matter.

Risks, Gaps, and Uncertainties

• The strongest cases are large public-sector programmes and shared services, so transfer to smaller product firms or less regulated environments requires caution.
• The evidence base is better at showing recurring symptoms and governance principles than at quantifying the exact marginal effect of each structural remedy.

Open Questions

• How often do private-sector platform teams or internal shared services show the same failure pattern when product management, operations, and architecture ownership are split?
• What lightweight ownership registry or service-catalog practices most reliably prevent re-emergence of accountability gaps after a reorganisation?
• Under what conditions does extra redundancy in accountability improve resilience rather than create paralysis?

sources

• [ ] Weill and Ross (2004) IT Governance: How Top Performers Manage IT Decision Rights for Superior Results
• [x] Massachusetts Institute of Technology (MIT) Center for Information Systems Research (n.d.) Classic Topics: Decision Rights
• [x] Information Systems Audit and Control Association (ISACA) Control Objectives for Information and Related Technologies (COBIT) resource page
• [x] Skelton and Pais (2025) Team Topologies book page
• [x] Ako-Nai and Singh (2019) Information technology governance framework for improving organisational performance
• [x] Queensland Parliament (2013) The Queensland Health Payroll System - Commission of Inquiry
• [x] National Audit Office (2011) The National Programme for information technology (IT) in the National Health Service: an update on the delivery of detailed care records systems
• [x] National Audit Office (2011) The National Programme for information technology (IT) in the National Health Service: an update on the delivery of detailed care records systems, full report Portable Document Format (PDF)
• [x] Government Accountability Office (2025) Agencies Need to Plan for Modernizing Critical Decades-Old Legacy Systems
• [x] Auditor General of Canada (2026) Modernizing the Pay System
• [x] Treasury Board of Canada Secretariat (n.d.) Lessons Learned from the Transformation of Pay Administration Initiative