Decision Support and Synchronization

Learning goal: understand how decision support and synchronization artifacts turn uncertainty into executable coordination.

Decision support: turn uncertainty into explicit triggers

The purpose of decision support is to prevent last-minute decisions made without the right information [usarmy2019adp5_0]. You do this by pre-identifying:

• decision points,
• triggers (what observable change means you must decide),
• information requirements,
• and pre-planned actions.

A disciplined way to express information requirements is through CCIR: a small set of PIR and FFIR tightly tied to decision points.

If a question is not tied to a decision, it is probably not a CCIR.

Synchronization: make distributed actions converge

Synchronization is not “coordination in general.” It is aligning time, space, and priorities so multiple units’ actions add up.

A synchronization matrix typically aligns:

• phases,
• tasks by unit or function,
• key events,
• decision points,
• and constraints and priorities.

The point is convergence: the minimum set of rules that keeps distributed action coherent.

Exercise

Create a minimal DSM:

• 5 decision points,
• each with a trigger,
• who decides,
• what action follows.

Then create a minimal synchronization matrix with three phases and three units or functions.