Why Embassies Systematically Undervalue Their Most Critical Knowledge Asset
The comforting cliché — and why it’s dangerous
Embassies often say:
“Our LES are the backbone of the mission.”
This statement is usually sincere. It is also usually operationally meaningless.
Calling LES the “backbone” suggests strength and support, but it obscures what LES actually provide — and what embassies quietly extract from them without protecting or formalizing it.
LES are not simply support staff, cultural translators, or continuity placeholders between FSO rotations.
LES are institutional memory embedded in people.
When that memory is not structurally integrated, embassies become brittle, repetitive, and prone to rediscovering the same problems every two to three years.
What institutional memory actually is (and is not)
Institutional memory is not:
- knowing where files are stored,
- remembering how to use systems,
- or recalling names and dates.
Institutional memory is:
- knowing how similar situations unfolded before,
- understanding which actors behaved predictably and which did not,
- remembering which “reasonable” solutions quietly failed,
- and recognizing early warning signs that are invisible to newcomers.
This memory is not written down because:
- much of it is experiential,
- much of it involves informal dynamics,
- and much of it lives at the boundary of what can be safely documented.
LES carry this memory because they:
- remain while FSOs rotate,
- experience long arcs of local politics,
- and observe consequences long after decisions are made.
How embassies actually use LES memory (informally)
In practice, embassies rely on LES memory constantly — but rarely admit it structurally.
Examples:
- “Has this outlet caused trouble before?”
- “Did we try this kind of event in the past?”
- “How did the host government react last time?”
- “Who should we not surprise with this?”
These questions are often asked:
- in hallways,
- over coffee,
- quietly before meetings,
- or after something goes wrong.
The answers shape decisions — but remain undocumented, unacknowledged, and unrewarded.
When LES leave, retire, or disengage, that memory disappears.
The institution then mistakes its own ignorance for novelty.
Why this is worse in Public Diplomacy than elsewhere
PD is especially vulnerable to memory loss because:
- it deals with perception rather than transactions,
- its effects are cumulative rather than immediate,
- and its failures often appear delayed or indirect.
In PD:
- a misinterpreted statement today can resurface months later,
- a partner praised once may assume future endorsement,
- silence during one crisis can redefine expectations in the next.
LES often remember:
- which narratives recur,
- which grievances never fully resolve,
- and which audiences react strongly to symbolic signals.
When this memory is excluded from planning, PD outputs become technically correct but locally naive.
The structural error: treating LES knowledge as advisory, not operational
A common institutional pattern:
- LES knowledge is welcomed as “input.”
- Final decisions are made elsewhere.
- LES concerns are framed as “perspective,” not risk.
- When consequences occur, LES say, quietly, “We warned about this.”
This is not because LES seek control.
It is because they recognize pattern recurrence.
Institutions discount pattern recognition because it feels subjective — until it proves accurate.
Why “just document it” doesn’t work
Leadership often responds to memory loss by saying:
“We should document lessons learned.”
This helps — but it is insufficient.
Much LES knowledge:
- cannot be fully decontextualized,
- loses force when written abstractly,
- or becomes politically sensitive when formalized.
Documentation without role recognition still treats memory as optional.
The issue is not storage.
It is authority to be heard early.
What structural integration actually looks like
Treating LES as institutional memory requires more than consultation.
It means:
- involving LES at the problem-definition stage, not just solution review,
- asking LES to identify recurring patterns before options are framed,
- creating safe mechanisms for LES to flag “this has gone wrong before” without needing proof.
It also means:
- recording LES assessments alongside decisions,
- not dismissing concerns because they lack documentary citation,
- and recognizing that “experience-based warnings” are a legitimate analytic input.
LES memory and risk detection
LES are often the first to detect:
- when language will be read as endorsement,
- when silence will be read as confirmation,
- when a partner will over-interpret access,
- when a media outlet is positioning a story strategically.
These are not messaging critiques.
They are risk forecasts.
Ignoring them does not eliminate the risk — it simply shifts responsibility upward.
The cost of not protecting LES memory
When LES memory is not structurally integrated:
- FSOs repeat avoidable mistakes,
- PD posture oscillates unpredictably,
- trust erodes internally,
- and LES disengage from proactive problem-solving.
Over time, LES stop warning early — because warnings are exhausting when ignored.
At that point, the institution loses its early-warning system.
What this means for PD leadership and SPES
For PAOs and SPES, LES memory is not a nice-to-have.
It is mission-critical intelligence.
Your role includes:
- legitimizing experiential knowledge,
- translating it into risk language leadership understands,
- and protecting LES from having to “prove” what they know intuitively.
If LES feel they must justify every concern as if it were an opinion, the institution has already failed.
Bottom line
LES are not just staff who happen to stay longer.
They are the only continuous observers of institutional consequence.
Public Diplomacy that does not structurally integrate LES memory will appear competent until it suddenly is not — and by then, the warning signs will feel obvious in retrospect.
The institution’s choice is simple:
Either treat LES memory as an operational asset —
or keep paying for its absence, one avoidable incident at a time.
Member discussion: