R-ST-02 Organisational & Structural DAMAGE 3.3 / High

Coordination Tax Collapse

AI handles execution and coordination overhead evaporates faster than governance can adapt. Informal coordination mechanisms disappear before formal replacements exist.

The Risk

Organizations rely on informal coordination mechanisms that are not documented in process manuals. A team member knows which stakeholders need to be consulted before making a decision. A manager understands which teams' priorities are aligned and which are in tension, and can navigate that political landscape. A subject matter expert knows which rules are actually enforced and which are routinely waived. These informal mechanisms are the "coordination tax": the overhead that enables the organization to function coherently.

When agents handle execution, this coordination tax is often eliminated. The agent does not need to consult stakeholders because the agent's authority has been explicitly delegated. The agent does not need to navigate political tensions because the agent has been programmed with decision rules. The agent does not need to know which rules are waived because the agent follows formal rules.

The problem is timing: agents can eliminate coordination tax faster than organizations can build formal replacements. As informal coordination mechanisms disappear, no formal governance structure has been designed to replace them. The organization loses the ability to navigate exceptions, manage competing priorities, and maintain coherence.

How It Materializes

A healthcare system implements an agentic system for clinical protocol adherence, designed to ensure that clinicians follow evidence-based guidelines. The system monitors physician orders and alerts physicians when orders deviate from approved protocols.

In practice, experienced physicians often deviate from standard protocols based on clinical judgment. A patient with a standard diagnosis may have unusual comorbidities that make the standard protocol contraindicated. The physician deviates from protocol based on clinical judgment, coordinates with specialists through informal conversations, and documents the deviation in the patient chart.

The agentic system, unaware of these informal coordination mechanisms, flags every deviation as a protocol violation. Initially, physicians work around the system. They document their deviations more carefully, or they contact system administrators to override the alerts.

As the system is used at scale, the informal coordination becomes impossible. There are thousands of physicians and hundreds of deviations per day. System administrators cannot manually review every deviation. Formal governance structures for protocol deviations do not exist.

Two negative outcomes occur. First, physicians begin to ignore the system: if alerts are constantly overridden informally, they lose their signaling value. Second, governance breaks down: the organization loses track of which deviations are happening, why, and which are actually justified. A patient is harmed due to a protocol deviation that was clinically appropriate but poorly documented. The healthcare system cannot defend the deviation because its formal governance system does not account for protocol exceptions.

DAMAGE Score Breakdown

Dimension Score Rationale
D - Detectability 4 Coordination tax collapse is not immediately visible. The organization continues to operate initially because informal mechanisms are resilient. Collapse becomes apparent when exceptions overwhelm the system.
A - Autonomy Sensitivity 5 Coordination tax collapse is most severe for autonomous agents that have no human oversight. Agents cannot adapt when informal coordination mechanisms break down.
M - Multiplicative Potential 4 Coordination tax collapse compounds as the agent's scope expands and the number of coordination exceptions increases.
A - Attack Surface 3 Coordination tax collapse is not typically a direct security vulnerability. However, breakdown of coordination can be exploited by adversaries who understand that informal mechanisms have been eliminated.
G - Governance Gap 5 Most organizations have not explicitly mapped informal coordination mechanisms. When these mechanisms are eliminated, formal governance structures do not exist to replace them.
E - Enterprise Impact 4 Coordination tax collapse can trigger operational failures, compliance failures, and clinical or financial harms depending on domain.
Composite DAMAGE Score 3.3 High. Requires proactive governance design before agent deployment.

Agent Impact Profile

How severity changes across the agent architecture spectrum.

Agent Type Impact How This Risk Manifests
Digital Assistant Low DA works with humans who maintain informal coordination. The human retains awareness of stakeholder relationships and coordination needs.
Digital Apprentice Low AP is supervised by humans who maintain awareness of coordination needs.
Autonomous Agent Critical AA operates independently and cannot maintain the informal coordination that humans were performing. Coordination collapse is severe.
Delegating Agent High DL invokes tools and APIs. If informal coordination between the agent and tools is required, that coordination may be eliminated.
Agent Crew / Pipeline Critical CR chains multiple agents. Informal coordination between agents in the pipeline may break down as agents operate at scale.
Agent Mesh / Swarm Critical MS features dynamic peer-to-peer delegation. Informal coordination mechanisms that enable agents to cooperate are likely to break down as the mesh scales.

Regulatory Framework Mapping

Framework Coverage Citation What It Addresses What It Misses
NIST AI RMF 1.0 Minimal N/A Framework-level governance; does not address organizational coordination. No guidance on identifying or preserving informal coordination.
MAS AIRG Partial Section 4 (Accountability and Governance) Requires clear governance and decision-making authority. Does not warn against eliminating informal mechanisms.
DORA Minimal N/A Digital operational resilience focus. No guidance on preserving coordination in automated systems.
ISO 42001 Partial Section 6 (AI management system context) Requires documented governance. Does not mandate documentation or preservation of informal mechanisms.
OCC Guidance Minimal N/A Operational risk focus. No guidance on managing coordination in automated systems.

Why This Matters in Regulated Industries

In banking, credit approval relies on coordination between loan officers, credit analysts, compliance, and executives. Much of this coordination is informal: an experienced loan officer knows which transactions require higher-level review without explicit rules. When agents automate loan approval, the informal coordination is lost. Formal governance must account for this, but often does not.

In healthcare, clinical decision-making relies on coordination between physicians, specialists, nurses, and pharmacists. Much of this coordination is informal: a physician knows which specialists need to be consulted, which test results require immediate action, which drug interactions demand attention. When agents automate clinical recommendations, the informal coordination is lost.

In insurance, underwriting relies on coordination between underwriters, actuaries, legal, and claims. Informal coordination mechanisms help navigate the tension between growth and risk management. When agents automate underwriting, these informal coordination mechanisms are eliminated.

Controls & Mitigations

Design-Time Controls

  • Implement coordination mapping that explicitly documents informal coordination mechanisms before agents are deployed. Interview subject matter experts to identify stakeholder consultations, political tensions, and flexible rules.
  • Design a formal governance layer that replaces informal coordination mechanisms with explicit decision authority, escalation paths, and exception handling.
  • Establish coordination points in agent workflows where agents are required to consult with or route decisions to humans for coordination review.
  • Implement exception handling as a first-class feature: design systems that can capture, track, and manage exceptions to normal agent decision-making.

Runtime Controls

  • Deploy coordination monitoring that tracks informal coordination still occurring outside the agent system. Log this and use it to improve the formal governance layer.
  • Implement escalation tracking that monitors when decisions are escalated to humans for coordination or approval. High escalation frequency indicates that informal coordination is still necessary but not formalized.
  • Establish feedback loops from field teams to the agent deployment team to flag coordination breakdowns.
  • Use the JIT Authorization Broker to implement formal coordination checkpoints at decision boundaries.

Detection & Response

  • Conduct coordination health audits that assess whether the organization maintains adequate coordination for the agent's scope. Interview stakeholders about consultation, visibility, and exception handling.
  • Implement process integrity monitoring that detects when informal coordination mechanisms are being used to work around formal systems.
  • Establish post-incident review processes for coordination failures to identify which informal mechanism was eliminated and how formal governance can replace it.
  • Create a coordination case library documenting coordination scenarios the system must handle.

Related Risks

Address This Risk in Your Institution

Coordination Tax Collapse requires formal governance design that replaces informal mechanisms before they disappear. Our advisory engagements are purpose-built for banks, insurers, and financial institutions subject to prudential oversight.

Schedule a Briefing