← Back to Taxonomy
FM-07 · Failure Mode

Coordination Decay (aka Orphaned Work)

Tier: Foundational (Tier 1)
Severity: Systemic
Detectability: Low

Definition

Work spans multiple teams, systems, or functions, but no single role owns end-to-end outcomes. Handoffs multiply. Accountability fragments. Progress depends on informal follow-ups rather than explicit coordination mechanisms.

The system still moves, but only because individuals push work across boundaries manually. Delays, rework, and dropped tasks accumulate invisibly between teams. Failures appear intermittent and situational rather than systemic.

What Fails

End-to-end ownership of work that spans teams, systems, or functions. Tasks move locally but stall globally. No one is accountable for outcomes across handoffs.

Why It Emerges

Organizations scale by specialization without redesigning coordination mechanisms. Work is decomposed faster than ownership models evolve. Coordination is assumed to be a social skill instead of an architectural requirement.

How It Hides

  • Work appears "in progress" everywhere
  • Individual teams report success locally
  • Delays occur between systems, not within them
  • Failures manifest as timing issues, not errors
  • Progress depends on informal follow-ups

The gaps live between dashboards.

What It Gets Mistaken For

  • Collaboration problems
  • Communication breakdowns
  • Personality conflicts
  • Lack of alignment
  • Insufficient resourcing

The system blames people for what design failed to specify.

Fatal misread: Misalignment is treated as a people problem instead of a coordination design failure.

Early Warning Signals

  • Work "falls between teams"
  • Progress depends on specific individuals
  • Repeated clarification of "who owns this?"
  • Status updates outnumber decisions
  • Tasks stall after handoff

If these are present, coordination has already decayed.

Common Misdiagnoses

  • "This is just cross-functional complexity"
  • "We need better collaboration"
  • "Teams aren't aligned"
  • "People need to communicate more"
  • "This is a resourcing issue"

What Actually Interrupts It

Explicit end-to-end ownership with authority across handoffs.

Not:

  • More meetings
  • Better documentation
  • Clearer RACI diagrams

But:

  • Named owners for outcomes, not steps
  • Structural authority that spans teams
  • Fewer handoffs, not better ones
  • Designed coordination paths, not social escalation

If ownership does not cross the boundary, the boundary will fail.

Recovery Condition

Work is either formally integrated or formally killed.

Fail-Safe Default

Stop execution until ownership and integration point are defined.

Cascade Relationships

Upstream: FM-03 Responsibility Without Authority, FM-05 Normalized Workarounds

Downstream: FM-02 Escalation Inversion, FM-06 Exception Inflation

If no one owns the handoff, the handoff will fail.
A structural failure mode. Diagnostic only. · DRI™ Coherence Taxonomy