Use this when
proposals collect discussion but do not move reliably into decisions, broadcast, and execution.
Advanced practitioner depth
Layer 03 · Communication · Communication Architecture
Decision Flow System
Executive summary
Route decision communication through propose, consult, synthesize, decide, and broadcast. This advanced practitioner guide places that work inside Communication Architecture. It helps leaders turn a broad concern into a specific operating decision without treating the topic as a stand-alone transformation. Use the detailed model below to clarify the current state, make trade-offs visible, and assign ownership for the next move. Apply it when proposals collect discussion but do not move reliably into decisions, broadcast, and execution. The practical result is a decision communication flow from proposal through consultation, commitment, and broadcast. Keep that output connected to adjacent layers so upstream constraints remain visible and downstream execution can show whether the design is working.
Practical output
Leave with a decision communication flow from proposal through consultation, commitment, and broadcast.
Detailed model
How to apply decision flow system
Use the practitioner material below after the executive orientation establishes the job, trigger, and expected output.
Five Stages
No major decision moves to execution without structured communication.
The five-stage flow turns communication into a pipeline for context, input, commitment, and broadcast.
01
Propose
Decision owner submits a written brief with context, options, risks, deadline, and requested input. No brief, no decision.
02
Consult
Stakeholders respond within a defined window. Input is structured, time-boxed, and tied to the decision.
03
Synthesize
Objections, dependencies, assumptions, and conditions are surfaced before the commit window closes.
04
Decide
One accountable owner commits. Rationale, date, confidence, and constraints are recorded.
05
Broadcast
The decision is published to impacted teams and stored permanently in the system of record.
Leader Moves
How leaders apply Layer 3.
Define which channel types exist and what each is for. Then enforce it across the organization.
No major decision moves to execution without a written artifact on record.
Every recurring decision meeting gets replaced with a structured async review window when the decision is routine and reversible.
Every tool, channel, and forum has a named owner with clear accountability.
Stop measuring meeting volume. Start measuring decision latency.
Choose the next path
Return to the layer or apply this topic to the operating model.
The layer overview restores context. The recommended action turns this practitioner model into the next piece of work.