Team Charter

What it is

A Team Charter is a concise team agreement on how the team works together. It documents goals, roles, communication channels, decision-making rules, quality expectations, and the way to resolve disagreements. The practice helps when agreements only exist in verbal conversations and each person interprets them differently. It is most useful at the single-team level, where members can actually change their working rules.

When it helps

Team members have differing understandings of the team's purpose and argue about priorities in each new work cycle.
Decisions get lost in chats, and the team ends up revisiting already agreed-upon matters.
New members spend a long time figuring out the unwritten rules: who to contact, where to log tasks, and who makes the final decision.
Conflicts are discussed behind the scenes because there is no agreed-upon way to resolve disagreements.
The quality of outcomes depends on individual habits rather than clear team expectations.

How to start

1 Select a document owner: typically the team lead or a facilitator who will draft the charter and guide the discussion to a decision.
2 Hold a short working session and list the team's purpose, key results, main roles, and areas of responsibility.
3 Document communication rules: which matters go to chat, which go to meetings, where decisions are stored, and the response deadlines the team commits to.
4 Describe how the team makes decisions and what happens if members disagree: who decides, whose input is needed, and where the outcome is recorded.
5 Test the charter on a near-term real task and remove any items the team is not ready to follow in practice.

Expected effect

The team gets a shared document of agreements that can be revisited during disputes, onboarding, or shifting priorities. This reduces renegotiations, clarifies role and quality expectations, and helps the manager address issues through rules rather than personal grievances.

Common pitfalls

Making the document too long: team members stop using it if it's hard to quickly find a working rule.
Copying a template without discussion: formal norms don't work if the team hasn't accepted them as their own.
Not assigning an owner for updates: agreements become outdated after changes in team composition, goals, or process.
Using the charter as a means of punishment, not as a support for calm conversation about work rules.
Documenting ideal rules that the team can't comply with given the current workload or authority.

FAQ

Who should own the Team Charter?

Usually the team manager starts it, but the charter should belong to the whole team. The owner keeps it updated, and the rules are discussed and adopted by the members who will be using them.

Can we start without an external facilitator?

Yes. It's enough to get the team together, go through goals, roles, communications, decisions, and conflicts, and then record only those rules that members are ready to put into practice immediately.

How can we tell if the charter is effective?

The team starts referencing it in work situations: during debates over a decision, when onboarding new members, selecting a communication channel, or discussing the quality of results. If no one looks at the document, it should be simplified or updated.

What if part of the team resists documenting the rules?

Start with specific pain points: lost decisions, drawn-out approvals, differing quality expectations. Talk not about abstract discipline, but about which rules will eliminate recurring friction.