Loading...
In 1958, programmers at IBM began storing years as two digits to save precious bytes of memory. By the 1990s, this shortcut was embedded in billions of lines of COBOL running banks, power grids, air traffic control, and nuclear arsenals. The fear: on January 1, 2000, computers would read '00' as 1900, triggering cascading failures — ATMs freezing, planes losing navigation, hospital equipment resetting. In 1996, programmer Peter de Jager published warnings that galvanized governments worldwide. The U.S. Congress created the Senate Y2K Committee, chaired by Robert Bennett and Christopher Dodd. Their approach was textbook pre-mortem thinking: assume the disaster has already happened, then work backward to prevent it. Scenario planners at the Federal Reserve stockpiled $50 billion in extra ...
Popular framing: Y2K was a hoax — nothing happened, so the panic was overblown.
Structural analysis: The non-event was the evidence of success. Pre-mortem reasoning plus scenario planning plus engineered margins of safety across 300,000 programmers and $300B of remediation closed the failure paths before midnight; the natural experiment shows it — countries that spent heavily had near-zero failures, countries that didn't had clusters. Survivorship bias on the outcome misreads avoided cost as wasted cost.
The gap matters because it systematically discredits preventive action: if successful prevention is indistinguishable from unnecessary panic, societies will consistently under-invest in future systemic risk mitigation. Every Y2K-style framing of 'wasted money on a non-event' raises the political cost of the next pre-mortem intervention, making catastrophic failure more likely when the next slow-building systemic risk matures.
