Make the implicit explicit before friction does it for you
Most team conflict traces back to unspoken assumptions: who decides, how we communicate, what we are actually here to do. A team charter surfaces those assumptions and turns them into a shared agreement. Written together and revisited often, it becomes the reference that settles disputes before they escalate and onboards new members in minutes.
How it works
The builder walks you through the sections a working charter needs. The mission is one sentence on why the team exists. Goals are the concrete outcomes the team owns this period. Roles map each person to their responsibilities so there are no gaps or overlaps. The decision-making section names how the team resolves disagreement, which is the part most charters skip and most teams need most.
Communication norms cover where and how the team talks, expected response times, and meeting etiquette. The cadence section lists recurring meetings so everyone knows the rhythm. The tool assembles all of this into a single Markdown document, with empty sections omitted so the charter stays tight.
What each section does
| Section | What it answers |
|---|---|
| Mission | Why does this team exist? One sentence. |
| Goals | What outcomes is the team accountable for this quarter or year? |
| Roles | Who does what, and who is the single owner of each area? |
| Decision-making | How do we decide when we disagree? Who has the final call? |
| Communication norms | Where do we talk, what is the expected response time, how do we run meetings? |
| Meeting cadence | What recurring meetings happen, how often, how long? |
Skipping even one section creates gaps that surfaced assumptions will fill — usually in the form of complaints during a retrospective.
Writing guidance: specificity over aspiration
A strong charter is specific. Vague norms do not hold up under stress; concrete ones do.
Instead of: “We communicate openly.” Write: “Team decisions are discussed in #team-product, not DMs. Everyone replies within one working day. Cameras are optional in standups.”
Instead of: “We make good decisions together.” Write: “Default to consent: any team member can block a decision by stating an objection with a reason. If no resolution is reached in two days, the team lead decides after hearing all objections.”
Instead of: “We respect everyone’s time.” Write: “All meetings have an agenda posted 24 hours in advance. Meetings end 5 minutes early. Cancellations happen at least 2 hours before the start.”
The more specific the norm, the less ambiguity there is when the norm is violated, and the easier it is to course-correct without making it personal.
When to use and update the charter
Write the first version at the beginning of a new team, a new project, or when a team’s size or composition changes significantly. Revisit it:
- Each quarter as part of planning to update goals and confirm roles.
- When a new member joins — use the onboarding moment to walk through it and ask if anything should change.
- After a retrospective flagged a recurring friction — often the fix is a norm clarification, not a process overhaul.
Keep it to one page. A charter nobody reads is worse than none, because people stop trusting documents.