> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/leadership/documents/team-charter.md).

# Team Charter

A team charter is a foundational document that defines a group's purpose, scope, and ways of working. 

Think of it as a "north star" for a project or a department. It ensures every member is aligned on why the team exists and how they will achieve their goals.

Rather than being a rigid set of rules, it is a collaborative agreement that prevents misunderstandings before they start.

#### Core Components of a Team Charter

Most effective charters cover these six primary areas:

**1. Purpose and Mission**

This section answers the "Why." It defines the team's reason for being and what success looks like in the long term.

**2. Roles and Responsibilities**

To avoid duplicated effort or tasks falling through the cracks, a charter lists who is responsible for what. This often includes:

* Team Lead\
  The primary point of contact.
* Scribe/Facilitator\
  Who manages the documentation.
* Subject Matter Experts\
  Specific technical or creative leads.

**3. Goals and Objectives**

These are the tangible outcomes the team needs to deliver. Good charters use SMART goals (Specific, Measurable, Achievable, Relevant, and Time-bound) to track progress.

**4. Communication Norms**

This establishes how the team shares information.

* Which tools will be used (e.g., Slack, email, or project management software)?
* How often will the team meet?
* What is the expected response time for internal queries?

**5. Decision-Making Process**

Deciding how to decide is crucial for avoiding deadlock. Will the team use a majority vote, seek full consensus, or does the team lead have the final say?

**6. Conflict Resolution**

A proactive plan for what happens when people disagree. It outlines the steps to take to resolve professional friction before it becomes personal.

#### Why Use One?

* **Clarity**\
  It eliminates "role ambiguity" by clearly stating expectations.
* **Accountability**\
  Because the team creates it together, members feel a stronger sense of ownership.
* **Onboarding**\
  It serves as an excellent manual for new members joining mid-project.
* **Efficiency**\
  By pre-defining workflows, you spend less time arguing about process and more time doing the actual work.

#### Example Structure

* **Mission**: To deliver a high-quality marketing campaign for the 2026 product launch.
* **Values**: Transparency, punctuality, and creative courage.
* **Boundaries**: The team has the authority to spend up to £5,000 without further approval.
* **Operations**: Weekly stand-ups on Tuesdays at 10:00 AM.

#### Further Reading

{% embed url="<https://www.figma.com/resource-library/team-charter/>" %}

{% embed url="<https://www.ppd.admin.cam.ac.uk/leadership-development/team-charter>" %}

{% embed url="<https://www.easyagile.com/blog/team-charter-working-agreement-social-contract-template-guide>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.designreference.xyz/leadership/documents/team-charter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.