On Friday 13 November 2026, a global cloud outage showed how much of our work depends on systems we rarely think about. The technology came back but the dependencies are still there.
The outage disrupted the tools organisations around the world rely on every day. Australian businesses and government agencies lost access to email, collaboration tools and other services for much of the working day. There was no indication of a cyberattack. Nothing was stolen. Nothing was lost.
And yet a lot of work simply stopped.
The consequences went well beyond unanswered emails. Online classes were disrupted. Government agencies and large organisations reported being brought to a standstill. Small businesses could not process orders or send invoices. Some people could not access other systems at all, because the sign-in codes they needed never arrived.
While everything is back up and running for now, the outage exposed major risks surrounding business resilience for both enterprise and government.
When technology becomes unavailable, how much of your organisation becomes unavailable with it?
How did your continuity plan hold up?
A continuity plan is essential in times like this but for many organisations, it either hasn’t been shared widely across the business, or it simply does not exist.
If you do have one, did people know what to do? Could they access the plan? Did it reflect how your organisation actually operates, or how it operated when the plan was written? And, importantly, did the process for contacting staff rely on the same services that were down?
A continuity plan saved on the intranet is useful until the people who need it cannot open the intranet. An instruction to contact your manager only works if there is still a way to reach them.
In a large organisation, there are multiple players needed to make decisions on how to proceed. Technology teams work to restore access. Operational teams decide which services continue, what can wait and what needs another way of working. Communications teams try to tell people what is going on.
A continuity plan should consider all the essential roles and their responsibilities. Those roles need to be defined before an outage. Not during one.
Should that process rely on email?
Email is a useful mode of communication. It moves approvals between teams. Delivers documents. Carries requests from the public. Sends sign-in codes. Tells staff there is work waiting in another system.
Over time, it quietly becomes more than just a communication channel. It becomes the thing holding whole processes together. So, what happens when it goes down?
Email is where most people felt it but it is not the only dependency hiding in plain sight.
Most organisations now run email, chat, documents, calendars and sign-in through one or two cloud providers. That is efficient. It is also a concentration of risk. When one provider has a bad day, everything that runs through it has a bad day, too.
It is easy to assume you are protected because your systems are in the cloud, backed up and managed by a reputable provider. You are protected from losing your data. You are not protected from losing access to it. And if sign-in runs through the same provider, people can be locked out of systems that are still running.
Technology resilience and business resilience are not the same thing.
What makes a continuity plan work?
Moving something out of email does not automatically make it resilient. An app notification will not help if the app is also down. An automated integration still needs monitoring, an owner and a way to recover when it fails.
A backup communication channel needs to work independently of the service that has gone down.
To be resilient, your continuity plan should factor in all possible risks and scenarios with processes in place for each. Looking at the whole process, including how people would know something has failed and what they could do about it, is where a continuity plan stops being a document and starts being practical.
People should know which work takes priority, who can make decisions and how to keep essential services moving.
A conversation for your next leadership meeting
Pick one critical process that relies on email and walk through it together.
- What role does email play? Is it a notification, an approval, a record or the way data moves?
- Could the work continue without it? Can someone find and action the task another way?
- Would changing the process improve it every day? Look for less double handling, fewer delays and clearer ownership.
- What would the alternative depend on? Make sure you are removing the dependency, not just moving it.
- What is the fallback? Can people reach the instructions, and do they have the authority to use them?
You might find email is still the best option. You might find a simple change that saves your team hours every week.
Either way, you will understand your organisation better than you did before.
Where Move FWD can help
At Move FWD, one senior team looks at how your people, processes and technology work together, and speaks to business leaders and technical teams alike.
Our Business Resilience & Dependency Review is a focused short engagement covering an agreed set of critical processes. We map what those processes rely on, identify where work could stall and recommend practical improvements.
That might mean simplifying an approval, connecting two systems, setting up a backup communication channel or making sure more than one person can run a critical task.
You leave with a clear dependency map, prioritised actions and an improvement roadmap, with honest advice on what is worth changing and what is fine as it is. And because we are the consultancy that stays to deliver, the same people can help you make the changes, not just hand over a report.
The outage lasted a day
The dependencies it exposed were there long before it. Unless something changes, they will still be there for the next one.
And there will be a next one.
The best time to find out where your organisation is exposed is not when everything stops working.