Why Tabletop Exercises Work (and Why Most Organizations Skip Them)

The cheapest practice you can run.

Tabletop exercises are the lowest-effort, highest-return form of security practice available to most organizations. They require no special equipment, no disruption to operations, no travel. They can be run in a standard conference room with a scenario, a facilitator, and a small group of participants. A 90-minute tabletop exercise can surface capability gaps that a full audit might miss.

Which is why, when organizations say they are going to “get to it eventually,” the something they usually mean is precisely this. And which is why it matters to name, specifically, why tabletops work and why they keep getting deferred.

What a tabletop exercise actually is.

A tabletop exercise (TTX) is a structured discussion-based rehearsal of a realistic scenario. Participants gather around a table. A facilitator presents the scenario, typically in phases. Participants work through their responses, make decisions, and describe what they would do at each stage.

There is no physical action. No one runs. No one evacuates. No one draws a weapon. The whole exercise happens in conversation, using the scenario as a structured prompt for real discussion.

Despite the low energy, tabletops produce outsized learning because they surface the gaps that pure document review cannot.

The four things tabletops surface.

Every well-designed tabletop exercise produces four categories of insight.

1. Protocol gaps

The written plan says X. The team tries to execute it in the scenario and discovers X is incomplete, outdated, or ambiguous. The gap between paper and practice becomes visible in ways that a read-through alone does not produce.

2. Coordination gaps

Two people each assumed the other was doing Y. Three people each planned to be in the same room at the same moment, with no one at the place they were supposed to be. The tabletop makes these coordination failures concrete before they happen in a real event.

3. Communication gaps

How do team members contact each other during the event? Does the primary contact actually have current phone numbers? Does the backup communication path still work? Does the team leader know how to reach law enforcement without dialing 911 directly? Tabletops are where communication breakdowns become visible.

4. Decision-making gaps

Who has authority to make the call? When does it escalate? What criteria trigger different response modes? These questions often have implicit answers that do not survive the first scenario. The tabletop forces the team to make the decision out loud, which reveals where decision authority is ambiguous.

Why organizations skip them.

If tabletops are so valuable, and so low-cost, why do most organizations not run them? A few honest answers.

”We don’t know how.”

Tabletop facilitation is a learnable skill, but it is not obvious. Organizations that have not run tabletops before often do not know how to design one, how to pace it, how to handle common pitfalls, or how to debrief effectively. External facilitation for the first few exercises, with knowledge transfer to internal staff, usually solves this.

”We think it will reveal something uncomfortable.”

It almost certainly will. That is its value. Organizations that avoid tabletops because they will produce difficult findings are organizations that will face those same findings later, in less controlled conditions. The tabletop is a low-stakes way to discover problems.

”We don’t want to scare people.”

A well-facilitated tabletop does not scare participants. It respects them as adults engaging thoughtfully with important questions. The fear response is usually about a poorly designed or poorly facilitated exercise, not about tabletops in general.

”We are too busy.”

This is the most common reason. It is also the reason that compounds. Organizations too busy for a 90-minute tabletop every quarter are organizations that will be much more busy handling an incident for which they were not prepared.

”We did one three years ago.”

A tabletop from three years ago is no longer relevant to your current facility, staff, or threat environment. Annual tabletops are the minimum that makes the exercise meaningful.

The scenarios that produce the most return.

Not every scenario is equally productive. The best tabletops share common features.

They are realistic

A scenario that matches a plausible situation for the specific organization produces more learning than a dramatic generic exercise. A church in Naples rehearsing a medical emergency during communion is more useful than the same church rehearsing a nuclear accident.

They are role-specific

The scenario requires participants to act in their actual roles, making the decisions they would actually face. Generic “think about what your team would do” prompts produce generic answers. “You are the children’s ministry director, and you have just received this specific report” produces actionable insight.

They have injects

Well-designed tabletops include “injects,” unexpected developments the facilitator adds partway through to change the scenario. The injects test whether the team can adapt, not just whether they can execute the first plan.

They end with action

Every tabletop should conclude with a written list of follow-up actions and assigned owners. If the exercise ends with “that was interesting” and no next steps, the learning evaporates within a week.

The Hurricane Ian lessons.

Before Hurricane Ian in September 2022, some Southwest Florida organizations had recently run tabletop exercises on severe weather response. Others had not. The post-Ian reviews showed a clear pattern. The organizations that had tabletopped recently activated their plans faster, with fewer protocol questions, and with clearer communication.

The tabletops themselves had not predicted the specific details of Ian. What they had produced was a team accustomed to making storm-response decisions under structured pressure. When the real storm arrived, that muscle memory carried over. Teams that had not rehearsed found themselves trying to make complex decisions for the first time during the emergency.

The proverb names the layered dynamic. Wisdom builds. Understanding establishes. Knowledge fills. Tabletop exercises contribute to each layer. They build wisdom through the act of deliberate preparation. They establish understanding through repeated practice. They fill the organization with specific knowledge about how its own team works under pressure.

Starting your first tabletop.

For organizations that have never run a tabletop before, a short path to start:

• Pick one scenario relevant to your facility. Start simple. A medical emergency during your busiest hour is a good first scenario.
• Identify 4 to 8 participants whose roles would be involved in that response
• Block 90 minutes on the calendar. Protect the time from other demands.
• Have one person facilitate (internal or external). Their job is to present the scenario and keep the discussion moving.
• Work through the scenario in phases. At each phase, ask: what do you do? Who do you call? What do you need?
• Capture every gap the discussion surfaces. Assign owners and deadlines before ending.
• Schedule the next tabletop before anyone leaves the room

The first exercise will feel rough. That is normal. By the third or fourth, the team will have developed a rhythm and language for the practice.

The P23 approach to tabletops.

When we facilitate tabletops for client organizations, we bring several things to the work:

• Scenario design informed by what we have seen at similar organizations, not generic templates
• Structured injects that test common gaps
• Facilitation that balances challenge with psychological safety
• After-action documentation that produces a written record of findings and commitments
• Knowledge transfer so the organization can begin facilitating its own tabletops over time

For ongoing fDoS clients, quarterly tabletops are part of the standard engagement. For other clients, we facilitate on an as-needed basis, typically quarterly or for specific event planning.

The regret pattern.

In every engagement we have run with a client after a significant event, the same observation surfaces: we wish we had tabletopped this sooner. The reflection is not about the specific event. It is about the general discipline. Tabletops that were not run, but should have been, show up as absences in the team’s response when it mattered.

If your organization in Fort Myers, Cape Coral, Naples, or Port Charlotte has not run a tabletop in the last year, and the thought of scheduling one produces a vague “we should, but…” response, that is the signal. The exercise itself is easy. The scheduling and the commitment are the hard parts. We would be glad to help with both.