Tight Coupling Trap

The system design failure where components are so interdependent that change or failure in any component immediately affects many others, eliminating the system's ability to absorb shocks, adapt to change, or fail gracefully. Perrow identified tight coupling as one of the two conditions (along with interactive complexity) that make normal accidents inevitable. The trap mechanism: (1) tight coupling is initially created for efficiency (less overhead, faster throughput, simpler design), (2) the efficiency gains are real and measurable, (3) the fragility costs are hidden because they only manifest during disruption, (4) the system becomes optimized for normal conditions and catastrophically fragile under stress. The lean manufacturing movement, while powerful, created tightly coupled global supply chains with near-zero inventory buffers—producing dramatic efficiency gains under normal conditions and dramatic failures under disruption (COVID-19 revealed these at global scale). The same pattern applies to organizational tight coupling: when every person is fully utilized with no slack, a single absence disrupts everything.

When to use it

When optimizing systems for efficiency. When evaluating supply chain or operational resilience. When a small disruption causes disproportionate system-wide effects. During system design and architecture reviews.

How it can help

Provides the analytical lens for evaluating when efficiency optimization has created dangerous fragility. The diagnostic: perturb the system (mentally or physically) and observe how far the effect propagates. If a small disruption in one area immediately affects many other areas, the system is tightly coupled. Prevention requires intentional slack design: (1) build buffer inventory, spare capacity, and redundancy into critical paths, (2) design interfaces between components that absorb rather than transmit shocks, (3) budget for resilience as explicitly as you budget for efficiency, (4) stress-test the system regularly under simulated disruption. The key insight: the cost of slack (ongoing inefficiency) is almost always less than the cost of fragility (catastrophic occasional failure).