READINESS
Tabletop drills your team will actually run
Most teams know they should rehearse. They skip it because writing scenarios, running injects and writing up the debrief eats a week. Incident Lake does that work, runs the drill in the same Slack or Teams channel you use for real incidents, and turns what you learn into tracked follow-ups.
01 Design
Scenarios that fit your stack
Start from an industry catalog (financial services, telecom, energy, healthcare, logistics, public sector and more) or have the LLM generate one from your own service map. Nothing runs until someone approves it.
02 Run
Injects on a schedule
Cards drop into the drill at the times you set. Facilitators and players see different views, and every decision players make is captured in the timeline.
03 Learn
A debrief that becomes work
The debrief is drafted for you and exports to PDF or Excel. Risks go to problem management; runbook fixes go to the knowledge approval queue.
Frameworks we draw on
Scenarios reference DORA (digital operational resilience testing), ISO 22301, ISO 22398, ISO/IEC 27001 and NIST SP 800-84. Running a drill in Incident Lake does not by itself make you compliant with any of them.
Auditors increasingly ask for evidence that exercises happened and that findings were closed. Every drill leaves a timeline, a debrief and a list of follow-ups with owners.
How a drill runs
Pick or generate a scenario
Choose from the catalog or generate from your CMDB. An owner reviews and approves it.
Run it where you run real incidents
The drill opens as a clearly labelled incident in Slack or Teams, and the agent asks for commander and severity exactly as it would on a bad day.
Close the loop
Missed escalations and slow decisions become improvement tasks you can track to done.
Run your first drill
Sign-up takes a work email and a company name. Replaying last quarter's worst outage is a good first scenario.
Start free →References to regulations and standards are general information, not legal or audit advice.