A team charter is the agreement a team makes with itself about how it will work together. It sits alongside the project charter and does a different job, since the project charter authorises the project and names the project manager, while the team charter governs conduct inside the team.
What a charter holds
Shared values come first, meaning the handful of things the team says it cares about, written specifically enough to be violated. Respect fails that test, because nobody argues for the opposite. "We would rather raise a risk early and be wrong than raise it late and be right" is a value, because it tells somebody what to do on a Tuesday.
Working agreements are the concrete ones. When work is ready to start and when it is finished, how documents and code get reviewed, what happens if somebody is going to miss a commitment, and how much of a day is protected from meetings.
Communication norms cover which channel carries what, expected response times, and what has to be written down rather than said. Decision rules say who decides what and what happens when the team cannot agree, which is the clause everybody skips writing and everybody eventually needs.
Meeting expectations set attendance, preparation, punctuality and who runs each recurring session. The conflict process describes how disagreement is handled before it reaches a manager, and it is the hardest part to write because it has to be agreed by people who currently get on.
The moment each clause pays for itself
A charter reads as a list of pleasant intentions until you put the second column next to it. Every clause exists for a specific bad afternoon, and the way to test a draft is to name the afternoon.
| What the charter covers | The moment it earns its keep |
|---|---|
| Shared values | Somebody has to choose between raising a risk early and looking foolish, and the team already made that choice on their behalf |
| Working agreements | A commitment is about to slip, and who hears about it and how soon was settled weeks ago |
| Communication norms | Something urgent goes to the channel nobody reads at the weekend, and the norm says which channel carries urgency |
| Decision rules | The team has split three against two on a design and the argument has been running for a week |
| Meeting expectations | Two people arrive unprepared to a review six people cleared their calendars for, and it is the third time |
| The conflict process | Two people have stopped speaking to each other and both are waiting for a manager to notice |
Read the right hand column first when drafting. A clause with no plausible afternoon behind it is decoration, and a bad afternoon with no clause behind it is the gap worth filling before the project meets it.
The team writes it
This is the whole point rather than a detail of process. A charter written by the team is a commitment its authors made in front of each other, which is a different psychological object from a document handed down.
The project manager facilitates. That means running a session where the questions get asked, disagreement surfaces instead of being smoothed over, and the wording is argued about until it means something. A session that reaches unanimous agreement in twenty minutes has produced nothing, because all it captured was what everybody assumed already.
The prompts that generate real disagreement are concrete ones. What counts as finished, how long a review may sit, what somebody does when they disagree with a decision that has already been made, and how the team wants to hear that a date is at risk. Each of those has several defensible answers, and the argument between them is the session doing its work.
Include the quiet members deliberately. The person who says least during charter writing is often the one whose expectations differ most from the rest of the room, and those are exactly the expectations the exercise exists to surface.
It earns its keep at the first disagreement
Writing a charter feels warm and slightly redundant. Everybody agrees, the document goes somewhere sensible, and for six weeks it does nothing visible.
The moment it pays back is the first real friction. Somebody has missed two commitments without saying anything, or a decision keeps being reopened, or reviews are stalling because one reviewer is overloaded. In a team with no charter that conversation is a confrontation between individuals and becomes about character. In a team with one it is a comparison against something both people helped write, and the subject is the agreement rather than the person.
This is also why vague charters are worse than none, since a promise to communicate openly can be compared against nothing at all.
| A clause you can argue with | The same clause written so it can be checked |
|---|---|
| Communicate openly | Say within a day when a commitment is at risk, in the team channel |
| Respect each other | Disagree in the meeting rather than in the corridor afterwards |
| Be responsive | Answer a direct question within a working day, or say when the answer will come |
| Come to meetings prepared | Read the document before the review, or say at the start that you have not |
| Resolve conflict constructively | Raise it with the person first, and bring it to the team if two attempts fail |
Everything in the right hand column either happened or it did not, which is what makes the charter usable in the conversation it was written for.
When the team changes, the charter changes
A charter is an agreement between particular people. Every arrival changes the group that made it, and a new member who inherits a charter written by strangers has received a policy after all.
Bring new members through it properly, which means asking what they would change rather than sending them the document. Some of what they suggest will be better, and the parts they cannot follow are usually the parts written in language that made sense only to the people in the original room.
Revisit it when the work changes shape as well. A team that moves from predictive delivery to iterative delivery, absorbs a supplier, or spreads across several time zones is operating under conditions its agreements were written before. A review held after a difficult month is worth more than one held on a calendar, because there is something concrete to test the wording against.
The familiar failure
The commonest failure is a charter written to be seen. It contains the values a team believes an auditor wants, it is duly signed, and nobody refers to it again, so the first real argument proceeds exactly as it would have done without it. A charter that has never been cited during a disagreement is a charter out of use, and that is something you can check rather than a matter of opinion.