Team Agreement¶
Norm charter — instantiates Psychological Safety Enablement
A short set of norms a team writes for itself — naming which candid behaviors are welcome and where the line of respectful conduct sits — so expectations are explicit and pointed-to before stress hits.
Team Agreement is a short, team-authored charter of behavioral norms — a handful of "we will / we won't" commitments the group makes to itself before the hard moment arrives. Its defining property is that it is a prospective, collective act of naming: the team decides in advance which candid behaviors are explicitly welcome (asking the "obvious" question, disagreeing with the lead, admitting you're lost) and where the boundary of respectful conduct sits, then writes it down so it can be pointed to later. It does not respond to any particular disclosure, run any review, or police any punishment; its entire contribution is to make the local rules explicit and jointly owned rather than tacit and inferred from whoever holds power. Because the team authored it together, the norms carry a legitimacy that a leader's edict lacks — but that same reliance on shared authorship is also its fragility, because a charter binds only as far as behavior under pressure actually honors it.
Example¶
A middle-school grade-level teaching team is chronically, politely dysfunctional: the two veteran teachers set the tone, the three newer ones nod along in meetings and then quietly do their own thing, and nobody names the instructional problems everyone privately sees. At an offsite, instead of another vision statement, they write a one-page agreement together. It names the behaviors they want to be safe: any of us can say "I tried that lesson and it flopped" without it counting against us; any of us can ask why we're doing something without being treated as difficult; disagreement about method is expected, not disloyal. It also names the boundary: we critique the lesson, not the teacher; we don't relitigate a decision behind each other's backs. The value shows up two months later, when a first-year teacher says in a meeting, "I have to be honest, our shared unit isn't working in my room" — and instead of the old frost, a veteran points to the agreement: this is exactly the thing we said was safe. The charter did not make her brave; it gave her, and the room, a pre-agreed rule to stand on.
How it works¶
- Author it together. The team drafts the norms itself rather than receiving them, because the mechanism's legitimacy comes from joint ownership — a rule the group wrote binds differently than one handed down.
- Name the welcome behaviors concretely. Vague "be open" is replaced with specific protected acts — questions, admissions of failure, method disagreement — so people know exactly what the agreement covers.
- Draw the respect boundary explicitly. The charter states what candor does not license: personal attacks, back-channeling, ignoring shared decisions — so protection for good-faith candor doesn't blur into permission for bad conduct.
- Make it referenceable. The agreement is written and visible so that, in the moment someone takes a risk, it can be pointed to — turning a private hope into a shared, invocable rule.
Tuning parameters¶
- Specificity — abstract values versus concrete behaviors. Concrete "we will" statements are actually invocable in the moment; abstract ones feel good and guide nothing.
- Authorship breadth — whole team versus a subset drafting for the rest. Full participation maximizes ownership and buy-in but is slower and can stall on wordsmithing; delegated drafting is faster but weaker glue.
- Boundary explicitness — how sharply the respect line is drawn. A crisp boundary prevents candor from curdling into cruelty but can feel legalistic; a soft one is warmer but leaves the hard cases unresolved.
- Revisit cadence — one-and-done versus periodically renewed. Revisiting keeps the agreement live and matched to the team's real behavior; leaving it framed on the wall lets it fossilize into decoration.
- Enforcement lightness — whether the norms are self-policed by peers or tied to any consequence. Peer self-policing preserves the collegial, owned character; formal consequence hardens it but shifts it toward a rulebook.
When it helps, and when it misleads¶
Its strength is that it converts tacit, power-inferred rules into explicit, jointly-owned ones — which is both a coordination win (everyone now knows what's expected) and a legitimacy win (the norm is ours, not the boss's). It leans on the force of an injunctive norm — a shared sense of what the group approves and disapproves of — which shapes behavior precisely because people are responsive to what their peers sanction.[n1] Naming the welcome behaviors and the respect boundary in advance gives a hesitant member a pre-agreed rule to invoke at the moment of risk.
Its failure mode is the gap between the written word and behavior under stress: an agreement that says "we welcome dissent" is worth nothing if the first real disagreement is met with a cold shoulder — and in fact it can be worse than nothing, because now the team has documented a norm it visibly violates, breeding cynicism. This is the parent archetype's slogan safety in charter form. A related misuse is the offsite ritual that produces a laminated poster nobody ever invokes again. The agreement also cannot, by itself, protect anyone from retaliation or make a leader actually respond well; it only sets the expectation. The guarding discipline is to treat the first stress test as the real ratification — to notice whether behavior matches the words when it counts, name the gap out loud when it doesn't, and revisit the agreement against actual conduct rather than admiring it on the wall.
How it implements the components¶
speak_up_behavior— the charter's core work is naming, concretely and in advance, which candid acts the team is protecting (questions, admissions of failure, method dissent), which is exactly this component's job of specifying the precise behavior rather than sloganizing "openness."protected_behavior_boundary— by drawing the respect line explicitly (critique the work not the person; no back-channeling), it defines the boundary that protects good-faith candor while preserving standards for respectful conduct.
It does not set the leader_response_norm — how authority actually responds when someone speaks — which is Leader Vulnerability Modeling; the Agreement names the expectation prospectively, but a leader enacting it in the moment is a different act. Nor does it provide the learning_review_container that turns surfaced concerns into tracked change — that is the Learning Review.
Related¶
- Instantiates: Psychological Safety Enablement — the team-authored charter that makes candor norms explicit and jointly owned before stress arrives.
- Sibling mechanisms: Leader Vulnerability Modeling · Pre-Meeting Silent Input · Learning Review · Blameless Postmortem · Error-Reporting System · Anonymous Reporting · Retaliation Protection Process · Dissent Round
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Team Agreement operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it a short set of norms a team writes for itself — naming which candid behaviors are welcome and where the line of respectful conduct sits — so expectations are explicit and pointed-to before stress hits.
Independent corroboration: The frozen evidence defines Team Agreement as 'A short set of norms a team writes for itself — naming which candid behaviors are welcome and where the line of respectful conduct sits — so expectations are explicit and pointed-to before stress hits', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Team agreement derives most directly from organizational management's coordination, workflow, and capability tradition; its defining operation is to a short set of norms a team writes for itself — naming which candid behaviors are welcome and where the line of respectful conduct sits — so expectations are explicit and pointed-to before stress hits.
Related originating lineages:
- Education & Pedagogy — Education, assessment, and instructional practice supplies a parallel or contributing lineage for the mechanism's defining operation: a short set of norms a team writes for itself — naming which candid behaviors are welcome and where the line of respectful conduct sits — so expectations are explicit and pointed-to….
- Operations Research — Operations research's allocation, scheduling, queueing, and optimization tradition provides a formative adjacent lineage for the same team agreement operation.
- Psychology — Experimental, clinical, and behavioral psychology supplies a parallel or contributing lineage for the mechanism's defining operation: a short set of norms a team writes for itself — naming which candid behaviors are welcome and where the line of respectful conduct sits — so expectations are explicit and pointed-to….
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a short set of norms a team writes for itself — naming which candid behaviors are welcome and where the line of respectful conduct sits — so expectations are explicit and pointed-to….
Review resolution: Both blind reviewers independently select organizational_management as the primary historical origin for the concrete operation—A short set of norms a team writes for itself — naming which candid behaviors are welcome and where the line of respectful conduct sits — so expectations are explicit and pointed-to before stress hits. The queued differences concern alternate origin disagreement, origin mode disagreement, domain reach disagreement, encyclopedia synthesis disagreement, not the primary lineage. I retain every alternate that either reviewer explains, without a numeric cap, and choose origin_mode=cross_disciplinary_synthesis because the reviewers' combined evidence identifies material construction from multiple disciplines. domain_reach=universal records later portability rather than multiplying historical origins; confidence=high is the conservative shared evidentiary level, and encyclopedia_synthesis=true preserves either reviewer's affirmative synthesis finding.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] An injunctive norm is a shared perception of what a group approves or disapproves of (as distinct from what it merely does) — a distinction from Robert Cialdini's norm research; injunctive norms guide behavior because people are sensitive to peer approval and sanction, which is the social force a written team agreement tries to make explicit and binding. ↩