It's been quite a week for technology outages.
Between November 10 and November 18, several major organizations experienced significant service disruptions. Microsoft, Apple, Workday, the Federal Aviation Administration (FAA), and even the National Security Agency (NSA) were among those affected.
What makes these incidents particularly interesting from an IT Service Management (ITSM) perspective is that several were connected to routine maintenance, software updates, infrastructure upgrades, or testing.
Activities that organizations perform every day.
Let's look at what happened.
A Week of Changes and Service Disruptions
Microsoft 365 – November 12–13
A global outage disrupted Outlook, Exchange Online, Teams, and other Microsoft 365 services for nearly 24 hours.
Microsoft's preliminary findings identified a combination of a software defect introduced months earlier, network traffic changes, and reduced server capacity. Routine network maintenance exposed the existing defect, overwhelming infrastructure and disrupting services.
The incident demonstrated how a seemingly routine change can expose underlying weaknesses that traditional change testing may not detect.
Workday – November 13–14
Workday experienced a significant disruption affecting its production environment, leaving customers unable to access critical HR and business services.
Reports identified a disaster recovery testing issue that introduced data inconsistencies into the production environment. Workday placed affected production tenants into maintenance while recovery activities were performed.
An important reminder that disaster recovery testing is itself a change activity that requires appropriate controls, isolation, and risk assessment.
Federal Aviation Administration (FAA) – November 13
A nationwide ground stop disrupted thousands of flights across the United States.
The FAA reported that network instability occurred during infrastructure maintenance involving the replacement of legacy telecommunications equipment. Excessive connection attempts overwhelmed parts of the network, affecting communications and radar feeds.
The precise root cause remains under investigation, but the incident raises important questions about assessing dependencies and the potential impact of routine infrastructure changes on critical services.
Apple – November 17
Apple experienced outages affecting services including iCloud, Apple Music, the App Store, and AppleCare.
Apple acknowledged that an internal update caused the disruptions. Although services were progressively restored, the incident demonstrated how an internal technology change can quickly become a customer-facing service issue.
National Security Agency (NSA) – November 17
The NSA reported temporary degradation of its internal classified communications network during scheduled routine maintenance.
The agency stated that mission-critical capabilities remained operational, highlighting both the potential risks of maintenance activities and the importance of operational redundancy.
What Do These Incidents Tell Us?
These incidents occurred in different organizations, industries, and technology environments. They don't necessarily indicate that change management processes failed, but they do demonstrate why managing change risk matters.
A change can be technically successful and still create an unexpected business impact.
Consider the questions every organization should be asking:
- Risk assessment: Are we assessing the potential business impact of a change, or simply categorizing it as low, medium, or high risk?
- Dependencies: Do we understand which services, applications, infrastructure, and business processes could be affected?
- Testing: Are we testing beyond the immediate component being changed?
- Recovery: Do we have a practical, tested recovery approach if the change creates unexpected problems?
- Change scheduling: Are we considering business activity, service criticality, and the cumulative risk of multiple changes?
- Continual improvement: Are we learning from unsuccessful changes and using that information to improve future decisions?
Change Management Is About Risk, Not Approvals
Too often, organizations measure change management effectiveness by the number of changes approved, completed on time, or implemented without a reported incident.
Those measures have value, but they don't tell the entire story.
Effective change management should help organizations make informed decisions about introducing risk into their operating environment.
That means understanding what could go wrong, the consequences if it does, and whether the organization is prepared to respond.
It also means recognizing that a routine or standard change isn't automatically risk-free.
The events of the past week provide some very visible examples of why this matters.
So here's the question: Are your change management practices set up in a way to manage your organizational risk?
Or are they primarily designed to manage the administrative process of implementing changes?
At Blackfriar Consulting, we help organizations assess and improve their ITSM practices, including Change Management, with a focus on practical improvements that support business outcomes.
Contact us to see where we can help
