Who Actually Owns What in Embassy Public Diplomacy — and Why This Keeps Breaking

The recurring failure pattern

Most embassy public-facing failures do not occur because someone acted in bad faith, lacked intelligence, or violated policy. They occur because authority, voice, and risk are misaligned, and the institution quietly allows that misalignment to persist.

The pattern is familiar:

  • A program needs visibility.
  • A post is drafted.
  • PAO clears for style and tone.
  • Legal says “be careful.”
  • Leadership wants speed.
  • The content goes out.
  • Something escalates.

Afterward:

  • No one is sure who “owned” the decision.
  • Everyone can explain their narrow role.
  • The institution absorbs the cost.

This is not a people problem. It is a structural problem.

Three different things that are constantly confused

In embassy operations, three concepts are often treated as interchangeable. They are not.

  1. Authority
  2. Voice
  3. Risk

Understanding the difference — and how they interact — is foundational to competent PD practice.

1. Authority: who has the right to decide

Authority is formal and bounded.

It comes from:

  • position,
  • delegation,
  • law,
  • and policy.

Authority answers questions like:

  • Who can approve a statement?
  • Who can commit the Embassy to a position?
  • Who can bind the institution?

Authority is scarce and usually sits with:

  • the Ambassador,
  • the DCM,
  • or explicitly delegated officers.

Most PD outputs are produced far from authority.

That is not a flaw — but it creates risk if not acknowledged.

2. Voice: who speaks in public

Voice is operational, not formal.

Anyone who drafts, posts, briefs, or speaks contributes to institutional voice:

  • PAO
  • SPES
  • PD officers
  • Program officers
  • Sometimes even LES managing platforms

Voice answers:

  • Who is perceived as speaking for the Embassy?
  • Whose words circulate?
  • Whose language gets quoted?

Crucially:

Voice is often exercised by people without authority.

This is unavoidable — and manageable — if risk is owned correctly.

3. Risk: who absorbs consequences

Risk is neither formal nor visible.

Risk answers:

  • Who deals with fallout?
  • Who explains to Washington?
  • Who manages host-government reaction?
  • Who repairs damaged relationships?

Risk is almost always absorbed by:

  • the Front Office,
  • PAO,
  • or the Ambassador — regardless of who drafted the content.

Risk travels upward and outward.
Authority does not automatically follow it.

The core institutional problem

The central PD failure is this:

Voice is exercised downstream, risk is absorbed upstream, and authority sits somewhere else entirely.

When these three are not explicitly aligned, institutions rely on assumptions instead of decisions.

Common assumptions include:

  • “If PAO cleared it, it’s safe.”
  • “If Legal didn’t object, it’s fine.”
  • “If the program owns it, they’ll handle fallout.”
  • “If leadership wanted it fast, they accept the risk.”

None of these are structurally true.

Why clearance chains don’t solve this

Clearance is often mistaken for risk transfer.

It is not.

  • PAO clearing for tone does not assume policy risk.
  • Legal flagging “be careful” does not own consequences.
  • A program requesting visibility does not absorb attribution risk.

Clearance chains distribute process, not responsibility.

Unless someone explicitly says:

“I am authorizing this and accept the institutional risk,”

the institution is operating on borrowed confidence.

Concrete PD examples

Example 1: Social media post naming a local partner

  • Program drafts a post praising a partner organization.
  • PAO edits for clarity.
  • Legal notes reputational sensitivity.
  • Post goes live.

Outcome:

  • Competing organizations allege favoritism.
  • Media asks whether the U.S. endorses that partner.
  • Host government inquires quietly.

Who owns this?

  • Not the program (they can’t respond officially).
  • Not PAO (they didn’t authorize endorsement).
  • Not Legal (they warned).

Risk lands on the Front Office — unassigned.

Example 2: Press guidance during an unfolding incident

  • DCM asks for “something confident.”
  • PAO proposes holding language.
  • Program insists facts are clear.
  • Washington asks, “What’s the Embassy’s position?”

If the guidance is definitive and later wrong:

  • credibility suffers,
  • correction looks like retreat,
  • trust erodes.

If the guidance is cautious:

  • leadership worries about appearing unsure.

This is not a writing problem.
It is an authority articulation problem.

What competent PD systems do differently

Competent PD operations separate drafting from decision-making and make risk ownership explicit.

They ask:

  • Who is authorizing this posture?
  • What risk is being accepted?
  • What happens if this is wrong or misused?

They document:

  • what was known,
  • what was uncertain,
  • and who chose to proceed.

This does not slow things down.
It prevents post-hoc chaos.

The SPES role in this system

SPES does not “control messaging.”

SPES:

  • identifies where voice exceeds authority,
  • flags where risk is unowned,
  • and forces explicit decisions.

SPES’s most important function is to say:

“This output implies X. Are we prepared to own that?”

This is often uncomfortable — and essential.

LES contributions here are critical

LES often see risk first because they understand:

  • how language will be interpreted,
  • which actors will exploit ambiguity,
  • and how similar situations played out before.

When LES say:

  • “This will be taken as endorsement,” or
  • “This will be misunderstood locally,”

they are describing risk propagation, not expressing opinion.

Ignoring that input shifts risk silently upward.

Why this keeps recurring

This problem persists because:

  • authority is uncomfortable to name explicitly,
  • risk is assumed to be “shared,”
  • and institutions prefer harmony over clarity.

But ambiguity does not eliminate risk.
It just delays its recognition.

Bottom line

Public Diplomacy breaks when:

  • voice is exercised without authority,
  • authority is assumed without consent,
  • and risk is absorbed without ownership.

Fixing this does not require better writing.
It requires explicit alignment of decision, voice, and consequence.

Until that alignment exists, the institution will continue to experience “surprising” failures that were structurally predictable.