Working Agreements
Explicit, team-created norms for everyday collaboration, including communication, meetings, focus time, decisions, handoffs, and conflict.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/working-agreements/
01What it means
Working agreements are a small set of observable commitments about how team members will work together. They translate broad values such as respect or transparency into behaviors the group can recognize, discuss, and revise. They are narrower than a team charter, which also defines purpose, scope, authority, and success.[1][2]
02Why it matters
Unspoken norms still govern a team, but they usually favor established members and remain difficult to challenge. Explicit agreements reduce coordination ambiguity, make inclusion needs easier to discuss, and provide neutral language for addressing recurring friction. The creation conversation is often as valuable as the final list because it exposes incompatible assumptions early.
03When to use it
Create agreements when a team forms, becomes distributed, changes membership, adopts new tools, or repeatedly struggles with meetings and handoffs. Review them after incidents, retrospectives, or changes in working conditions. They are useful for temporary cross-functional groups as well as long-lived teams.
04How it works
- Ask members what helps or hinders their best work, including accessibility, time-zone, and concentration needs.
- Group concerns into practical areas such as communication channels, response expectations, meetings, decisions, reviews, and escalation.
- Write specific behaviors with enough flexibility for judgment, avoiding slogans such as communicate better.
- Discuss tradeoffs and power differences so that silence is not mistaken for genuine consent.
- Choose a short initial set, publish it where work happens, and identify how members can raise a breach safely.
- Test the agreements for several weeks and revise them using concrete examples rather than personal blame.
05A practical example
A hybrid product team agrees that decisions affecting absent colleagues remain open for one business day, urgent requests use a dedicated channel with a named owner, and meeting notes record decisions and dissent. After a month, it shortens the decision window for reversible changes but keeps it for architectural and policy choices.
06Where it breaks
Agreements cannot override employment policy, legal duties, or individual access needs. They may become tools for conformity if a majority imposes preferred work styles on everyone. Rules that are too rigid can slow urgent work, while agreements without consequences or review quickly become decorative. Managers remain responsible for addressing misconduct and structural problems.
Common mistakes
- Copying another team’s norms without discussing local needs and constraints.
- Using abstract values instead of observable behaviors and response expectations.
- Treating initial silence as consent or allowing senior members to dominate the agreement.
07Sources
- Working Agreements PlayAtlassian · Professional facilitation guideWorking Agreements Play
- Team Norms and Working Agreements That StickTeamRetro · Professional facilitation guideTeam Norms and Working Agreements That Stick