Resilience • continuity • recovery

Prepared before it is needed

Resilience is a discipline built through preparation, design, documentation, redundancy, and practical recovery planning.

Resilience is a discipline

Operational resilience is built through preparation, design, documentation, redundancy, risk awareness, and practical recovery planning.  It begins long before adversity arrives.

Prepare deliberately

Identify critical services, dependencies, people, recovery expectations, and communication paths before a disruption exposes them.

Design for recovery

Backups, failover, alternate access, spare equipment, configuration records, and restore tests turn resilience from intention into capability.

Communicate clearly

During disruption, people need calm information: what is affected, what is being done, what alternatives exist, and what expectations are realistic.

ICT resilience checklist

BackupsKnown scope, protected storage, tested restores, and realistic recovery expectations.
RedundancyAlternate paths for critical services, connectivity, power, access, and communications.
DocumentationReadable diagrams, credentials handling, runbooks, vendor notes, and configuration records.
MonitoringVisibility into failures before users become the monitoring system.
FailoverPractical procedures that can be followed by real people under real pressure.
User expectationsClear communication about what is resilient, what is not, and how service is prioritised.

Relevance to New Zealand

New Zealand's geographic diversity, rural communities, maritime and aviation dependencies, earthquakes, storms, and regional infrastructure needs all reward practical resilience thinking.  That does not require alarmism.  It requires disciplined preparation, maintainable systems, and respect for the people who depend on them.

The Alaska lesson behind resilience

In Alaska, resilience is not an abstract concept.  It is shaped by roads that may be long or unavailable, weather that can change plans quickly, communities separated by distance, supply chains that require patience, and communications paths that cannot always be assumed.  Those realities teach preparation before pressure.

That same thinking belongs in professional ICT and communications work.  A resilient organisation understands its dependencies, documents its systems, tests recovery, protects alternate paths, communicates clearly, and avoids designs that only work when everything else is going well.

Before the outage

Know critical services, owners, credentials, backups, vendors, escalation paths, communication channels, and realistic recovery priorities.

During the outage

Keep information calm, truthful, and useful.  People need to know what is affected, what alternatives exist, what is being done, and what comes next.

After recovery

Capture lessons, update documentation, remove avoidable fragility, and leave the organisation better prepared than before.

For New Zealand

Regional infrastructure, rural connectivity, storms, earthquakes, maritime reliance, and distributed communities make practical resilience thinking directly relevant.