Understand exposure
Identify what critical operations depend on — suppliers, sites, systems, people, authority — who controls each dependency, and how quickly it can be lost.
← About/Our Approach
The organisationas one operating system
Resilience is designed around how dependencies, people, assets, suppliers, technology and authority behave together — and how each one degrades — rather than around a list of separate scenarios.
01
THE SYSTEM
Nothing here fails on its own
Critical operations sit at the end of a chain of systems that are usually planned for separately and fail together.
Disruption to power reaches communications, payments and operations at once, by different routes and on different timescales. Transport decides who can reach work; authority decides how long everything else waits.
The work starts by drawing these dependencies for a specific organisation — what it relies on, who controls it, and how quickly it can be lost — because the lines between the boxes are where plans usually fail.
02
A
Severe but credible, not only likely
We prepare against severe but credible disruption, not only the most statistically likely. The likely event is usually already covered.B
Designed for degraded conditions
Critical procedures have to work when connectivity, power, staffing or normal systems are unavailable — on paper, where necessary.C
Authority that does not depend on one person
Critical decisions cannot wait for someone who may be unreachable. Decision rights, thresholds and succession are set in writing beforehand.D
Tested by adversarial challenge
Plans are tested under realistic scenario pressure, including deliberate challenge from people trying to find where they break.03
Design for degraded operation
Define how each critical function operates when normal systems or resources are unavailable, and what it can stop doing.
Clarify authority
Make decision rights, escalation thresholds and succession explicit before the crisis, so no decision waits for one person.
Test under pressure
Use scenario exercises, simulations and adversarial challenge to expose weaknesses while they are still inexpensive to fix.
Embed capability
Keep plans, people, procedures and physical resources usable without KOLOSAL7 in the room — through drills, paper copies and regular re-testing.
P1ExposureWhat you depend on, who controls it, and how quickly it can be taken away.
P2DesignCommand structure, thresholds, degraded-mode runbooks, delegated authority.
P3TestWargame against a live adversary. Everything that fails is rewritten.
P4EmbedDrills, paper copies on site, annual re-test, standing government channel.
04
L1 / PLAN VIEW
Board, delegated authority, thresholds pre-signed.
Succession named three deep before anyone needs it.
- 01SEVEN NAMED SEATS
- 02THRESHOLDS PRE-SIGNED
- 03SIGNED DELEGATION
One structure, four layers, drawn for your organisation and rehearsed until the sequence is muscle memory.
HOW AN ENGAGEMENT STARTS→Written, tested,and left readyto execute
Not advice and not a document. The plan is installed, rehearsed on shift, and handed over in a state it can be run in.