Most teams that build a working agreement do it once, early, in an enthusiastic kickoff meeting - and then never open the document again. Three weeks later, a real conflict happens that the agreement was supposed to help with, and nobody thinks to check it, because it's already become background noise. The problem usually isn't that the team didn't want a working agreement. It's that the one they built was never actually built to be used.
Why most team agreements don't survive contact with a real problem
They're written before anyone has a real disagreement to calibrate against. A kickoff-meeting agreement, built when everyone is optimistic and nothing has gone wrong yet, tends to be vague and aspirational - "we'll communicate openly," "we'll respect each other's time" - because there's no concrete friction yet to make it specific.
They skip the uncomfortable topics entirely. It's easy to agree on meeting cadence. It's much harder, and much more valuable, to agree in advance on what happens when someone misses a commitment, how conflict actually gets raised, or who has final say when the team can't reach consensus. Agreements that avoid these topics are exactly the ones that turn out useless the first time they're actually needed.
Nobody ever refers back to them. Without a specific trigger to revisit it - a scheduled check-in, a new team member, a project milestone - the document just becomes something that existed once, in a folder nobody opens.
What makes an agreement actually get used
Cover the specific, uncomfortable things, not just the pleasant ones. Decision rights when the team disagrees. Response-time expectations that are realistic, not aspirational. How and where conflict gets raised. What "done" actually means for a deliverable. What happens - specifically - when someone misses a commitment. These are the exact moments an agreement is supposed to help with, and they're the ones most kickoff conversations skip because they feel presumptuous to discuss before any conflict has happened.
Make it genuinely specific, not a values statement. "We communicate respectfully" isn't actionable. "Decisions get made by the person accountable for that piece of work, after hearing from everyone affected, within 48 hours" is something the team can actually check itself against later.
Build in a real reason to reopen it. A scheduled check-in - a project midpoint, a monthly review, whenever a new person joins - works far better than hoping someone remembers to revisit it. Without a trigger, "we'll update it as needed" reliably means "we'll never update it."
Treat the first real conflict as the actual test, not a failure of the agreement. The first time the agreement gets used for something real - a missed deadline, a disagreement about direction - is the moment that reveals whether it was specific enough to be useful. If it wasn't, that's information to fix the agreement with, not a sign the whole exercise was pointless.
If your team hasn't built a working agreement yet, or wants a structured starting point that covers the topics above by default, MBA Lab's team charter builder turns a name and member list into a complete, printable working agreement - roles, decision-making, conflict handling, and accountability included - in about two minutes.