Writing a Team Charter That Prevents the Slow Drift Into Confusion
Most teams never write down what they are actually for. It works until it does not - until a reorg, a fast hire spree, or a scope dispute reveals that everyone had a slightly different picture the whole time.
A team charter is a short document that answers the questions a new member, a partner team, or a stressed team lead needs answered: what is this team responsible for, what is explicitly not ours, how do we make decisions, and how do we work together. It is the difference between a team that shares an understanding and one that assumes it shares an understanding.
The charter earns its keep at the boundaries. Most inter-team friction is a scope dispute in disguise - two teams both think a thing is theirs, or both think it is the other's. A charter that states what a team owns and, just as importantly, what it does not, resolves those before they become standoffs.
What a charter should contain
- Purpose: one or two sentences on why the team exists and what changes because it does.
- Scope: what this team owns, and - the part people skip - what it explicitly does not, with a pointer to who does.
- How decisions are made: who decides what, and what gets escalated. This is where a charter prevents the quiet paralysis of nobody being sure they can decide.
- Ways of working: the few norms that genuinely matter - how you communicate, your meeting cadence, how you handle interrupts. Not a rulebook; the handful of agreements that reduce friction.
What to leave out
A charter fails when it becomes an aspirational values poster. "We value excellence and collaboration" tells a new hire nothing and ages instantly into something nobody reads. Keep it operational: the things someone needs to know to work with or in this team, stated concretely enough to be useful and act on.
Keep it short. A charter longer than a page or two will not be read, and an unread charter is worse than none because it creates the illusion of shared understanding without the substance. If it does not fit on a page, you are writing a handbook, not a charter.
Keeping it current
A charter written once and never revisited becomes a fossil - it describes the team that existed at founding, not the one that exists now. Revisit it when the team changes shape: a reorg, a new mandate, a merged team. The review is quick if the charter is short, and it is exactly when scope is shifting that the charter is most worth having accurate.
In Atlas, a team charter lives as a doc in the team's space, next to the work and the decisions it governs, so a new member finds it on day one and the team can revise it in place when reality moves - rather than in a separate tool that slowly diverges from how the team actually operates.