Business resilience
Context
Resilience moved to the boardroom.
Regulators demand it (NIS2, DORA). Insurers price it. Boards ask for it. And when companies get hit by something serious, it's the first thing everyone points at.
The problem: most resilience programmes are policies in a binder. No one has trained them. No one knows if they work. The first time they get used is the real time.
What it is
Resilience is not a policy. It is a muscle.
Resilience is the capacity to absorb shocks, learn, and come back stronger. It is a muscle to be trained, not a policy to be filed. The difference between having a plan and having a plan that works is training.
Early steps
Map. Build. Train.
1. Map vulnerabilities while there is time. Where do you depend on individuals, suppliers, systems? What happens if they fail tomorrow?
2. Build capabilities and structures in. Clear decision structures, redundancy where it matters, playbooks for the scenarios you cannot handle on the fly.
3. Train it before you need it. Tabletop exercises, simulated incidents. The first time you try it must not be the real time.
Why us
We run Resilient Gym ourselves.
We run Resilient Gym in Copenhagen, because physical resilience is the foundation of mental resilience, and that foundation has to be trained, not read about. We bring the same thinking into your business: train the foundation, the rest follows.
In a world of geopolitical instability, supply-chain crises, and new threats, the foundation is no longer a bonus. It is a precondition. We lead by what we do.
When to call
Signals
New regulatory demands, a critical supplier dependency, fragile IT architecture, or just a gut feeling that you would not handle a serious incident. Those are good signals.
If you are in the middle of an incident right now, that is Recovery in Special Projects.