1. Why Public Diplomacy Exists (For Non‑PD Officers)

Public Diplomacy (PD) exists to translate U.S. policy and values into understandable, credible, and locally resonant communication with foreign publics. It is not marketing, propaganda, or event planning. It is a policy-support function that operates in the public domain, where missteps are visible, durable, and amplifiable.

At post, PD:

  • Explains U.S. policy priorities to foreign audiences
  • Listens to public sentiment and reports it back into policy channels
  • Shapes the information environment in which U.S. actions are interpreted

PD does not:

  • Set policy
  • Speak independently of U.S. Government positions
  • Optimize for popularity at the expense of accuracy or coherence

Why leadership should care:

  • Poor PD creates policy friction, reputational damage, and FO clean‑up work
  • Good PD reduces misunderstandings, absorbs shocks, and preserves maneuvering space

2. How PD Interfaces With the Front Office (Authority & Escalation)

PD operates under delegated authority but within clear escalation boundaries. Its value depends on judgment, not volume of output.

Decision Authority

  • Routine PD outputs (standard social media, cultural programming, factual amplification) are executed under PD section authority
  • Content touching on elections, security, trade, sanctions, religion, or high‑salience bilateral tensions requires FO awareness and, in many cases, explicit clearance

Escalation Triggers

Escalation to FO is required when a product:

  • Interprets policy rather than restates it
  • Could be construed as endorsing or criticizing a political actor
  • Introduces new framing not already used by Washington
  • Is likely to generate domestic backlash or international press pickup

Refusal Norms

PD officers (FSO or LES) are expected to pause or refuse execution when:

  • Clearance is ambiguous or incomplete
  • The product optimizes for speed at the expense of accuracy
  • The product creates asymmetric reputational risk for the Mission

Refusal is not obstruction; it is a governance function.

Front Office Expectations

Leadership should expect PD to:

  • Flag risk early
  • Offer alternatives, not just objections
  • Preserve institutional credibility over short‑term engagement metrics

Leadership should not expect PD to:

  • “Just post it” under time pressure
  • Retroactively fix policy ambiguity
  • Absorb blame for unclear tasking

(Training modules will build on this foundation: pre‑production judgment, clearance discipline, and post‑release risk management.)