Use this when
decisions stall, disappear after meetings, or fail to produce traceable execution and feedback.
Advanced practitioner depth
Layer 02 · Decisions · Decision Architecture
The Decision Lifecycle
Executive summary
Move decisions through eight stages: frame, gather, analyze, pre-commit, decide, communicate, execute, and review. This advanced practitioner guide places that work inside Decision 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 decisions stall, disappear after meetings, or fail to produce traceable execution and feedback. The practical result is a documented decision path from framing through commitment, execution, and review. 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 documented decision path from framing through commitment, execution, and review.
Detailed model
How to apply the decision lifecycle
Use the practitioner material below after the executive orientation establishes the job, trigger, and expected output.
Eight Stages
A decision is a lifecycle, not a moment.
The decision lifecycle preserves context from framing through learning so decisions can be executed, communicated, monitored, and improved.
01
Frame
Define scope, stakes, reversibility, owner, and decision tier.
02
Gather
Collect data, signals, constraints, perspectives, and known uncertainties.
03
Analyze
Test assumptions, compare options, surface trade-offs, and identify risk.
04
Pre-Commit
Run the critical gate: tier fit, owner clarity, evidence quality, and rollback logic.
05
Decide
One human commits. AI may inform, but accountability attaches to the Decider.
06
Communicate
Broadcast the decision with context, rationale, implications, and next actions.
07
Execute
Assign work, monitor execution, track signals, and manage exceptions.
08
Review
Retrospective the decision, learn from outcomes, and update the decision architecture.
Critical Gate
Pre-commit is where decision quality becomes decision discipline.
The pre-commit gate checks tier fit, owner clarity, evidence quality, AI role, rollback logic, and communication requirements before the organization commits.
Is this decision reversible or irreversible?
Which tier does this decision belong in?
Who is the one Decider?
What evidence is required before commitment?
What can AI do: act, draft, inform, or nothing?
What is the rollback or escalation path?
How will the decision be communicated with context?
When will the decision be reviewed for learning?
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.