How decisions are made, documented, revisited, and closed in an embassy environment
1) What this artifact is
A staff-facing operational guide for making decisions in a way that prevents the most common embassy failure: everyone talked, nobody decided, nobody remembers what was decided, and the same issue returns next week.
“Decision hygiene” is the set of practices that ensure a decision has:
- a named decision-owner (authority),
- a clear scope,
- a record (lightweight, usable),
- follow-through,
- and a closure condition.
This is not a theory of leadership. It is a practical method to reduce churn, surprise, and blame.
2) Who it is for
- FSOs and LES who prepare options, drafts, or recommendations
- Supervisors who must decide, defer, or elevate
- PD teams handling fast-moving issues with reputational risk
- Any section where recurring debates or unclear guidance consume time
3) How the work actually functions (process)
A) A “decision” is not a discussion outcome
A decision exists only when the following are true:
- Someone with authority is identified as the decision-maker
- The decision is expressed as a clear statement (“We will do X / not do Y”)
- The decision has scope (what it covers and what it does not)
- The decision has a time horizon (effective until when, or when it will be revisited)
- The decision has an owner for execution (who does what next)
If any one of these is missing, you do not have a decision—you have a conversation.
B) The two decision types that drive speed and risk
Use this classification to avoid over-clearing small choices and under-clearing big ones:
- Type 1 (Hard to reverse): once done, it’s costly or politically damaging to undo
Examples: public statements, formal commitments to partners, high-profile engagements - Type 2 (Easy to reverse): can be adjusted with limited cost
Examples: internal workflow changes, draft iterations, scheduling choices
Mechanism:
Type 1 decisions require tighter authority/clearance and more deliberate documentation.
Type 2 decisions can be made faster—but still need a named owner and closure.
C) The minimum viable “decision record”
Embassies often fail by treating documentation as either:
- a full memo nobody reads, or
- nothing at all.
Decision hygiene uses a short decision record that is easy to create and retrieve.
A usable decision record answers:
- What was decided?
- Who decided?
- When does it take effect?
- Who executes?
- When do we revisit (if ever)?
This can be one email, one Teams message, or one line in a tracker—if it contains the above.
D) Decision closure: when something stops being debated
The institution needs a rule for when discussion ends.
A decision is “closed” when:
- the decision-maker states it,
- execution begins,
- and new discussion requires new facts, new risk, or new authority, not recycled opinions.
If people can reopen decisions just by re-arguing, the organization trains itself into churn.
E) Escalation vs. deferral: two different moves
Embassy teams confuse these constantly.
- Escalation = “This must be decided at a higher level, now or by a deadline.”
- Deferral = “We are intentionally not deciding yet, and here is the trigger for deciding.”
Both are legitimate. Both require explicit language.
4) Common failure patterns (paired with corrections)
Failure 1: “We all agree”
What happens: staff treat apparent consensus as a decision. Later, someone denies it.
Correction: “Agree” must be translated into a decision statement with a named decider.
Fix language:
“Decision: We will do X. Decider: [Name/Role]. Effective: [Date]. Owner: [Name].”
Failure 2: Decisions made implicitly (and later weaponized)
What happens: a supervisor hints, staff act, then get blamed for “misunderstanding.”
Correction: Staff should request explicit confirmation in writing.
Fix language:
“Confirming direction: proceed with X by Y date. If incorrect, please advise.”
Failure 3: “Let’s circle back” becomes permanent
What happens: the same issue returns repeatedly because deferral triggers are never defined.
Correction: Every deferral must include a trigger and a date.
Fix language:
“We are deferring until we receive [info] or until [date], whichever comes first.”
Failure 4: No owner (monkey transfer without consent)
What happens: decisions become “everybody’s responsibility,” so nobody executes.
Correction: Assign one execution owner and keep “helpers” distinct.
5) Realistic scenarios (≥3)
Scenario 1: PD press guidance under deadline
A journalist asks for comment in 30 minutes. PD team discusses options.
Failure mode: lots of discussion, no decision, someone improvises.
Decision hygiene response:
- Name the decider (PAO / FO depending on topic)
- Classify as Type 1 (public-facing, hard to reverse)
- Use a holding line if no cleared line exists
- Record the decision and who executes follow-up
Decision record example (one-line):
“Decision (PAO): Use holding line A; no additional comment. Owner (LES): send to journalist by 4:15pm; log query; revisit if FO provides updated guidance.”
Scenario 2: Conflicting priorities from two supervisors
An LES receives urgent requests from POL and PD.
Failure mode: silent overload, missed deadline, blame later.
Decision hygiene response:
- Raise the conflict explicitly as a decision request
- Ask the higher authority (or primary supervisor) to set priority
- Document the prioritization decision
Email language:
“Two urgent tasks conflict. Decision needed: which takes priority today? If Task A is priority, Task B will slip until tomorrow.”
Scenario 3: Recurring weekly meeting debate
A team repeatedly debates the same outreach strategy.
Failure mode: churn; no closure; staff stop taking discussion seriously.
Decision hygiene response:
- Force a decision statement
- Define closure and review date
Decision record:
“Decision (Section Chief): We will pursue Strategy B for 60 days. Review on [date] with metrics X/Y. Until review, we do not reopen unless new constraints emerge.”
6) Checklists / templates (≥2)
Checklist 1: The 30-Second Decision Test
Before you leave a meeting or end a thread, confirm:
- Who is the decider?
- What exactly was decided (one sentence)?
- Scope: what does this cover / not cover?
- Who owns execution?
- By when?
- Is there a revisit date or trigger?
If you cannot answer these, you don’t have a decision.
Template 2: Minimum Viable Decision Record
Use this in an email, Teams message, or tracker entry:
Decision:
Decider (role):
Date/time:
Scope (includes/excludes):
Execution owner:
Deadline:
Revisit trigger/date (if any):
7) What not to assume / not to do
Do not assume
- “everyone nodded” means decided
- silence means approval
- agreement in a meeting will be remembered later
- execution will happen without an owner
Do not do
- reopen decisions by re-arguing instead of bringing new facts
- assign responsibility to a group (“we”)
- let decision authority remain ambiguous
- skip recording Type 1 decisions
Member discussion: