Appendix 14 — Common Failure Cases & Postmortems (Anonymized)

What Actually Goes Wrong, and How SPES Intervenes

Purpose of this appendix
To document recurring, structural failure modes in Embassy public engagement—not to assign blame, but to:

  • make failure predictable rather than surprising,
  • equip SPES to intervene early,
  • and prevent the institution from relearning the same lessons each rotation.

This appendix is based on patterned institutional behavior, not hypothetical risk.

14.1 How to Read These Postmortems

Each case includes:

  • Trigger
  • What went wrong (structural, not personal)
  • Why it keeps happening
  • SPES intervention point
  • What would have prevented it

Names, dates, and locations are intentionally omitted.

14.2 Failure Case 1 — “The Overconfident Interim Brief”

Trigger
Media inquiry + Washington request + Ambassador unavailable.

What went wrong

  • DCM requested a “clean, confident” summary.
  • PAO flagged uncertainty.
  • Language removed caveats to reassure Washington.
  • Summary circulated and was later contradicted by facts.

Why it keeps happening

  • Confidence is rewarded institutionally.
  • Caution is read as indecision.
  • Interim authority gaps are uncomfortable.

SPES intervention

  • Flag authority gap explicitly.
  • Insist on holding language framing for interim briefs.
  • Document caveat removal as a risk transfer.

Preventive control

  • Mandatory “known / unknown / posture” structure for interim briefs.

14.3 Failure Case 2 — “The Defensive Program Officer”

Trigger
Allegations involving a U.S.-funded program.

What went wrong

  • Program officer insisted allegations were “misleading.”
  • Early rebuttal language drafted.
  • Later facts complicated the narrative.

Why it keeps happening

  • Program officers are emotionally invested.
  • Defensive posture feels protective.
  • Lack of separation between program integrity and comms risk.

SPES intervention

  • Separate program defense from public language.
  • Recommend holding language.
  • Escalate when rebuttal exceeds evidence.

Preventive control

  • Rule: program staff cannot clear rebuttals to allegations.

14.4 Failure Case 3 — “The Social Media Screenshot”

Trigger
Benign Facebook post about outreach activity.

What went wrong

  • Caption included values-laden phrasing.
  • Screenshot circulated stripped of context.
  • Post treated as policy endorsement.

Why it keeps happening

  • Social posts drafted for goodwill, not durability.
  • Underestimation of screenshot travel.

SPES intervention

  • Apply “screenshot survival test.”
  • Recommend neutral, descriptive captions.
  • Advise against posting at all if unnecessary.

Preventive control

  • All social captions reviewed for attribution risk.

14.5 Failure Case 4 — “PAO vs Program Ownership Standoff”

Trigger
Sensitive issue with unclear policy guidance.

What went wrong

  • PAO refused to own risk.
  • Program refused to be listed as risk owner.
  • Draft circulated without clear authority.

Why it keeps happening

  • Risk ownership is unattractive.
  • Informal processes lack accountability.

SPES intervention

  • Force explicit ownership mapping.
  • Recommend hold/defer if ownership unresolved.
  • Log refusal to own risk.

Preventive control

  • No external language without named risk owner.

14.6 Failure Case 5 — “ICS Ghost Logic”

Trigger
Messaging based on expired ICS assumptions.

What went wrong

  • Democracy-forward language used post-2025.
  • Messaging conflicted with new NSS posture.
  • Embassy exposed to policy inconsistency claims.

Why it keeps happening

  • ICS language persists culturally.
  • Staff assume continuity.

SPES intervention

  • Flag delta between ICS and current policy.
  • Recommend descriptive language only.
  • Brief Front Office on misalignment risk.

Preventive control

  • Quarterly drift memo (Appendix 13).

14.7 Failure Case 6 — “Silence Without Framing”

Trigger
Journalist inquiry not answered promptly.

What went wrong

  • No holding language issued.
  • Silence interpreted as confirmation.
  • Rumor escalated.

Why it keeps happening

  • Fear of saying the wrong thing.
  • No agreed silence protocol.

SPES intervention

  • Recommend bounded holding language.
  • Explain silence vs framed silence distinction.

Preventive control

  • Silence requires documentation or holding line.

14.8 Failure Case 7 — “Exchange Program Overreach”

Trigger
Public speech referencing exchange alumni.

What went wrong

  • Alumni framed as “future leaders.”
  • Alumni cited speech publicly.
  • Embassy accused of political grooming.

Why it keeps happening

  • Soft-power myths.
  • Pressure to show impact.

SPES intervention

  • Remove aspirational language.
  • Reinforce exchange neutrality.

Preventive control

  • Exchange language checklist (Appendix 8).

14.9 Pattern Summary (Why These Failures Repeat)

Across cases, failures stem from:

  • authority gaps,
  • time pressure,
  • emotional investment,
  • misaligned incentives,
  • and lack of shared standards.

SPES exists to interrupt these patterns.