Several decisions may address a single problem

In a fictional crisis exercise, a team decides to secure a damaged site, control access and arrange regular checks of the safeguards. The log contains three decisions. Meanwhile, the loss of another operating function remains unaddressed. Counting decisions alone obscures the difference between several work steps and several problems receiving attention.

My conference manuscript “The Decision Corridor: An Exploratory Rubric for Reviewing Temporal Actionability in Crisis Management Team Decisions” (Rico Kerstan, version dated 29 May 2026) develops an exploratory review rubric. The decision corridor denotes plausible, actionable paths under the scenario conditions. In the study, ten positively classified decision episodes form six connected decision complexes.

A positive decision complex groups temporally connected episodes that fall within the corridor and address the same scenario problem. This prevents related measures from appearing as independent performance successes. A broader spread of complexes has not been shown to improve team performance. I recommend extending problem-based grouping to the whole decision log without thereby classifying every assignment as within the corridor.

For practical reviews, I draw a distinction between two views: the decision log identifies individual assignments; a separate grouping shows which problems those assignments address. In the example, securing the site, controlling access and checking the safeguards initially belong together. This grouping also makes the unaddressed operating function visible.

The role responsible for the review should group assignments according to their purpose. An assignment may affect several problems; explain that overlap rather than automatically counting it more than once. Equally, a substantial problem should not be split artificially to make the report appear more balanced. The relevant question is which developing situation the team intended to influence.

For the next crisis exercise, I recommend reviewing one decision log with the team lead and grouping its entries by problem. The debrief can then examine the distribution of attention, including reasons for deliberately deferring a problem and responsibility for returning to it, rather than infer performance from decision counts.