Build the norms your team actually commits to. Everyone proposes, everyone votes - agreements are adopted democratically, not handed down.
Start a free sessionNo account required. Share a code and you are in. Password-protected rooms supported.
Working agreements are the explicit commitments a team makes about how they will work together - communication norms, meeting rules, coding standards, and anything else that affects day-to-day collaboration. They are not imposed by management: the team creates them together.
When a team builds its own norms, people are far more likely to follow them. Agreements feel fair because everyone had a voice. They reduce friction, set clear expectations, and give the team a shared language for calling out when something is not working.
Every team member can propose agreements and vote on every proposal. No single person or manager decides what the norms are - the group does.
When people vote on an agreement and it passes, they feel ownership. Agreements that are decided together are followed more consistently than ones handed down from above.
The host sets an adoption threshold (e.g. 75%). Proposals that clear the bar are adopted. Those that do not are dropped or revised. No ambiguity about what the team agreed to.
The whole process - proposing, voting, and adopting - takes 20 to 30 minutes. You leave with a real, voted-on list of working agreements, not a long facilitation exercise.
Real scenarios software teams run into.
The first week is the best time to establish norms before habits form. A working agreements session gives a new team a shared foundation: how you communicate, how you handle conflict, what done means.
When several new members join or a team is restructured, old agreements may no longer fit. Run a session to revisit norms and make sure everyone - including newcomers - has a voice.
If the same interpersonal or process issues keep appearing in retrospectives, it is a sign the team lacks clear shared norms. Working agreements give those problems a formal, agreed-upon solution.
Distributed teams need explicit agreements even more than co-located ones. How do you communicate async? What is the expected response time? When are meetings required vs optional? Working agreements answer these questions.
Treat working agreements like a living document. Run a session every quarter to review what is still working, retire what is not, and add anything new the team has learned about how they work best together.
When two teams need to work closely together on a shared goal, a joint working agreements session sets expectations upfront and prevents misunderstandings about ownership, communication, and decision-making.
The host creates a session and sets an adoption threshold - e.g. 75% means 3 out of 4 people must vote yes for an agreement to pass.
Share the session code with your team. No accounts needed - everyone joins instantly.
Everyone proposes agreements: communication norms, meeting rules, coding standards, anything the team should commit to.
All proposals are visible to the whole team during the collection phase.
The host opens voting. Each person votes yes or no on every proposal, independently and privately.
Votes are hidden until the host reveals results - no social pressure to follow others.
The host reveals results. Proposals that meet the threshold are marked as adopted.
The team now has a set of democratic, voted-on working agreements to commit to.
Create a free session in seconds and invite your team with a code. No account, no setup.
Start a free Working Agreements session