Better decisions. More thoughtful work.

A Team Charter Needs Working Agreements People Can Use

A team discussing working agreements around a board of notes.
AI-generated photographic illustration; not documentary photography.

“We communicate well” sounds agreeable in a team charter. It becomes useful only when people can tell what to do at 4 p.m. when a decision is still unanswered and tomorrow’s work depends on it.

Atlassian’s working-agreements play encourages teams to make shared expectations explicit and revisit them when circumstances change. A charter can hold those agreements, but the document should describe a workable arrangement rather than a collection of admirable words.

Start with recurring friction

Ask each person to name a situation that repeatedly slows the team down. Keep the examples about work: an unclear handover, an unanswered request, a decision that gets reopened or a meeting without an owner. Look for a small number of patterns the group can address.

Then write an agreement that identifies the action and the exception. For example: “The person handing over a task records its current state, next step and unresolved question. If the handover is urgent, they also contact the receiving person directly.” This is an illustrative agreement, not a rule every team must adopt.

Test the wording against a real day

Give the group a scenario and ask what the agreement requires. If people give incompatible answers, revise the wording. If the agreement depends on someone monitoring messages outside their working hours, discuss that assumption openly rather than hiding it inside “be responsive.”

Make room for access needs, time zones and different roles. A good agreement can set an expectation while allowing a clear way to raise a constraint.

Give the charter a review mechanism

Name where the current version lives, who records agreed changes and when the team will review it. A short check after a trial period can ask which agreement helped, which was ignored and whether the problem was unrealistic wording or an unresolved resource issue.

Keep the document short enough to consult during work. The measure of success is not how impressive the charter sounds at a launch meeting. It is whether a newcomer can use it to understand how the team makes ordinary decisions together.