A team charter is a short written agreement covering three things: why the team exists, what it actually values in how people behave day to day, and the specific ground rules for meetings, decisions, communication, and conflict.
It's not a mission statement for the wall, it's a working reference the team wrote together and can point back to. Most team friction isn't about strategy, it's about mismatched expectations that were never said out loud, and a charter is where you say them out loud once, together.
- Write it together, don't hand down a finished draft. A charter the team didn't help write is just another policy nobody reads.
- Nail the purpose in one sentence. If it takes a paragraph to explain why the team exists, it's not sharp enough yet.
- Name three to five real operating principles. Pull them from actual moments of friction or pride, not from a generic values poster.
- Set explicit working agreements. Meetings, decisions, communication, and conflict are the four places assumptions quietly diverge, so spell each one out.
- Revisit it at least yearly. A charter that never changes as the team changes stops being a working document and becomes wallpaper.
A worked example for a client-facing operations team. Replace the purpose, values, and agreements below to match your own team.
"We exist to get every client live on time, without burning out the people who make it happen."
- Standing sync is Tuesday 10am, 30 minutes, agenda posted the day before.
- No meeting happens without a written agenda.
- Default to a shared doc instead of a meeting when it can be async.
- Every decision has one named owner, even when input is broad.
- Disagree and commit once a call is made, relitigate only with new information.
- Anything client facing or over $10k gets a second read before it ships.
- Chat for anything that isn't urgent, a call only for a true blocker.
- Response window is same business day, not same hour.
- Client facing news reaches the team before it reaches the client.
- Raise it directly with the person first, not in a side channel.
- Still stuck after that, bring it to the team lead within a week.
- Start from the assumption the other person is trying to do good work.
"We wrote this together, and we'll hold each other to it."
The download is a fillable Word document with the same worked example, ready to swap for your own team's answers and print for signatures.
- Draft it in a working session with the whole team, not a survey you tally up afterward.
- Keep it to one page. If it's longer than that, nobody will actually reread it.
- Put it somewhere people actually see, pinned in the team channel, not buried in a folder.
- Don't write values that sound good but nobody could point to a behavior for.
- Don't treat it as a one-time exercise, revisit it when the team changes.
- Don't let it sit unsigned, the signatures are what make it a commitment instead of a suggestion.