For Video, Social Media, and External-Facing Products (USG / Embassy)

Purpose:
Create a living institutional memory that helps staff recognize quality, risk, and failure before publication—without turning into a punitive archive or a rigid style guide.

This is about pattern recognition, not rule enforcement.

I. What This Library Is (and Is Not)

It IS

  • A practical decision aid
  • A shared baseline for judgment
  • A way to surface why something worked or failed
  • A protection against institutional amnesia

It is NOT

  • A training manual
  • A compliance checklist
  • A naming-and-shaming archive
  • A substitute for policy clearance

II. Structure of the Reference Library

Each entry should be short, legible, and comparative.

Core Fields (Required)

  1. Product Type
    • Video (long-form / short-form)
    • Social media post
    • Graphic / carousel
    • Statement / caption
  2. Audience
    • Local foreign public
    • Media
    • Students / youth
    • Government / elite
    • Mixed (flag as risky)
  3. Outcome Classification
    • ✅ Worked
    • ⚠️ Risky but acceptable
    • ❌ Failed / pulled / corrected
  4. Why It Landed That Way (1–3 bullets)
    • Language choice
    • Visual framing
    • Compression issue
    • Context mismatch
    • Policy ambiguity
  5. Lesson (One Sentence)
    • “Shortened captions can change policy meaning.”
    • “Neutral tone prevented misinterpretation.”
    • “Visuals implied endorsement not stated in text.”

III. Categories of Examples to Include

A. Clear Wins

Include these first so the library isn’t fear-driven.

Examples:

  • Videos that explain policy without promising outcomes
  • Posts that humanize issues without politicizing them
  • Content that survived controversy unchanged

Why they matter:
They model what to do, not just what to avoid.

B. Risky but Approved

These are the most valuable entries.

Examples:

  • Products that required Front Office clearance
  • Posts that generated strong reactions but stayed accurate
  • Content that pushed tone boundaries responsibly

Why they matter:
They teach judgment under constraint, not obedience.

C. Failures / Pullbacks

Handle with care.

Include only:

  • What went wrong
  • Where the failure occurred (language, visuals, assumptions)
  • What rule would have stopped it earlier

Exclude:

  • Names
  • Blame
  • Internal drama

Rule:
If the lesson isn’t clear, don’t include the example.

IV. Special Section: “Looks Fine, Isn’t”

This section prevents false confidence.

Examples:

  • Grammatically correct posts that implied policy
  • Neutral videos that became misleading when clipped
  • Accurate facts placed in misleading sequences

Tag these explicitly as:

“Passed review, failed context.”

V. How This Library Is Used (Operationally)

1. During Planning

  • Teams skim 2–3 relevant examples
  • Ask: Which pattern does our product resemble?

2. During Review

Reviewer references an entry:

“This resembles Example X — same compression risk.”

3. During Escalation

  • Attach one comparable example to escalation note
  • Keeps debate concrete, not abstract

VI. Governance Rules for the Library

Ownership

  • Maintained by PD / Comms lead
  • Reviewed quarterly, not continuously

Admission Threshold

  • Entry only if there is a clear lesson
  • Not every product belongs here

Sunset Rule

  • Entries reviewed annually
  • Retire outdated platform norms

VII. Why This Works Institutionally

  • Converts tacit knowledge into shared memory
  • Reduces over-reliance on senior reviewers
  • Improves junior staff judgment faster
  • Shifts review from “I feel” to “We’ve seen this”

This is how institutions learn without freezing.