How responsibility quietly transfers, why it causes damage, and how to stop it in embassy work

1) What this artifact is

A staff-facing operational guide explaining the recurring embassy failure mode commonly known as “Who has the monkey” — the quiet, often invisible transfer of responsibility from the person who owns a task to someone else, without authority, clarity, or agreement.

This artifact explains:

  • what the problem actually is (mechanically),
  • how it shows up in embassy settings,
  • why it causes institutional harm,
  • and how FSOs and LES can prevent it.

This is not a personality critique. It is a workflow and authority failure analysis.

General sources (concept origin and management practice):

  • William Oncken Jr. & Donald Wass, Harvard Business Review, “Management Time: Who’s Got the Monkey?” (classic articulation of the concept)
  • Federal management guidance on accountability and delegation (OPM; GAO), applied here to embassy operations

2) Who it is for

  • FSOs who supervise LES or manage portfolios
  • LES supervisors who feel overburdened or unclear on authority
  • Staff who routinely “help out” and then get stuck owning problems
  • Anyone experiencing workload creep without formal tasking

3) How the work actually functions (process)

A) What “the monkey” actually is

The “monkey” is responsibility for next action.

It is not:

  • the task itself,
  • the background information,
  • the problem description.

It is the obligation to:

  • decide what happens next,
  • take the next step,
  • be accountable if nothing happens.

In healthy systems, the monkey stays with the person who owns the outcome, unless it is explicitly transferred.

B) How monkeys move (quietly and incorrectly)

Monkeys move when:

  1. Someone raises a problem.
  2. The listener responds with help instead of structure.
  3. The next action becomes ambiguous.
  4. Responsibility shifts without authority.

Common phrases that transfer monkeys:

  • “Let me take a look.”
  • “I’ll see what I can do.”
  • “Send it to me and I’ll handle it.”
  • “I’ll follow up.”

If authority, timeline, and ownership are not restated, the monkey has moved.

C) Why this happens in embassies

Embassy conditions make monkey transfer likely:

  • rotating leadership,
  • strong service culture (“be helpful”),
  • hierarchical discomfort,
  • unclear delegation,
  • time pressure.

LES often accumulate monkeys because they provide continuity.
FSOs often accept monkeys to avoid delay or conflict.

Neither is malicious. Both are systemic.

D) Why this causes real harm

Uncontrolled monkey transfer leads to:

  • invisible overload (especially for LES),
  • missed deadlines with unclear blame,
  • decision paralysis,
  • resentment and burnout,
  • supervisors doing subordinate work,
  • loss of accountability.

Critically: the institution loses visibility into where work is actually stuck.

4) Common failure patterns (paired with corrections)

Failure 1 — “Helping” without defining ownership

Pattern: Supervisor solves the problem personally.
Correction: Clarify who owns the next action before offering help.

Failure 2 — LES absorb responsibility to be useful

Pattern: LES take on tasks without authority.
Correction: Ask explicitly: “Do you want me to own this, or advise?”

Failure 3 — Meetings that generate monkeys

Pattern: Tasks emerge but no owner is named.
Correction: End meetings by assigning owner, deadline, and authority.

Failure 4 — Email chains with no decision point

Pattern: CCs multiply; no one acts.
Correction: State explicitly who is responsible for the next step.

5) Realistic scenarios (≥3)

Scenario 1 — “Can you just check this?”

An FSO asks an LES to “check” a draft.

Risk: LES becomes de facto owner.

Correct response:
“Happy to review — do you want feedback only, or do you want me to revise and resubmit?”

Scenario 2 — Problem raised in a meeting

Someone flags an issue; discussion follows.

Risk: Group assumes someone else will act.

Correct response (chair):
“Who owns the next step? What’s the deadline?”

Scenario 3 — Supervisor rescues a late task

A deadline slips; supervisor steps in to fix it.

Risk: Monkey permanently transfers upward.

Correct response:
Ask what blocked progress, reset ownership, and clarify expectations — do not silently take over.

6) Checklists / templates (≥2)

Checklist A — Monkey Control Questions

Before agreeing to “help,” ask:

  • Who owns the outcome?
  • What exactly is the next action?
  • Who decides?
  • By when?
  • Am I advising or owning?

If these are unclear, stop and clarify.

Template B — Explicit Ownership Language

Use this language in emails or meetings:

“I can advise on this, but you retain ownership of next steps.”

“I’ll take ownership of this until [date], after which it returns to you.”

“You own this; I’m available if you need input.”

7) What not to assume / not to do

Do not assume

  • that helping equals owning,
  • that silence means someone else has it,
  • that responsibility naturally follows hierarchy.

Do not do

  • accept work without authority,
  • “just fix it” without clarity,
  • let monkeys accumulate quietly.