The unspoken rules, written down: why teams need working agreements

In an office, a hundred small norms get set without anyone deciding them. Who you interrupt, how fast you reply, what a raised eyebrow in a meeting means. Remote work deletes that ambient context, and most teams never notice until something breaks.

What actually makes a team work

Google's Project Aristotle studied what separates high-performing teams from the rest and found that physical proximity did not predict performance, as long as psychological safety was present.^[1] Psychological safety is simply the shared belief that you can speak up, admit a mistake, or ask a question without fear of embarrassment or punishment. Across the research it consistently ranks above resources, budget, and training as a driver of team performance.^[1]

Distance makes it harder, not automatic

Virtual environments tend to lower trust, reduce a sense of shared responsibility, and increase isolation, which makes remote teams harder to lead than co-located ones.^[2] You cannot read body language over a video call as easily, and the informal hallway moments that let people get to know each other simply do not happen.^[3] Safety that an office produced by accident now has to be produced on purpose.

Working agreements, defined

A working agreement is a short, explicit set of norms a team writes for itself: not a policy handed down, but a contract the team owns. The most useful ones cover the decisions that otherwise get made by assumption:

• Decision rights. Who can decide what, and when a decision needs more voices.
• Communication norms. What is async by default, what deserves a meeting, and what a reasonable response time looks like.
• How we disagree. Where dissent goes, and how it is handled, so that speaking up is the safe choice.
• How we show up. Availability, focus time, and what good looks like when nobody is watching.

Why writing it down matters

Teams that talk openly about these norms are far better placed to manage both the friction and the upside of remote work.^[2] The act of writing an agreement does two things at once: it surfaces the disagreements that were hiding inside everyone's private assumptions, and it gives new members a way to absorb the culture without osmosis. A norm you can point to is a norm you can improve.

Make it a living document

The failure mode is treating an agreement as a one-time offsite exercise that yellows on a wiki. The teams that get value from it revisit theirs when something rubs, and edit it in the open. The goal is not a perfect document. It is a shared, visible answer to how we work here, so trust does not depend on everyone guessing the same way.