
Have you ever been in a grocery store when the cash register systems crashed? I have, and it wasn’t pretty to watch the panic in shoppers’ eyes when they couldn’t use their credit or debit cards to pay.
How about being at an airport like last Friday when the U.S. air traffic control system crashed, leaving tens of thousands stranded?
We live a technology-dependent existence today, and it comes home to haunt us every time the power goes out in your neighbourhood, or the elevators in your building malfunction, or the underground garage door to your parking area won’t open.
I remember working on documenting a banking application for a client many years ago. The bank wanted to automate the teller experience and spent millions on new software that required tellers to completely change customer interactions. A system that efficiently used paper records went digital, and the paper system vanished. Woe to the bank when the new computer system crashed with no manual backup to rescue operations. Branches closed until the new system eventually rebooted.
Technology Breaks
This has been a week of technology crises, one global and the other American. The Microsoft outage affected millions of users in 70 countries, crashing e-mail and online meeting systems software for more than 4 hours.
On France 24, an English-language network in France, Marcel Saucet, Research Associate at the University of San Diego School of Law, described the Microsoft outage as an example of overreliance on technologies becoming single points of failure.
Then on Friday, November 13, always an ominous date for those who are superstitious, the U.S. air traffic control system crashed. The disruption left 1.5 million passengers stranded in airports, more than 4,700 flights cancelled that day, and 15,000 more disrupted over the next few days. International flights passing through U.S. airspace from Canada either didn’t fly or were rerouted.
These are just two examples of single points of failure brought on by technology reliance in the 21st century. This is our Achilles’ heel, and we have had plenty of warning that it was coming based on recent history.
Historic Single Points of Failure
There is weakness in overdependence on singular solutions. This one isn’t specifically a technology single point of failure. It does, however, illustrate vulnerability to chokepoints. I’m talking about the 2026 U.S.-Israel-Iran war, which has continued to shut down marine traffic through the Strait of Hormuz and is contributing to oil and fertilizer shortages and inflationary pricing on gas and diesel fuels around the world.
Whether we are talking about industrial processes, supply chains, marine chokepoints, or electrical grids, the historic examples of single points of failure are many.
I cherry-picked these three from recent electrical grid failures:
- The 2011 Southwestern U.S. blackout, when a single power line failed in Arizona and triggered a cascade of blackouts that affected 5 million people across the state, Baja California, San Diego, and California’s Central Valley.
- A similar power line failure in Switzerland in 2003 caused a cascading blackout across Italy.
- Another failed power line in Ohio, one that I personally remember, led to the great North American blackout of August 2003. More than 50 million people in the Northeastern U.S., Ontario and parts of Eastern Canada were left to experience two starlit nights with cities completely blacked out. Some saw the blacked-out skies as a blessing and a return to nature.
Contingency Planning for Single Points of Failure
Without contingencies when technology fails, modern society gets disrupted. This continues to happen despite historic examples of the consequences.
I mentioned the grocery store cash register incident earlier in this article. At least when they went out, one checkout lane had a register that could accept cash. Having this contingency is a good example of a workaround. It slowed operations down, but at least the store remained open.
Think about workaround contingencies that could keep a range of business operations going when technology we rely on fails. Here are some examples:
- If your business relies on e-commerce and it crashes, have a backup in place to take orders by telephone.
- If your inventory and warehouse management systems fail, have printed waybills, pick lists, and other paper records to keep operating.
- If your customer service management system (CRM) goes offline, create manual call logs and printed client phone listings to ensure you can continue to engage clients.
- And considering my previous reference to banking systems, ensure you continue to have downtime forms and processes so people can get their money. By the way, the same workarounds need to be in place for health, insurance and other businesses dependent on electronic records.
The Need for Redundancy
When primary technology systems fail, redundancy plans should include:
- On-site backup power in the event of grid failure, including off-the-grid servers that become accessible.
- Alternate workplace solutions, including work-from-home, as occurred during the COVID-19 pandemic.
- Satellite telecommunication links when landline or land-based wireless systems fail.
These are just three workaround solutions that provide defence in depth against dependent system failures. You may not get the same volume of work done. You may experience slower feeds and speeds. At least, however, short of shutting down, redundancy and workarounds today are a necessary part of doing business in our heavily technology-dependent 21st century.

