Running an AI-agent incident tabletop exercise
A useful tabletop follows one plausible agent failure through detection, containment, evidence, business recovery and accountable return to service.
The next move. Considered. Ideas for the people turning agentic AI into real work: strategy, systems and the evidence behind better decisions.
A useful tabletop follows one plausible agent failure through detection, containment, evidence, business recovery and accountable return to service.
Model concrete failure scenarios across detection, containment, correction, disruption and consequence, then use ranges to choose controls.
“Internet access” is too broad a permission for an agent. Define destinations, protocols, data-release rules and failure behaviour, then test bypasses against the deployed network path.
Boards do not need to review prompts or model scores. They need a clear account of what each agent may do, whose mandate it carries and how control is recovered.
Maintenance agents can turn condition signals into coordinated work, but plant safety and control demand bounded action and field verification.
A joint lab should be a governed way to create decision evidence across organisations, with shared methods but explicit ownership of systems, data and conclusions.
Buy evidence, controllability and lifecycle obligations—not a confident demo or an unrestricted promise of autonomy.
Long-running agent work cannot rely on a transcript and hopeful retries. Explicit state makes progress, authority, recovery and completion inspectable across failures.
Accept an agent against outcome distributions, critical invariants and recovery evidence—not one scripted response or an average score.
Model usage is one line in a wider cost stack that includes integration, evaluation, control, human work, incidents, change and exit.
Agility is not a property of the algorithms you chose. It is a property of how your code, your data formats and your protocols name them—and whether anything can change without a coordinated rewrite.
Reviewable agent decisions depend on a small chain of artefacts connecting workflow purpose, authority, configuration, evidence, findings, controls and ownership.
KEEP EXPLORING
Read the method, assumptions and questions to ask.
A little more clarity
Start with the questions that shape a better decision.
The blog examines where agents create business value, how teams define release evidence, how authority and tool access should be bounded, and how engineering, security and governance owners can make a shared decision.
They are written for product, engineering, AI platform, security, governance and transformation leaders responsible for moving an agent workflow from idea or pilot towards accountable operation.
Articles explain the problems and decision methods behind the consultancy’s service direction. They are educational material and do not replace a scoped review of an organisation’s actual system.