DISCUSS YOUR SITUATION →
← About/Experience

Learned from conditions,not from scenarios

KOLOSAL7's approach comes from operating experience in Ukraine, where continuity has had to be maintained through sustained, overlapping disruption rather than prepared for as a single event.

Organisations operating in Ukraine have had to keep working through physical threat, attacks on energy infrastructure, scheduled and unscheduled power outages, communications disruption, workforce displacement, restricted physical access, supply and fuel constraints, and state requirements that change as conditions do.

What matters for continuity is not any one of these on its own. It is what each one does next, and where its effects land.

01Power interruption
Sites on backup generation
Fuel logistics become an operational dependency
02Communications loss
Coordination falls back to what still connects
Decisions wait for people who cannot be reached
03Restricted physical access
Sites cannot be staffed or serviced as planned
Maintenance and resupply slip together
04Workforce disruption
Rotations run short of people
Fatigue arrives before any material runs out
05Supply and fuel constraints
Inputs arrive late or not at all
Reserves are consumed faster than they were sized for
06Changing state requirements
Priorities and permissions are reordered
Plans written for the old rules stop applying

Five lessons that shape every engagement.

  1. 01

    Dependencies fail together

    The decisive failures are rarely single events. Power, communications, access and people fail in combination, and each one changes what the others can still do.

  2. 02

    Exhaustion arrives before scarcity

    Under sustained disruption the first resource to run out is usually people who can keep working, not fuel or materials. Rotation and relief have to be designed, not assumed.

  3. 03

    Authority is the first bottleneck

    When the person allowed to decide cannot be reached, everything waits. Decision rights and succession have to exist on paper before they are needed.

  4. 04

    Digital-only procedures disappear with the network

    A procedure that needs a login, a shared drive or a working phone may not exist at the moment it is needed. Critical instructions have to survive the loss of connectivity.

  5. 05

    Backup behaves differently under sustained load

    Generators, batteries and fuel reserves sized for hours meet disruption measured in days. Backup arrangements have to be tested for duration, not only for switchover.

The couplings exposed by sustained disruption in Ukraine — between power and communications, between people and access, between authority and time — exist in any organisation that relies on infrastructure it does not control.

IN UKRAINE — AT THE EVENT

The work is to keep operations running under conditions that already exist.

IN EUROPE — AT A DISTANCE

The work is to find those couplings before they are tested in reality.

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.

DISCUSS YOUR SITUATION→