A working agreement is a set of norms that the team creates and agrees to follow. Unlike rules imposed by management, working agreements are owned by the team. They define how members communicate, make decisions, handle conflict, and collaborate. Teams without explicit working agreements operate on implicit assumptions that frequently lead to misunderstandings and frustration.

Team Working Agreements: Building Shared Expectations

Why Working Agreements Matter

When a team member responds to Slack messages within minutes while another checks Slack twice a day, conflict follows. The immediate responder feels the other person is unresponsive. The twice-a-day checker feels the other person has unrealistic expectations. Neither is wrong — they simply have different assumptions about communication norms.

Working agreements make implicit assumptions explicit. They prevent the friction that comes from mismatched expectations and provide a reference point when disagreements arise.

Creating Working Agreements

Facilitation Process

Brainstorm individually (5 min). Each team member writes down what they need from the team to do their best work. Common themes include communication expectations, meeting behavior, availability, and decision-making.
Share and cluster (10 min). Post all items and group similar ones. Common clusters include communication norms, meeting etiquette, quality standards, and availability expectations.
Discuss and refine (20 min). For each cluster, discuss what the team agrees to. Focus on observable behaviors rather than vague aspirations. “We respond to PR reviews within 4 hours” is observable. “We value collaboration” is not.
Consensus check (5 min). Every team member must be willing to follow every agreement. If someone objects to an item, discuss it further or remove it. A working agreement that team members do not buy into will not be followed.
Post visibly. Display the agreements where the team can see them daily — on the physical wall, in the project management tool, or at the top of the team wiki.

Common Working Agreement Categories

Communication

We respond to Slack DMs within 4 business hours
We use threads for all Slack discussions
Urgent issues are communicated by phone call, not Slack
We post status updates in the project channel by end of day Friday

Meetings

All meetings have agendas shared at least 1 hour before
Meetings start and end on time
Cameras on for team meetings
No laptops during decision discussions

Quality

All code is peer-reviewed before merge
PRs are under 400 lines of change
Tests are required for new features
We follow the definition of done without exception

Availability

Core hours are 10 AM - 3 PM in the team’s primary time zone
Focus time blocks on calendars are respected
Vacation requests are posted two weeks in advance
On-call rotation is shared equally

Decision Making

Architectural decisions require RFC with 48-hour comment period
Sprint scope changes require Product Owner approval
Day-to-day technical decisions are made by the person doing the work
Disagreements unresolved after 15 minutes are escalated to the team lead

Enforcing Working Agreements

Working agreements are self-enforced. Any team member can (and should) respectfully point out when an agreement is being violated. “Hey, I notice we haven’t been reviewing PRs within our 4-hour SLA this week. Can we discuss this in the next retrospective?”

The key word is “respectfully.” Working agreements are tools for alignment, not weapons for blame.

Evolving Working Agreements

Review working agreements in retrospectives at least quarterly. Agreements that the team consistently follows without thinking about them may no longer need to be stated. Agreements that are frequently violated need to be either recommitted to or removed. New situations (a team member in a different time zone, a change in project type) may require new agreements.

The working agreement is a living document. A team that created agreements six months ago and never revisited them is not getting the full benefit of the practice.

Working Agreements for Remote Teams

Remote and distributed teams need additional agreements around:

Response times by channel and time zone
Camera expectations for video calls
Async communication defaults — when to message vs. when to schedule a call
Documentation expectations — decisions in meetings must be written down and shared
Social interaction — virtual coffee chats, team events, informal channels

Remote working agreements are more detailed than co-located team agreements because the team cannot rely on in-person cues and spontaneous communication to resolve ambiguity.