The tabletop exercise is the workhorse of continuity and crisis programs, and for good reason. It is inexpensive, it brings the right people into one room, and it can surface gaps in roles, communication, and decision-making without disrupting operations. But many tabletop exercises share a quiet flaw: they are built to walk through the plan rather than to test it. The scenario unfolds the way the plan expects, participants describe what they would do, the facilitator nods, and everyone leaves reassured.
Reassurance is not the goal. The purpose of an exercise is to find out what is not true before a real event does. That requires deliberate design: clear objectives, explicit assumptions to challenge, scenarios that create genuine pressure, and an evaluation method that captures evidence rather than impressions.
This article sets out how to design exercises that go beyond the tabletop, whether you keep the discussion-based format or move toward more operational testing.
Why This Matters
Plans are built on assumptions, many of them unstated. The backup site will be available. The key supplier will respond within four hours. The team that restores the core system will be reachable. The data replicated overnight will be clean. Customers can be told what is happening within the hour. When an assumption is wrong, a plan that looks sound on paper can collapse in the first hours of a real event.
Exercise doctrine recognizes the need for range and rigor. The U.S. Homeland Security Exercise and Evaluation Program (HSEEP) distinguishes discussion-based exercises, such as seminars, workshops, tabletops, and games, from operations-based exercises, such as drills, functional exercises, and full-scale exercises, and sets out a cycle of design, conduct, evaluation, and improvement planning. NIST Special Publication 800-84, written for IT plans, similarly distinguishes tabletop exercises from functional exercises in which people actually perform their duties in a simulated environment. ISO 22301 requires organizations to run an exercise program that validates their business continuity strategies and solutions over time and produces documented results and improvement actions.
The common thread is that exercises are evidence-generating activities. Their value depends on whether they are designed to reveal what the organization does not yet know.
The Business Challenge
Exercise programs tend to drift toward comfort for understandable reasons.
Scenarios repeat. The same ransomware or data center outage storyline is reused because the materials already exist. Participants learn the story, not the capability.
Objectives are vague. "Test the business continuity plan" is not an objective that can be evaluated. Without specific objectives, there is no basis for deciding whether the exercise succeeded.
Facilitators protect the plan. When a participant proposes something the plan did not anticipate, a facilitator may steer back to the script rather than explore the gap.
Dependencies are assumed away. Suppliers, shared services, and other business units are represented by a line in the scenario ("assume IT restores the system") rather than by people who must actually respond.
Information is too clean. Real events begin with fragmentary, contradictory information. Exercises often hand participants a clear, complete picture from the start.
Evaluation is an afterthought. Notes are taken informally, the debrief turns into a general discussion, and the resulting report lists observations without evidence or priority.
Key Concept: Design Around Assumptions, Not Around the Plan
The most effective shift in exercise design is to start from the assumptions the organization is relying on, and then build a scenario that tests whether they hold.
Build an assumption register
Before writing any scenario, work with plan owners to list the assumptions embedded in their plans and recovery strategies. Useful prompts include:
- What must be available for this plan to work: people, sites, systems, data, suppliers, communications?
- What timing does the plan rely on, such as notification times, supplier response times, or recovery durations?
- What does the plan assume about the cause and scope of the disruption?
- What does it assume other teams or providers will do, and have they agreed?
Rate each assumption by how much the plan depends on it and how confident the organization is that it is true. The assumptions that are both critical and uncertain are where exercises add the most value.
Write objectives that can be evaluated
Turn the priority assumptions into specific objectives. For example: "Validate that the payments operations team can switch to the manual processing workaround and sustain it at peak-day volume for eight hours," or "Assess whether the crisis team can reach a decision on customer notification within sixty minutes of confirming a data compromise." Each objective should suggest what evidence would show success or failure.
Choose the right format for each objective
Not every objective needs a full-scale exercise. A spectrum of formats is available:
- Discussion-based tabletop: best for testing roles, decision-making, escalation, and coordination.
- Tabletop with live injects: adds time pressure and evolving information while remaining discussion-based.
- Functional or simulation exercise: participants carry out real tasks, such as using communication tools, activating call trees, or running workarounds, in a controlled setting.
- Technical recovery test: systems are actually failed over or restored to confirm recovery capability and timing.
- Integrated exercise: combines decision-making, operational workarounds, and technical recovery, often involving third parties.
Match the format to the objective and to the maturity of the capability. A new plan may first need a walkthrough; a mature one deserves a harder test.
From comfortable to challenging: an illustrative redesign
Consider a hypothetical regional distributor whose annual exercise has used the same storyline for three years: the primary data center loses power, the plan says operations move to the secondary site, and the tabletop confirms each team knows its steps.
A redesign starts with the assumption register. Plan owners identify three critical, uncertain assumptions: that the warehouse management system can be restored at the secondary site within six hours, that the third-party logistics provider will be notified and able to adjust collection schedules the same day, and that the operations director, who holds most of the institutional knowledge, will be available.
The new scenario begins on a Friday evening with an alert about unusual activity on the warehouse system and no confirmation of cause. Within the first hour, the technology team must decide whether to isolate the system, which would halt picking. The operations director is on a flight and unreachable. A later inject reveals that the logistics provider's escalation contact listed in the plan has left the company. The technology team runs a parallel functional test to measure how long restoration at the secondary site actually takes.
The result is uncomfortable but valuable: the exercise shows the restoration takes far longer than the plan states, the escalation path to the supplier is broken, and decision-making stalls without one individual. None of those findings would have surfaced from the original tabletop.
The facilitator's role
Facilitation shapes what an exercise reveals. A good facilitator keeps the scenario moving, holds participants to realistic timing, and probes vague answers ("Who specifically makes that call? How would you reach them at 2 a.m.?"). When participants find a gap, the facilitator lets them sit with it long enough to understand its consequences rather than rescuing them. Where possible, use a facilitator who is independent of the plan being tested, so there is no instinct to protect it.
What Organizations Should Do
Design scenarios that are severe but plausible
The phrase used by UK regulators for operational resilience testing is a good design principle for any organization. A scenario should be serious enough to stretch the capability but realistic enough that participants accept it. Ground scenarios in your own dependency map, recent incidents in your sector, and threat intelligence. Consider compound events, such as a cyber incident that coincides with the absence of key staff, or a supplier failure during a seasonal peak.
Engineer the information flow
Start with partial, uncertain information and let the picture develop. Introduce injects that create dilemmas rather than just new facts: conflicting reports from different sources, a journalist's inquiry before the facts are confirmed, a regulator's request for an update, or a supplier who is slow to respond. Plan injects that are triggered by participants' decisions, so the scenario responds to what they do.
Bring dependencies into the room
Where a plan depends on another team or a third party, invite them to play their role rather than assuming their response. Joint exercises with critical suppliers are particularly valuable, because they test notification paths, contractual commitments, and recovery coordination that are otherwise taken on trust.
Include elements of surprise
Consider limited-notice or no-notice elements where practical: an exercise that starts outside normal hours, unannounced unavailability of a key participant, or a requirement to work without a primary tool. Surprise reveals dependencies on specific individuals and on preparation time that real events will not provide.
Plan the evaluation before the exercise
Assign observers with clear evaluation guides linked to each objective. Ask them to record what happened, when, and why, not just whether it went well. Capture timestamps for key decisions and actions. After the exercise, compare performance with the objectives and with the assumptions you set out to test, and record which assumptions were confirmed, disproved, or left untested.
Keep a multi-year program view
Map exercises over a two- to three-year horizon so that the most critical services and the most uncertain assumptions are tested first and most often, formats increase in realism over time, and scenarios vary. Record what each exercise covered so gaps in coverage are visible.
Leadership Considerations
Ask what the exercise is trying to disprove. When an exercise is proposed, a useful leadership question is: which assumption are we testing, and what would we do if it turned out to be false?
Accept discomfort. A well-designed exercise will make some participants uncomfortable and will produce findings that reflect poorly on current arrangements. That is the return on the investment. Leaders should make clear that exposing weaknesses is the point.
Protect time for participation. Realistic exercises require the people who would actually respond, including senior leaders and technical specialists. Treat exercise participation as part of the job, not an optional extra.
Fund operational testing where it matters. Discussion-based exercises are valuable but limited. For the most critical services, invest in functional and technical tests that show whether recovery actually works.
Look for patterns. Across several exercises, the same issues often recur: unclear decision rights, poor situational awareness, over-reliance on specific people. These patterns deserve leadership attention because they usually point to structural causes.
How OpResONE Can Help
OpResONE designs and facilitates exercises that go beyond simple tabletop walkthroughs. We work with your teams to build assumption registers, write objectives that can be evaluated, develop severe but plausible scenarios grounded in your dependencies, and design injects that create realistic pressure. We can facilitate discussion-based exercises, functional simulations, and integrated tests involving technology teams and critical suppliers.
Every exercise we run is evaluated against its objectives, with findings tied to the assumptions tested and turned into prioritized, owned actions. We also help organizations plan multi-year exercise programs aligned with standards such as ISO 22301.
Related Resources
- Scenario Testing & Exercises advisory
- Business Continuity advisory
- Why Testing Matters
- Rehearsing Decisions Under Pressure
- Scenario Testing & Exercise Planning Checklist
Put Your Assumptions to the Test
If your exercises tend to confirm the plan rather than challenge it, a different design approach can change what you learn. Schedule a Strategy Call to discuss your exercise program and the assumptions most worth testing.
Sources
- FEMA, "Homeland Security Exercise and Evaluation Program (HSEEP) Doctrine," 2020 revision (discussion-based and operations-based exercises; AAR/IP)
- NIST SP 800-84, "Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities"
- ISO, "ISO 22301:2019 Security and resilience — Business continuity management systems — Requirements" (exercise programme, clause 8.5)
- Financial Conduct Authority, "Operational resilience" (severe but plausible scenarios)

