August 3, 2026 · by David Gilbert · 4 min read · Emergency Services & Tech
Tabletop exercises — simulated incidents, played out on a map or digital display rather than in the field, with everyone making the same calls they would in a real response — can feel a bit like homework compared to an actual callout. One particular exercise found a genuine gap in how we shared information that years of real incidents, oddly, hadn't fully exposed, and it's changed how seriously I take this kind of training.
Why a Simulation Found What Reality Hadn't
Real incidents are chaotic enough that small inefficiencies get absorbed into the general difficulty of the situation — something doesn't quite work smoothly, everyone's stressed and busy, and it gets attributed to "incidents are just hard" rather than to a specific, fixable process gap. A structured exercise removes enough of that chaos that you can actually isolate a problem instead of it disappearing into the general noise of a real, high-pressure event.
The Specific Gap We Found
Information was reaching the incident controller from field teams promptly enough. The actual problem was on the way back out — decisions made centrally weren't reliably reaching every team that needed them, particularly ones operating slightly outside the main flow of radio traffic. Nobody had designed this gap on purpose. It had just developed quietly as the team and the area of operation both grew, never deliberately fixed because no single incident had made it obviously, undeniably visible all at once.
Why This Matters More Than It Sounds
A decision that doesn't reach the people meant to act on it is, functionally, the same as no decision being made at all, except worse, because everyone centrally believes it's been actioned. That gap between "decided" and "actually communicated to everyone who needs it" is exactly the kind of failure that looks fine in a debrief — "we made the right call" — while quietly not helping anyone on the ground who never actually received it.
What We Actually Changed
We built a more structured confirmation step into how decisions get distributed — not relying on broadcast-style radio traffic alone, but an active step to confirm specific teams have actually received and understood specific instructions, rather than assuming a broadcast message reached everyone simply because it was said clearly once over the air.
Why This Connects Directly to My Day Job
This is the exact same category of gap I find constantly in business systems — something that technically works, that nobody designed to fail, that's quietly been leaking information for ages without anyone noticing because no single incident made it obviously visible. A client's internal process for following up on enquiries. A handover process between two staff members. The fix is almost always the same: build in an active confirmation step rather than trusting a one-way broadcast to have actually landed.
Why I'd Defend Tabletop Exercises to Anyone Who Thinks They're a Waste of Time
It's tempting, especially for experienced people, to see structured practice scenarios as something for newer members rather than something genuinely valuable regardless of experience level. This single exercise is the clearest argument I've got against that instinct — years of real incidents hadn't surfaced this gap, and a couple of hours of structured simulation did, specifically because it removed enough chaos to let a real, persistent process problem become visible.
The Takeaway for Any Team, Anywhere
If you've never deliberately run a structured "what if" scenario for your own business or team — not a real crisis, just a calm, deliberate simulation of one — it's worth doing at least once. The value isn't really in rehearsing the parts you already know work. It's in finding the quiet, unglamorous gap nobody's noticed yet, before a real situation is the one that finds it for you instead.
