Decision Support as Anti-Surprise Infrastructure
Most operational failure does not look like ignorance. It looks like late recognition: a commander recognizes the decision point only after the window to act has narrowed.
Decision support is the infrastructure that prevents late recognition. It does not eliminate uncertainty. It formats uncertainty into explicit triggers.
The core pattern
- Decision point. A choice among options that changes the plan.
- Trigger. An observable change that indicates the decision must be made.
- Information requirement. What must be known to decide.
- Authority. Who decides if the commander is unavailable.
- Action. What happens when the trigger occurs.
A DSM/DST is just a way of forcing these to be explicit.
Why this matters for mission command
Mission command is not “decentralize everything.” It is decentralize execution with constraints. Decision support makes those constraints concrete: which choices are delegated, what triggers matter, and what reporting is required.