How teams function when the goal is collective performance, not individual positioning

1) What this artifact is

A staff-facing operational reference defining what teamwork actually means in a U.S. embassy environment. It clarifies how teams are expected to function when the goal is:

  • improving collective performance,
  • developing all members,
  • protecting institutional integrity,
  • and delivering results under pressure.

This is not motivational language and not a values poster. It is a behavioral and structural guide that explains what teamwork looks like in practice, what it is not, and how it breaks down in real embassy settings.

2) Who it is for

  • FSOs and LES working in section teams
  • Supervisors and team leads
  • New staff onboarding into embassy culture
  • Anyone experiencing internal competition, mistrust, or uneven treatment

This applies across grades, roles, and employment categories.

3) How the work actually functions (process)

A) The core purpose of teamwork

In an embassy, teamwork exists to:

  • deliver outcomes the individual cannot deliver alone,
  • reduce institutional risk,
  • preserve continuity despite rotation,
  • develop capacity over time.

Teamwork is instrumental, not sentimental.
It is about how work moves, how people are treated, and how credit and accountability are handled.

B) What teamwork is (mechanically)

Effective teamwork means:

  1. Shared objectives
    Team members understand the mission goal and align their work accordingly.
  2. Clear roles with mutual support
    People know who owns what, and others assist without undermining ownership.
  3. Information sharing
    Relevant information is shared proactively, not hoarded.
  4. Collective problem-solving
    Problems are addressed as system issues, not personal failures.
  5. Skill development
    Team members help each other improve, especially where experience differs.

C) What teamwork is not

Teamwork is not:

  • internal competition for visibility,
  • jockeying for position or favor,
  • withholding information to gain advantage,
  • shifting blame downward or sideways,
  • performing loyalty at the expense of truth.

These behaviors weaken the institution even if they appear to benefit individuals in the short term.

D) Sharing credit and responsibility

In functioning teams:

  • Credit is shared outward, not claimed inward.
  • Mistakes are owned appropriately, not displaced.
  • Success is framed as a team outcome.
  • Accountability is clear but not weaponized.

Supervisors are expected to distribute credit fairly and absorb blame upward, not pass it down.

E) Growth as a team responsibility

Embassy teams assume:

  • all staff are capable of growth,
  • uneven performance is often a systems issue,
  • development requires opportunity, not favoritism.

This means:

  • rotating opportunities fairly,
  • coaching instead of sidelining,
  • correcting behavior early and privately,
  • avoiding permanent labels (“strong,” “weak,” “difficult”).

F) Equal opportunity and fairness

Teamwork requires:

  • consistent standards,
  • transparent decision-making,
  • avoidance of favoritism,
  • clarity about why opportunities are assigned.

Perceived unfairness erodes trust faster than workload.

4) Common failure patterns (paired with corrections)

Failure 1 — Competition disguised as excellence

Pattern: Individuals seek visibility at others’ expense.
Correction: Evaluate and reward contributions to team outcomes, not solo performance.

Failure 2 — Throwing others under the bus

Pattern: Errors framed as individual incompetence.
Correction: Address mistakes as process failures unless misconduct is clear.

Failure 3 — Favoritism

Pattern: Same individuals get opportunities repeatedly.
Correction: Rotate chances intentionally; explain selection criteria.

Failure 4 — Silence in the name of harmony

Pattern: Problems go unspoken to “keep the peace.”
Correction: Encourage respectful dissent; silence harms the team long-term.

5) Realistic scenarios (≥3)

Scenario 1 — High-visibility task

One team member receives public credit for a group effort.

Teamwork response:
Supervisor acknowledges contributors explicitly and privately ensures fair evaluation.

Scenario 2 — Mistake on a shared product

An error appears in a team deliverable.

Teamwork response:
Fix the issue, review the process, adjust safeguards — do not assign blame publicly.

Scenario 3 — Development opportunity

A training or travel opportunity arises.

Teamwork response:
Apply clear criteria, rotate opportunities over time, explain decisions openly.

6) Checklists / templates (≥2)

Checklist A — Team Health Check

  • Are roles clear?
  • Is information shared promptly?
  • Is credit distributed fairly?
  • Are mistakes handled constructively?
  • Are development opportunities rotated?

If multiple answers are “no,” teamwork is degrading.

Template B — Team Norms Statement

As a team, we:
- Share information proactively
- Support each other’s development
- Address problems early and directly
- Share credit and absorb mistakes fairly
- Apply standards consistently

Use as a standing reference, not a slogan.

7) What not to assume / not to do

Do not assume

  • competition improves outcomes,
  • silence equals agreement,
  • strong performers do not need development.

Do not do

  • reward loyalty over performance,
  • protect favorites,
  • allow fear to govern interactions.