A successful exercise is one that reveals a gap
"Everything went well" is a negative signal. Here is how to design an exercise that produces usable information.
The report that says nothing
An exercise report concluding "everything went well" signals one of two things: either the exercise was too easy, or the findings were not recorded. Either way, ISO 22301 clause 8.5 is not satisfied: it expects gaps and their treatment.
Three design defects explain almost all such reports.
Defect 1: unmeasurable objectives
"Test the continuity plan" is not an objective: you will not know whether it was achieved. "Measure the time to assemble the crisis team out of hours" is one — it yields a duration. "Verify the holding statement is published within sixty minutes" is another — it yields a yes or no. "Identify the decisions the team cannot take without the CEO" is a third — it yields a list.
Three to five objectives suffice. Beyond that, observation scatters and nothing is measured properly.
Defect 2: injects that inform instead of forcing
"The service is still down" produces no decision. "The provider announces restoration at ten in the evening; client services asks whether to notify the four thousand affected clients now or wait" creates a dilemma: two options, each with a cost.
It is in those trade-offs that you observe the team's real capability. One inject every ten to fifteen minutes in the active phase; closer together and participants absorb without deciding.
Defect 3: improvised evaluation
Without a grid prepared before the exercise and handed to observers, the debrief produces impressions. With one, it produces measures comparable across exercises: assembly time, publication time of the first message, number of timestamped log entries, whether a twenty-four-hour horizon topic was addressed.
The hot debrief, in the right order
Fifteen to thirty minutes, immediately after, before everyone rebuilds the narrative. Three questions, in this precise order: how did it feel?, what was missing?, what must change?
The order matters. Starting with technical analysis blocks expression, and the most useful findings — "I didn't know I was allowed to decide that" — never surface.
The loop that makes the difference
Each finding becomes an action with an owner and a date. Follow-up is presented to the committee that steers continuity, not filed in the report. And the next exercise explicitly verifies that the previous actions had an effect.
That final loop is what turns an exercise programme into measurable improvement rather than an annual repetition.
Also worth reading
The RTO nobody had tested
A declared four-hour RTO, an exercise measured at four hours forty-seven, and three time items almost no plan counts.
Why your BIA bogs down, and how to unblock it
A hundred and twenty questionnaires, six months, and a table where every activity is four-hour critical. The cause is a sequencing error.