Workbench tool · Decisions
Executive Decision Brief
A compact working record for decisions that cross functions, carry meaningful uncertainty or need a clear approval and review point.
Blank structure
The tool supports the reasoning. It is not the reasoning itself.
Use the brief when a decision is important enough to deserve a clear evidence base but not complex enough to justify a long paper.
Executive Decision Brief
Reusable decision aid · One-page working record
Decision
Decision to be made. Decision owner · Required date · Authority level.
Why now
Why the decision is needed at this point, and what becomes harder or more expensive if it is delayed.
Evidence
Known · Assumed · Missing · Source confidence.
Uncertainty
What could materially change the choice, how likely that information is to improve, and when it may resolve.
Options
Viable alternatives, constraints, trade-offs and the consequence of doing nothing.
Recommendation
Preferred option and why it is more defensible than the alternatives under current evidence.
Commitment
Decision taken · Action owner · Due date · Evidence expected.
Reopen if
Name the evidence, threshold or changed condition that would justify reopening the decision. A review date alone is not a trigger.
Outcome check
What result should this decision produce, when can it reasonably be observed, and what evidence will show whether the underlying assumption held.
A decision brief should make it difficult to leave a meeting with “we’ll keep an eye on it” as the only commitment—and equally difficult to return three months later without asking whether the decision actually worked.
Where it earns its keep
Use it for: cross-functional decisions, risk acceptance, scope choices, portfolio trade-offs, management review and decisions that may need to be revisited when evidence changes.
Do not use it for: routine approvals where the decision rules are already clear, or as a substitute for analysis when the real issue is unresolved evidence.
Quality test: a reviewer should be able to understand what was decided, who had authority, what was known at the time, which uncertainty mattered, what would cause the decision to be reopened, and later whether the decision produced what management expected.
Illustrative example
Shutdown readiness decision
Synthetic example only · No client data · No externally validated result implied
Decision: whether to proceed with a planned shutdown while two critical spares remain in transit. Owner: accountable operations role. Authority: designated shutdown approval authority.
Why now: contractor mobilization and the operating window make delay increasingly expensive after the next review point.
Evidence: most workpacks are ready and the contractor is committed. The affected scope is assumed isolatable without undermining shutdown objectives. Final logistics confidence for two spares is still missing.
Uncertainty: whether the spares arrive before the point of no return and whether the affected scope can be isolated safely if they do not.
Options: proceed with contingency, reduce scope, or defer. Doing nothing is not neutral: mobilization cost and schedule exposure continue to rise while the decision remains implicit.
Recommendation: proceed only if the logistics checkpoint confirms the agreed confidence threshold; otherwise reduce scope under the pre-agreed contingency. This is illustrative decision logic, not an operational recommendation.
Commitment: record the authorized option, named action owner, due date, contingency actions and the next evidence expected from logistics.
Reopen if: confirmed spare status falls below the agreed logistics threshold, the isolation assumption fails, or the operating window changes materially. Reopen because the decision basis changed—not because another meeting appeared on the calendar.
Outcome check: after the logistics checkpoint and again after the shutdown window, compare actual spare status, scope delivered, disruption and residual exposure with the assumptions recorded here.