Team Charter · Ground Rules
Team Charter & Ground Rules
What is a team charter?
- Define purpose, roles, and rules together, and put them in writing
- Turns conflict from a people problem into a rules problem
- A charter the leader writes alone won’t be followed
What a team charter really changes is when the conversation happens. Even teams that seem to have no rules have them. But everyone carries a different version in their head, and the differences only surface after something goes wrong. Teams that write a charter settle that conversation at kickoff, not after the incident. So when problems arise, they can say “Rule #3 isn’t being followed,” not “That’s just how they are.” The problem becomes about a rule, not a person—that is the practical payoff of this document.
A charter and ground rules sit on different layers. A charter is the higher-level agreement, such as purpose, success criteria, and decision authority, that rarely changes once set. Ground rules are behavioral commitments you keep adjusting as you work, such as reply times, meeting practices, and how objections are handled. A charter also differs from a task allocation sheet or RACI chart. Those cover who does what; a charter covers who makes the final call when opinions split. To work in practice, keep it to one or two A4 pages and no more than 7–10 rules. A list of twenty is the same as having none, because no one can remember it.
The act of writing is what gives the rules their force. Rules a leader drafts and circulates for sign-off are followed to a different degree than rules drawn out when each member shares 'the most frustrating moment on this team.' In the latter, every rule comes with the incident that produced it. To maintain it, 15 minutes in a retrospective every two weeks or once a month is enough to address broken rules and rules that no longer fit reality. Reading it together in a new hire’s first 1:1 is also the cheapest way to turn team culture that was only passed on by word of mouth into a document.
The most common misconception is thinking agreement is done the day the document is produced. In reality, if nothing happens at the first violation, that rule is dead that day. In particular, when a leader says 'it’s urgent just this once' and overturns a decision without a meeting, members file the charter as decoration that no one needs to follow. From then on, things get worse than before the document existed, because there is now an extra layer of cynicism: the rules existed and still weren’t followed. Statements like 'we respect one another,' where no one can tell whether a violation has occurred, are risky for the same reason.
Eun-a ChoExpert in communication, stress management, career development, and Gen Z/Millennial training
John KimCEO of Nanum Consulting and author of B2B Marketing DesignIt became established in project management and team development practice as a way to agree on and document a team’s purpose, roles, and norms at kickoff. It is used as a tool to deliberately speed up what Tuckman’s stages of team development call the norming stage.
At Company A, a healthcare SaaS firm with 320 employees, a task force was formed to launch a new subscription product. Nine people were pulled from four departments—planning, development, design, and marketing—with a three-month deadline. In the first three weeks, decisions already made were reversed five times, and unanswered Slack mentions repeatedly stalled work for two days at a time. (Hypothetical example)
- In week 2, the product planning lead heading the task force gathered nine people and said, "Each of you, write in one sentence what would count as success three months from now." The sentences that came back split seven different ways.
- The development lead said, "We settle something on Slack, then it gets overturned again at the next meeting, so nobody wants to act." Out of that one remark came two lines: decisions are made only as weekly meeting agenda items, and decisions recorded in the minutes are not reopened without new data.
- The deputy marketing manager raised the problem of slow replies and framed it as: “Reply to mentions within 24 hours; if you’ll be late, leave one line saying when you’ll answer.” The team boiled the rules down to 8, fit them on a single A4 page, and pinned the page to the top of the Slack channel.
- The task force lead added 'Objections are raised before the agenda item closes; in return, objections in a meeting are never dismissed on the basis of rank.' At the very next meeting, he took a counterargument from a third-year designer and reversed his own decision, setting the example first.
- They set aside 15 minutes of the biweekly retrospective for checking the rules. In week 6, the QA team said a 24-hour reply is impossible during release week, so they changed that rule to 48 hours and added an exception to item 4.
- Three months later, reversed decisions fell from 5 to 1, and weekly meetings shrank from an average of 90 minutes to 55. The 8-rule document was carried over as-is to two follow-up task forces as their standard kickoff template.