Working Agreements: How Teams Build the Rules They Actually Follow

Summary

Every team mixes personalities, habits, and work styles, and that mix produces friction. A working agreement is the simplest tool I know for dealing with it: the team writes down together how it will work, keeps the list short and visible, and holds itself to it. It only works while the team keeps refining it.

What they are

A working agreement is more than a set of rules. Team members write it together to set guidelines for how they collaborate: expectations on respect, communication, deadlines, schedules, and work standards. It works in any industry and with any methodology.

Working agreements create a shared understanding of how team members wish to work together and engage with stakeholders.

A working agreement deals with likely areas of conflict early and sets clear expectations, which prevents misunderstandings and unproductive moments.

What they give a team

1. Clear roles. Everyone articulates their role and sees what the others contribute.
2. Better communication. Agreed channels and collaboration methods mean fewer misunderstandings.
3. Decision rules. The team has a structured way to decide and to solve problems, so resolutions come faster.
4. Every voice counts. Diverse perspectives are heard and valued, and outcomes improve.
5. A better climate. Teams feel more connected, motivated, and invested in shared success.
6. Accountability. Clear expectations make people answerable for what they do.
7. Trust and respect. Transparent, respectful collaboration gets a foundation to stand on.

Keep them alive

Writing the agreement is the first step. It only works if you keep refining it and hold each other to it.

Refine. Treat it as a living document. Review it at the start of a project or every few months, and adjust it as the team and its work change.

Hold each other to it. Each person owns their part in upholding it. When someone deviates, say so promptly and openly to keep the process intact.

How to build one

1. Find the need. Hold a team meeting to name the conflicts or unproductive moments that call for an agreement.
2. Discuss and propose. Every member speaks. The team leader guides with questions that shape the content.
3. Split into small groups. Smaller groups allow focused conversation on specific points.
4. Make it visible. Display it in the shared workspace, physical or digital. Remote teams need to be able to reach it.
5. Review it regularly. Encourage ownership and check that everyone is satisfied with the outcome.

What goes in

The content varies with the team and the project. These areas come up most often:

1. Communication channels. Agree which channel carries which kind of message: email, chat, or project tools.
2. Meeting protocols. Set how often meetings happen, how long they last, how people behave in them, and who plays which role.
3. Deadlines and milestones. Agree expectations on timelines and critical dates.
4. Collaboration tools. Name the apps for project management, file sharing, and communication.
5. Decision-making. Choose consensus, voting, or another agreed method.
6. Conflict resolution. Agree a framework for dealing with conflict promptly and respectfully.
7. Roles and responsibilities. Make clear who does what, so work does not overlap.

What a good agreement looks like

• Public and visible. It is written large and posted somewhere prominent, as a constant reminder.
• Made together. The whole team writes it, and nobody imposes it from outside. That is what creates ownership and commitment.
• Short. A small list people can remember beats a long one that overwhelms. Apply the Pareto principle and keep the few guidelines that matter most.
• Updated often. It changes as the team evolves and meets new challenges.
• Enforced by the team. People feel free to call out a breach, which keeps everyone accountable and gets issues resolved on time.

Examples

Atlassian’s guide to working agreements explains how to run a session. Below are a working agreement poster from Industrial Agency and a workshop board from Atlassian’s play.

Not a formality

Written once and filed away, a working agreement is a formality. It becomes the base of good teamwork, and prevents conflict before it starts, only while the team keeps refining it and holding each other to it.