Dependency Trap

When people or institutions become unable to function without a single actor or system.

What it looks like

• “Only they can fix it” becomes normal
• Vendor/leader lock-in blocks alternatives
• Exit is theoretically possible, operationally impossible
• Switching costs become existential risk

Failure mechanism

Capability concentrates into a single dependency node. The system loses redundancy, portability, and the ability to say “no.”

Minimum viable controls

Verification

• Map critical dependencies (technical + human) and failure modes
• Measure switching time/cost as a real risk metric
• Require transparent SLAs and operational proofs for critical suppliers

Counterweights

• Multi-sourcing or credible fallback options
• Contractual and architectural exit rights
• Role redundancy and cross-training for human dependencies

Correction Loops

• Regular failover drills (vendor outage, leader absence)
• Time-boxed dependency reviews
• “Dependency budgets” with reduction targets

Proof you’re controlling it

• You can replace the dependency without halting operations
• Failover drills are real and recorded
• Knowledge is distributed, not hoarded
• Exit plans are funded, not aspirational

Where it shows up

Common at Technological + Organizational depths; often becomes Institutional vulnerability.

Related patterns

Gatekeeper Capture • Authority Without Friction • Crisis as Audit