Subtitle: How missions lose knowledge—and how to stop relearning the same lessons every two years

1) What this artifact is

A training and reference artifact defining how institutional memory should be captured, transferred, and used in a high-rotation embassy environment.

This integrates:

  • documentation as protection,
  • root-cause awareness,
  • workload continuity,
  • and evaluation alignment.

It exists because rotation without memory is institutional amnesia, and amnesia recreates OIG-level failures.

2) Who it is for

  • Incoming and outgoing FSOs
  • LES who provide continuity
  • Supervisors inheriting teams
  • PD sections with external relationships

3) How the work actually functions (process)

A) What must be handed over (minimum viable memory)

  1. Active decisions (what was decided and why)
  2. Unresolved problems (with root causes identified)
  3. External sensitivities (media, political, cultural)
  4. Invisible dependencies (who actually keeps things running)

Anything else is secondary.

B) Memory must be explicit, not personal

When knowledge lives only in:

  • inboxes,
  • WhatsApp,
  • or one LES’s head,

the institution becomes fragile and unfair.

4) Common failure patterns (paired with corrections)

Failure: “My predecessor didn’t leave notes.”
Correction: Require handover as part of exit.

Failure: LES expected to brief repeatedly.
Correction: Write once; reuse.

5) Complex scenario (Bangladesh-relevant)

Scenario: Media relationships reset badly

  • New PAO arrives.
  • Long-standing Bangladeshi editors feel ignored.
  • Prior tensions around Digital Security Act coverage resurface.
  • LES had managed relationships quietly.

Variants involved:
Institutional memory, documentation, escalation, favoritism perception.

Corrective mechanism:

  • Handover document flagged “sensitive media relationships”
  • Early FO-cleared engagement
  • LES credited and positioned as continuity lead

6) Template

Handover Snapshot

Active decisions:
Unresolved issues:
Sensitive relationships:
Continuity dependencies:
What I would warn my successor about:

7) What not to assume / not to do

  • Do not assume memory transfers informally.
  • Do not rely on LES to “just explain later.”
  • Do not treat handover as optional.