
THE DISASTER LAB / PRACTICE BEFORE THE PAGE
What’s your
next move?
A safe place to rehearse a bad day. Choose a scenario, make the calls, and take the lessons back to your team.
AUTHORED EXERCISES · NO LIVE AIINSPIRED BY KNIGHT CAPITAL
The orders
won’t stop.
Configure release safeguards and emergency controls. Then find out whether they can contain a runaway router.
- Two safeguard choices
- Branching consequences
- A debrief based on your decisions
A FICTIONAL CUSTOMER INCIDENT
The shop is open.
Checkout isn’t.
A release breaks the purchase journey. Balance diagnosis, recovery, and the information your customers need.
- Three response decisions
- A fixed incident sequence
- Immediate feedback and replay
A RESTORE IS ONLY THE BEGINNING
The backup exists.
The data is missing.
Set an acceptable data-loss window, preserve the incident state, and decide when a restore is ready for customers.
- A recovery target you choose
- Three consequential decisions
- Validation and reconciliation lessons
WHEN THE BACKUP SHARES THE PROBLEM
Your provider is down.
Now what?
Test the assumptions behind your fallback. Keep a useful service running, communicate clearly, and bring traffic back deliberately.
- Two dependency choices
- Four response decisions
- A debrief you can take to your team
Bring the debrief to your team.
These are learning exercises, not predictions or readiness scores. They do not access your systems. Discuss which assumptions hold in your environment—and which need testing.
Start with a safeguard review ↗