Use casesIncident & crisis drills
Rehearse the bad day before it happens
Outages, security alerts, a supplier that suddenly can't deliver. Run the drill in a simulated company, so the first time your team handles it isn't the real time.
- Runs in
- A web browser, 3D included
- One exercise
- 20 to 55 minutes
- Practice levels
- Six, from worked example to exam
- Working tools
- 6 used in these exercises
A drill, for example
Thirty minutes after a release, checkout errors spike. Alerts fire, the support team doesn't know what to tell customers, and a manager wants an update. Afterwards the team replays the timeline and agrees what to do differently.
How it works
Every exercise follows the same rhythm as the real job: a problem arrives, you investigate, you act, and the simulated company responds.
- 01
Start the drill
Pick a scenario: outage, bad release, security alert or supply disruption.
- 02
The team responds
Investigate, act and communicate with the same pressure as a real incident.
- 03
The company reacts
Lost sales, recovery time and customer impact grow until the problem is handled.
- 04
Review together
Replay the timeline step by step and agree on improvements.
What you practise
Concrete tasks taken from the exercises on this page. Each one is done with real data, under real constraints, inside the same simulated company.
- T01
Software outages
Find the cause, roll back, and restore the service.
- T02
Security alerts
Triage, contain and preserve evidence.
- T03
Supply and plant disruptions
A late supplier or a failed machine with customer orders at risk.
- T04
Crisis communication
Clear updates for managers, staff and customers.
What your organisation gets
Evidence, not attendance.
- 01
No risk to production
Nothing real is touched, so drills can run as often as needed.
- 02
Repeatable scenarios
Run the same drill again after changes and compare the results.
- 03
Reviews based on facts
A complete timeline of what each person saw, did and said.
The tools you work with
Working tools, not screenshots. They read the same live data as the rest of the simulated company, and what you change in one shows up in the others.
- 01
Incident console
The live state of services and hosts during an outage, with the runbook actions.
- 02
Feature flags
The switches a service reads, and which one is breaking it.
- 03
Data pipelines
The pipelines feeding production, and which one is sending bad data.
- 04
Security alerts
Alerts, accounts, endpoints and signs of compromise in one view.
- 05
Machine data
Vibration, temperature, cycle time and throughput per work centre, over time.
- 06
Work orders
Work orders, repair history, spare parts and who is assigned to what.
Six levels, one exercise
Teachers and trainers choose how much help each person gets. The exercise stays the same; only the guidance and the grading change.
- L1
Watch it done
The exercise solved step by step, with what each step changed.
- Hints
- Read only
- Graded
- No
- L2
Step by step
The next move is pointed out, every hint is open, goals update as you work.
- Hints
- All hints
- Graded
- Yes
- L3
With hints
Every hint is open, but finding the next step is up to you.
- Hints
- All hints
- Graded
- Yes
- L4
On your own
Hints stop short of the worked answer. Goals still update as you go.
- Hints
- Some hints
- Graded
- Yes
- L5
Exam
No hints and no AI helper. Results appear only after you submit.
- Hints
- None
- Graded
- Yes
- L6
Free play
An open what-if sandbox. Try anything; nothing counts towards a grade.
- Hints
- All hints
- Graded
- No
What every attempt leaves behind
Judge the work, not a quiz score. Every attempt is recorded as it happens, so you can see how someone worked, not only where they ended up.
Every action, in order
What was checked, who was asked, what was changed and when. Nothing is overwritten.
Scores by skill
Each exercise scores the skills it was built to test, from what was actually done.
Weak habits, flagged
Poor patterns in how the work was done are flagged, not only wrong final answers.
A replay of the attempt
Step through the session as it happened, with typed personal details masked.
- Start the drill
- The team responds
- The company reacts
- Review together
Is this a replacement for chaos engineering?
No. Chaos engineering tests your systems. This trains your people: their investigation, decisions and communication.
Is it only for IT?
No. There are drills for software and security incidents, and for factory and supply chain disruptions.
Related
See it with your own people
Start with a pilot: one course or one team. We help you choose the exercises and measure the results.