Team Working Agreement¶
Document — instantiates Local Rule Design
Implements local rule design in groups by making repeated interaction rules explicit: how people signal blockers, make decisions, update each other, or coordinate handoffs.
A team working agreement is a short, self-authored document in which one team makes its own repeated interaction rules explicit — how we surface work, which calls we make ourselves versus bring to someone, how we hand off — and, crucially, keeps it a living artifact the team itself re-opens and revises. What makes it this mechanism is that the people bound by the rules write and own them, and the deliverable is a lightweight, visible document that draws the team's autonomy line: where a member acts alone and where they confer. Its legitimacy comes from authorship, not from a mandate handed down. It governs one team's day-to-day interaction, not the allocation of authority across many units.
Example¶
A six-person product team keeps colliding: two people edit the same module and clobber each other, "settled" decisions get re-litigated in the next standup, and work stalls waiting on approvals nobody agreed were needed. In a 30-minute session they write an agreement and pin it to the board: a work-in-progress limit of two items per person; anything reversible within a day, just do it and mention it at standup; anything one-way-door, bring it to the team first; pull requests reviewed within four working hours; and "done" means merged and deployed to staging. Two sprints later, a retrospective finds the four-hour review rule unrealistic across time zones, so the team revises it to end-of-next-working-day. Collisions drop, decisions stop bouncing, and the document keeps changing shape as the team learns — because the team owns it.
How it works¶
- Co-authored, so legitimate. The rules stick because the people who follow them wrote them.
- Concrete and situated. WIP limits, pull signals, a definition of "done" — rules an actual member can apply in the moment, not slogans.
- An explicit autonomy line. The agreement names which decisions a member makes alone and which they bring to the group.
- Lives in the shared workflow. It is visible where the work happens — the board, the standup, the channel.
- Re-opened on a cadence. The retrospective is the built-in moment to amend rules that stopped fitting.
Tuning parameters¶
- Specificity — a few guiding principles versus many concrete rules. Concrete coordinates tightly but calcifies; loose preserves judgment but under-coordinates.
- Autonomy threshold — how large a decision a member may make alone before conferring. Wide is fast but risks surprise; narrow is safe but slow.
- Revision cadence — every retrospective versus quarterly. Frequent keeps the document alive but can churn; rare lets it drift out of date.
- Scope — how much of the team's work the agreement tries to cover, trading completeness against a document too long to read.
- Enforcement style — peer reminder versus lead-owned. Peer keeps it flat; lead-owned risks it reading as policy.
When it helps, and when it misleads¶
Its strength is converting the implicit friction of a group into explicit, cheap-to-change rules owned by exactly the people affected — which makes local adaptation fast and low-drama.
Its failure mode is the dead document: written once in a kickoff, then ignored, or worse, degraded into ritual where people satisfy the letter of a rule while the coordination it was meant to create quietly erodes — a small-scale Goodhart effect, where the rule becomes the target and stops measuring anything real.[n1] The classic misuse is a manager imposing an "agreement" the team did not author; it reads as policy, earns no legitimacy, and changes no behavior. The guarding discipline is to keep it short, keep it visible, revisit it in retrospectives, and let the team — not a boss — own the edits.
How it implements the components¶
local_rule— the concrete situated rules (WIP limits, pull, "done", handoff) each member follows at the moment of interaction.autonomy_boundary— the explicit line between decisions the team makes alone and those it defers or confers on.interaction_medium— the team's shared workflow surface (standup, board, channel) where the rules live and stay visible.rule_revision_loop— the retrospective is the standing loop that re-opens and amends the agreement.
A working agreement does not implement boundary_condition (a formal charter or mandate limiting the team's authority from outside) or exception_or_escalation_rule (a formal escalation ladder for surfacing conflict between units) — that inter-unit governance machinery is Decentralized Governance Norm. A working agreement is one team's self-set autonomy; a governance norm allocates bounded authority across many units.
Related¶
- Instantiates: Local Rule Design — a working agreement is the social, single-team instance of shaping group behavior by making its local interaction rules explicit.
- Sibling mechanisms: Swarm Rule · Cellular Automata Rule · Market Rule · Protocol Rule · Community Norm · Routing Rule · Decentralized Governance Norm
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Team Working Agreement operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it implements local rule design in groups by making repeated interaction rules explicit: how people signal blockers, make decisions, update each other, or coordinate handoffs.
Independent corroboration: The frozen evidence defines Team Working Agreement as 'Implements local rule design in groups by making repeated interaction rules explicit: how people signal blockers, make decisions, update each other, or coordinate handoffs', 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 working agreement derives most directly from organizational management's coordination, workflow, and capability tradition; its defining operation is to implements local rule design in groups by making repeated interaction rules explicit: how people signal blockers, make decisions, update each other, or coordinate handoffs.
Related originating lineages:
- Operations Research — Operations research's allocation, scheduling, queueing, and optimization tradition provides a formative adjacent lineage for the same team working agreement operation.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: implements local rule design in groups by making repeated interaction rules explicit: how people signal blockers, make decisions, update each other, or coordinate handoffs.
Review resolution: Both blind reviewers independently select organizational_management as the primary historical origin for the concrete operation—Implements local rule design in groups by making repeated interaction rules explicit: how people signal blockers, make decisions, update each other, or coordinate handoffs. 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] Goodhart's law — "when a measure becomes a target, it ceases to be a good measure." Applied to a working agreement, it warns that once a rule (say, a review-time target) becomes the thing people optimize, they can satisfy it while the collaboration it was meant to protect decays. ↩