When to meet, when not to meet, and how meetings actually produce decisions and action

1) What this artifact is

A staff-facing operational guide defining meeting discipline in an embassy context: when meetings are appropriate, how they should be structured, and how they must end to avoid wasted time, hidden workload, and unclear accountability.

This artifact addresses a recurring institutional failure: meetings that feel productive in the moment but produce no decisions, no owners, and more confusion than clarity.

This is not advice on facilitation style. It is a mechanism for converting time spent together into decisions and execution.

2) Who it is for

  • FSOs and LES who attend recurring section or interagency meetings
  • Supervisors and section chiefs who convene meetings
  • PD teams coordinating press, programming, or outreach
  • Front Office–facing staff whose meetings drive Mission action

3) How the work actually functions (process)

A) The only three legitimate reasons to hold a meeting

A meeting is justified only if at least one of the following is true:

  1. A decision must be made that requires multiple inputs
  2. Time-sensitive coordination is required across roles or sections
  3. Critical information must be shared synchronously to avoid error

If none apply, a meeting should not be held. Use email, a tracker, or bilateral conversations instead.

B) Roles that must exist in every meeting

Regardless of size or formality, effective meetings require three explicit roles:

  • Convener / Chair — responsible for purpose and time
  • Decision authority — the person who can decide (may be the same as chair)
  • Recorder — captures decisions, owners, and deadlines

If these roles are not named, meetings default into discussion without outcome.

C) Agenda discipline: purpose before topics

An effective agenda answers, at the top:

  • What decision(s) will be made?
  • What inputs are required?
  • Who will decide?

Topic lists without decision framing invite drift.

D) How meetings end (this is where most fail)

A meeting is not over until the chair states:

  • the decision(s) made,
  • the owner(s) of next actions,
  • deadlines,
  • and any items explicitly deferred (with triggers).

If participants leave with different interpretations, the meeting has failed.

E) When to stop discussion

Discussion should stop when:

  • the decision authority has sufficient input,
  • new comments are repetitive,
  • or the issue exceeds the meeting’s scope.

The chair’s role is to close discussion, not extend it to preserve harmony.

4) Common failure patterns (paired with corrections)

Failure 1: Meetings as updates

What happens: time is spent sharing information that could be read.
Correction: Require pre-read updates; use meeting time for decisions only.

Failure 2: No decision authority present

What happens: discussion ends with “we’ll take this offline.”
Correction: Do not convene decision meetings without the decider.

Failure 3: Endless discussion

What happens: fear of conflict prevents closure.
Correction: Chair explicitly ends discussion and names next steps.

Failure 4: Monkeys created in meetings

What happens: tasks emerge with no owner.
Correction: Assign one owner per action before moving on.

5) Realistic scenarios (≥3)

Scenario 1: Weekly PD coordination meeting

The team meets weekly but revisits the same outreach issues.

Failure mode: discussion without closure.
Meeting discipline response:

  • Chair states decision objective at outset
  • Decision authority identified
  • Strategy chosen for a defined period
  • Review date set

End-of-meeting statement:

“Decision: pursue Strategy B for four weeks. Owner: X. Review on [date].”

Scenario 2: Interagency meeting without FO

Participants debate a sensitive issue but no FO representative is present.

Failure mode: apparent agreement later overridden.
Meeting discipline response:

  • Chair pauses decision
  • Documents discussion as input only
  • Schedules follow-up with decision authority

Scenario 3: Long meeting, no time left

Agenda overruns; last items rushed.

Failure mode: rushed pseudo-decisions.
Meeting discipline response:

  • Chair defers remaining items explicitly
  • Assigns owners to prepare options
  • Schedules decision point

6) Checklists / templates (≥2)

Checklist 1: Should This Be a Meeting?

Hold the meeting only if:

  • A decision is required
  • Multiple inputs are necessary
  • The decider will attend

If not, cancel or redesign.

Template 2: Meeting Close-Out Summary

Send within 24 hours:

Meeting:
Date:
Decisions made:
1)
2)

Action items:
- Action:
- Owner:
- Deadline:

Deferred items (with trigger/date):

7) What not to assume / not to do

Do not assume

  • discussion equals alignment,
  • attendance equals engagement,
  • silence equals consent.

Do not do

  • convene meetings without decision authority,
  • let meetings end without explicit outcomes,
  • rely on memory instead of a close-out summary,
  • allow meetings to replace individual responsibility.