AKIRA / Practical perspective
Friday the 13th: A Weekend of Crises—and a Test of Preparedness
AKIRA Intelligence Network examines crisis preparedness: decision authority, independent communications, evidence-led response and tested recovery.
Published
A leadership controversy. A major technology outage. A river collision. A nationwide interruption to air travel.
The events surrounding Friday, 13 November 2026 brought different forms of crisis into view at once: governance, digital dependency, physical safety and critical infrastructure.
For those affected, the consequences were immediate and personal. For boards and leadership teams watching, the weekend raised a practical question:
If our organisation faced a serious incident tonight, could we protect people, establish reliable facts and make decisions while our usual systems were unavailable?
The calendar provides the headline. Preparedness determines the response.
Different events, different responsibilities
At NVIDIA, reporting about Jensen Huang’s acknowledged relationship and alleged links to Chinese intelligence raised questions about governance and executive risk. Beijing denied the espionage allegations. NVIDIA announced an independent investigation; the existence of allegations does not establish that confidential information was compromised.
Source: AFP — https://www.afp.com/en/what-we-know-about-nvidia-ceo-spy-scandal
Microsoft’s widespread service disruption demonstrated the operational consequences of losing everyday digital tools. The company subsequently reported services restored and said it had found no indication of malicious activity.
Source: Associated Press — https://apnews.com/article/ca395c0f1e51af784b6d70afb6554f6a
In New Orleans, a tanker struck a docked passenger vessel on the Mississippi River, prompting an emergency response. The incident’s cause remained under investigation.
Meanwhile, the FAA reported communication problems affecting multiple air traffic control centres and issued a nationwide ground stop. That was a restriction on departures, rather than every aircraft in the country suddenly stopping operations.
Source: Federal Aviation Administration — https://www.faa.gov/newsroom/faa-statement-nationwide-ground-stop
These events should not be treated as evidence of a common cause. They do, however, provide a useful starting point for examining how organisations prepare, respond and learn.
The following are preparedness principles—not findings about the causes of these incidents.
Before the event: prepare for losing your normal capabilities
A crisis plan must remain usable when the conditions it assumes disappear.
Consider a simple exercise: email and collaboration tools are unavailable, the chief executive cannot participate, and several key people are stranded while travelling. Can the organisation still assemble its response team and authorise urgent action?
Preparation should establish:
- Decision authority: who leads, who deputises and which decisions require board involvement.
- Independent communications: a tested alternative that does not depend on the same systems as the primary channel.
- Operational priorities: what must continue, what can pause and what must stop for safety.
- Escalation thresholds: the signals that require immediate attention, including outside working hours.
- Accessible records: emergency contacts, essential procedures and critical information available during an outage.
Executive risk belongs in this preparation too. Organisations need clear arrangements for conflicts of interest, access to sensitive information and independent escalation when concerns involve senior leadership.
Controls should apply consistently, including to the most influential person in the organisation.
During the event: protect people and establish control
The first response should match the incident.
A physical emergency requires emergency services and qualified operational leadership. A technology failure requires technical containment and continuity arrangements. A governance allegation requires independent oversight and careful handling of evidence.
At leadership level, the immediate priorities are to protect people, limit further harm and establish a clear structure for decisions.
Create a concise situation report with three distinct categories:
Confirmed facts. Working assumptions. Unanswered questions.
Every significant fact should have a source and a timestamp. Every urgent unanswered question should have an owner.
This prevents a common failure: an early assumption being repeated until it becomes the organisation’s official position.
Maintain a decision log as well. Record what was decided, by whom, using what information, and when that decision will be reviewed. This supports both the live response and a fair assessment afterwards.
Avoid overwhelming operational teams with competing instructions. Establish one route for priorities, while preserving the ability to escalate immediate safety concerns.
Communicate while uncertainty remains
Waiting for complete certainty can leave employees, customers and partners without useful guidance. Speaking too confidently can damage credibility when the facts change.
An effective early update should explain:
- What is confirmed.
- Who or what is affected.
- What action is underway.
- What affected people should do.
- When the next update will be provided.
A credible update can acknowledge uncertainty. It should not speculate about responsibility, declare a cyberattack without evidence or promise a restoration time that the response team cannot support.
Communications also need to reach people through channels they can actually access. An outage notice sent only through the affected platform offers little practical help.
For incidents involving injury or danger, care for affected people and families must remain central throughout the response.
Investigate without prejudging the answer
Stabilising an incident and explaining its causes are related but separate tasks.
Preserve relevant records from the outset, without obstructing urgent safety work. Depending on the event, these may include system logs, maintenance records, messages, access records, decisions and witness accounts.
Where senior leadership may be involved, the investigation needs appropriate independence. Those whose conduct is being examined should not control its scope or conclusions.
Reconstruct the timeline and ask:
What happened? What was known at each stage? Which warnings were available? Which safeguards worked? Which failed, were bypassed or did not exist?
Assess decisions against the information reasonably available at the time. Hindsight can make uncertainty disappear from the story and produce unfair—or ineffective—recommendations.
Accountability matters. So does understanding the conditions that allowed the incident to develop.
Recovery: prove that operations are ready
Restoring a service is an important milestone. It does not, by itself, demonstrate that every consequence has been resolved.
Backlogs may remain. Information may need reconciliation. Staff may be fatigued. Customers may need individual support. Temporary workarounds may introduce new risks.
Define recovery criteria before declaring the incident closed:
Can essential activities operate reliably? Have safety checks been completed? Are outstanding exceptions visible and assigned? Is there a plan if the problem returns?
Recovery should be supported by evidence and monitored as operations resume.
Lessons learned must change behaviour
“Improve communication” is an observation. It becomes useful only when translated into a specific change.
For every material lesson, assign an owner, a deadline, resources and a test.
Examples include exercising an alternative communications channel, rehearsing a leadership handover, reviewing access privileges or checking whether a backup shares the same dependencies as the primary system.
Then repeat the exercise. A revised document does not establish that the organisation can perform differently under pressure.
The most useful question after a crisis is:
What can we now demonstrate that we could not demonstrate before?
Friday the 13th offers a memorable headline. The responsibility continues on Monday morning: review assumptions, close gaps and test whether the organisation is better prepared.
AKIRA Intelligence Network
Corporate Crisis Management & Strategic Advisory. Clarity under pressure.
Related services
To discuss how this guidance relates to your organisation, contact AKIRA.