How to Write a Team Working Agreement People Actually Follow

Most team friction is not about the work. It is about how the work happens: who replies to what and how fast, which meetings matter, where decisions are recorded, whether it is fine to message someone at 21:00. Everyone has different assumptions, and nobody says them out loud until they collide.

A working agreement is a short, written set of norms the team agrees on together. It is especially valuable for hybrid and distributed teams, where you cannot pick up norms by sitting next to each other.

What Belongs In A Working Agreement

Keep it to one page. Cover the questions that cause friction:

Communication

• Which channel for what (chat for quick questions, email for external, documents for decisions).
• Expected response times by channel.
• How to flag something urgent.

Availability

• Core hours when everyone is reachable.
• How to show focus time or being away.
• Expectations outside working hours. See right to disconnect laws and after-hours messages.

Meetings

• Which recurring meetings exist and why.
• Agenda in advance, notes afterwards.
• Cameras, if it matters to your team.

Decisions

• Who decides what.
• Where decisions are recorded. See how to write a decision log entry.

Feedback and conflict

• How to raise a concern.
• How the team reviews the agreement itself.

Write It With The Team, Not For Them

An agreement handed down by a manager is a policy. People follow policies reluctantly. An agreement the team writes together is a set of promises to each other, and people keep those far better.

A simple process:

1. Ask everyone to answer three questions in advance: what helps you work well, what frustrates you, what would you change?
2. In a 45-minute session, group the answers and agree a norm for each theme.
3. Draft the agreement, share it, and give people a few days to comment.
4. Review it every quarter or when the team changes.

Atlassian’s working agreements play is a good free facilitation guide.

Write Norms As Specific Behaviours

Vague values (“we communicate openly”) change nothing. Specific behaviours do.

Before:

We respect each other’s time and communicate effectively and asynchronously where possible.

After:

We reply to direct messages within four working hours. If something is urgent, we say “urgent” in the first line and explain why. Meetings without an agenda shared the day before can be declined. We do not expect replies outside core hours (10:00 to 16:00 UK time), and we schedule messages if we write late.

Each sentence in the second version is something you can see someone doing or not doing.

A Wrivio Context for team norms could say:

Rewrite these notes as a team working agreement. Clear, friendly and specific, each norm as an observable behaviour. Use “we”. Keep every time, channel, number and rule exactly as written. Do not add rules, values or penalties that are not in the original.

Press Ctrl+Shift+Space, paste the notes from your session, and check every norm still says what the team agreed.

An Example To Adapt

How we work together

• Chat for quick questions; documents for decisions; email for people outside the team.
• Direct messages: reply within four working hours. Channels: within one working day.
• Urgent means “this will cause harm if it waits until tomorrow”. Use the word and say why.
• Core hours 10:00 to 16:00. Outside them, no reply is expected.
• Every recurring meeting has an owner, an agenda the day before, and notes within 24 hours.
• Decisions go in the decision log with the date and who decided.
• If something about how we work is not working, raise it in the retro or with the team lead.
• We review this agreement every quarter.

Make It Visible

Pin it in your team channel, link it in onboarding, and refer to it in the moment (“per our agreement, can we get an agenda for this?”). An agreement nobody mentions is an agreement nobody remembers.

Common Questions

What is the difference between a working agreement and a team charter?

A charter usually covers purpose, goals and responsibilities. A working agreement covers how people work together day to day. Many teams have both; the working agreement is the one people refer to weekly.

How long should a working agreement be?

One page or less. If it does not fit on a page, it is trying to be a handbook.

What if someone keeps breaking the agreement?

Raise it privately first, as a reminder of something the team agreed together. If it continues, it is a performance conversation, and the agreement gives you a clear, shared reference.

Should managers be bound by it too?

Yes. A working agreement that the manager ignores is worse than none, because it teaches the team that norms are optional.

Download Wrivio for Windows to turn your team’s session notes into a clear, one-page working agreement.