What does it mean that bottleneck relationships create fragility?

When everything must flow through a single connection that connection is a critical vulnerability.

Example: In March 2021, the container ship Ever Given ran aground in the Suez Canal, blocking the 265-meter-wide waterway for six days. The canal normally handles roughly 12% of global trade. The blockage delayed 432 vessels carrying cargo valued at $92.7 billion, cost an estimated $400 million per hour in stalled commerce, and triggered supply chain disruptions that persisted for months. The fundamental problem was not the ship. It was that global shipping had funneled an enormous volume of trade through a single 193-kilometer channel with no bypass. The canal was a bottleneck relationship — a connection so central that its failure propagated instantly to every system that depended on it.

Try this: Map one system you participate in — your team, your household, your project workflow, your social circle. Identify every node (person, tool, process) and draw the connections between them. Now ask: if I removed this one node or this one connection, what breaks? Find the single point whose removal would cause the most disruption. That is your bottleneck. Write down three specific consequences that would follow from its failure, and one concrete action you could take this week to create an alternative path around it.