Observation No. 16 · The system everyone routes through
The detour was arranged before the road closed.
At 5:45 on a Friday morning in August, malware got into the computer systems of Suisun City, California. The city cut its entire network, partly by design: the system shuts itself down when it detects an intruder. Police dispatch, fire dispatch, 911 routing, records, all of it went dark at once.
And 911 kept working. Dispatchers started taking calls through the neighboring county’s dispatch center, the emergency operations center opened, and the city’s spokesman could say with a straight face that the average resident would notice little beyond being unable to pay a water bill. The most critical service the city runs survived the loss of everything it runs on.
It survived because the detour already existed. Somebody, on some ordinary day years before, arranged that the county’s center could carry the city’s calls. On every day since, that arrangement did nothing and cost nothing and was visible to no one. It waited.
Two days later, an airline ran the same experiment with the opposite preparation. On August 9, JetBlue’s crew scheduling software failed from late morning to mid-evening. That system is how crews pick up trips, swap trips, and get repositioned; it had been failing on and off for weeks. That day the airline logged 504 delays and 78 cancellations, with crews and planes out of position.
The pilots’ union had already described what the failure looks like from inside: crews unable to be positioned where they were needed, a scheduling department “effectively unreachable, with pilots experiencing hours-long hold times,” people stranded overnight at airports. The airline’s countermeasure was a $5,000 bonus for flight attendants who fly 150 hours in August.
Notice what the bonus is for. Cash solves a motivation problem. The people were willing; the failure was coordination. Thousands of qualified crew members were ready to work and had no way to find the work, because the one layer that matched people to planes was down and nothing stood behind it. Money cannot dial the phone that isn’t answered.
The two stories share one skeleton. In both, a single layer quietly carried all the matching: which dispatcher takes which call, which crew takes which plane. A layer like that disappears into the furniture precisely because it works every day. Then it stops, and what happens next depends entirely on what was arranged back when nothing was wrong.
Your business has this layer. It’s usually a person, or a whiteboard, or a group chat. One place where who-does-what gets decided, that everything routes through, that nobody thinks of as infrastructure because it’s just how Tuesday works.
The test worth borrowing from Suisun City is specific: the fallback existed as an arrangement, with a counterparty who had agreed, and a path that could actually carry the traffic. An arrangement is different in kind from an assumption. “The county takes our calls” is an arrangement. “We’d figure it out” is an assumption wearing work clothes.
The small-business versions of the mutual-aid agreement are unglamorous and nearly free. The reciprocal deal with another shop to cover each other’s emergencies. The retired scheduler who agreed, out loud, to answer the phone that week. The printed sheet in the drawer with the day’s jobs, crews, and customer numbers, updated Friday afternoons, useless every week until the one morning it’s the only copy of the schedule that still exists.
Each was arranged on a calm day, costs a few minutes a month, and does nothing for years. That’s what working looks like, for this kind of thing.
So the question the pair of failures asks: if the system everyone routes through vanished this morning at 5:45, is there a fallback that is arranged, tested, and reachable, or only one you assume exists?
