Purpose
When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day.
Facilitation Operating practice
Team Charter
Records a team’s mandate, boundaries, roles, and ways of working as a checkable agreement.
A Team Charter connects purpose, customers, responsibilities, communication paths, and decision rules. It provides a shared reference for formation, handover, and conflict clarification.
What shared agreement enables this team to fulfil its mandate with clear boundaries and responsibilities?
- Participants
- 3-12
- Time
- 75–120 minutes for the first version; review after 4–6 weeks and after material team changes.
Each step produces a concrete domain result for the complete run.
Mandate
Clarify mandate
Record purpose, expected value, and customers together.
Boundaries
Set scope
Name owned outcomes, dependencies, and explicitly excluded work.
Roles
Assign responsibility
Record decision, execution, and advice roles for concrete outcomes.
Ways of working
Agree collaboration
Document communication, meetings, conflict path, and relevant agreements.
Review
Maintain charter
Set assumptions, open points, and the next joint review.
Update the charter with team and sponsor after startup, mandate changes, and new team members.
A good fit when
Use it when forming a team, reorganizing, or starting work with several dependencies.
Ideal for
- New Teams
- Project Kickoff
- Team Reset
Not good for
- One-off workshops without an ongoing team
- Pure task planning
Outputs
Published charter with review
Versioned team charter with purpose, customers, success signals, scope, roles, decision paths, working rules, open points, and review date.
Team charter
Fictional example
Fictional short version for a team operating a digital booking service.
Purpose and customers
Why does the team exist, whom does it help, and what value should result?
We help small workshops book maintenance appointments reliably without phone queues.
Outcomes and boundaries
Which outcomes does the team own, and what is explicitly outside?
Owns booking flow and confirmation. Outside: workshop ERP and pricing.
Roles and decisions
Who decides, executes, or contributes to key outcomes?
Product decides priorities; Tech decides implementation; Support is consulted on confirmation-flow changes.
Collaboration
Which channels, rhythms, and conflict paths apply?
Blockers appear on the board daily; domain decisions go into the decision log; unresolved goal conflicts go to Product and sponsor within two working days.
Open points and review
What remains open, who resolves it, and when is the charter reviewed?
Open: access to ERP test data, owner Samira by 12 Oct; charter review on 30 Oct.
The example shows a useful level of detail, not a universal team design.
First step
Bring the mandate, expected value, affected groups, and decision path.
Deep dive
How it works
The group negotiates what reliability, communication, and conflict behavior concretely mean, instead of just stating good intentions. This creates a shared reference point against which later tensions or ambiguities can be checked.
In detail
A Team Charter helps because expectations about mandate, collaboration, roles, and success criteria are made explicit early. In practice, the format holds up when it addresses real tensions instead of just producing noncommittal feel-good statements. Day to day, observable behavior, decision paths, and practical consequences matter, so the charter provides orientation in everyday work and conflicts can be addressed earlier.
Facilitation
Use the charter moment early in a collaboration and put real expectations about purpose, roles, and working style on the table. The work becomes valuable as soon as unspoken assumptions about availability, decision-making, or quality become visible. Afterward, record the few agreements that should actually govern daily work.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
In playbooks
Artifact templates
Team Charter: WorksheetPlan the question, inputs, complete run, and review with clear ownership.markdown
Team Charter: WorksheetPlan the question, inputs, complete run, and review with clear ownership.
markdownteam-charter-markdown.md
Plan the question, inputs, complete run, and review with clear ownership.
Team Charter: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Complete run Time: 75–120 minutes for the first version; review after 4–6 weeks and after material team changes.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Charter template, mandate or project brief, known goals and interfaces, role overview, and calendar for the review.
- Roles: Whole team · sponsor for mandate and boundaries · facilitator · documentation owner
- Advance information: The sponsor clarifies purpose, decision space, and hard boundaries. Team members add role, experience, capacity, and important dependencies.
- Overall time needed: 75–120 minutes for the first version; review after 4–6 weeks and after material team changes.
- Setup: Mark the draft as changeable. Clarify mandate and boundaries before roles and collaboration; collect unresolved sponsor questions separately.
Prepare for the work steps
Mandate: Clarify mandate
- The sponsor clarifies purpose, decision space, and hard boundaries. Team members add role, experience, capacity, and important dependencies.
Boundaries: Set scope
- Shared mandate
Roles: Assign responsibility
- Explicit scope
Ways of working: Agree collaboration
- Role and decision map
Review: Maintain charter
- Agreed collaboration
Team charter
Purpose and customers
Why does the team exist, whom does it help, and what value should result?
...
Outcomes and boundaries
Which outcomes does the team own, and what is explicitly outside?
...
Roles and decisions
Who decides, executes, or contributes to key outcomes?
...
Collaboration
Which channels, rhythms, and conflict paths apply?
...
Open points and review
What remains open, who resolves it, and when is the charter reviewed?
...
Clarify mandate and hard boundaries with the sponsor; write team agreements together.
Atlassian Team Charter · original teaching example
Mandate: Clarify mandate
Expected artifact: Shared mandate
Shared mandate
Entry:
...
- Can team and sponsor state the same purpose, served people, and expected value?
Boundaries: Set scope
Expected artifact: Explicit scope
Explicit scope
Entry:
...
- Are owned outcomes, out-of-scope work, and external dependencies explicit?
Roles: Assign responsibility
Expected artifact: Role and decision map
Role and decision map
Entry:
...
- For key outcomes, is it clear who decides, executes, and contributes?
Ways of working: Agree collaboration
Expected artifact: Agreed collaboration
Agreed collaboration
Entry:
...
- Are communication and conflict rules written as observable behaviour?
Review: Maintain charter
Expected artifact: Published charter with review
Published charter with review
Entry:
...
- Are unresolved mandate questions, owners, and the next review visible?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/team-charter/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Agile
Working Agreements
Instead of Team Charter, choose Working Agreements when you want to define everyday rules for the team concretely and bindingly and need them as a lived working basis.
Facilitation
Expectation Mapping
Surfaces stakeholder expectations, clusters conflicts, and turns them into concrete agreements.
Facilitation
Delegation Poker
Shows delegation levels for decision areas and creates agreements about closeness, freedom, and control.
Facilitation
Alignment Mapping
Makes goals, concerns, and open gaps visible so clarification steps can be planned deliberately.
Facilitation
Stakeholder Salience Model
Moves group input, selection, and decision toward a concrete result through "prepare the stakeholder list", "define power, legitimacy, and urgency", and "derive strategy by class".
Facilitation
3-Circle Venn Diagram
Compares three perspectives in a shared picture and makes overlaps as visible as differences.
Constraints and origin
MediumWorkshop2-4 h
Profile
- Method form
- Operating practice
- Participants
- 3-12
- Time
- 2-4 h
- Maturity
- Canonical
- Origin
- Praxisgemeinschaft
Next up: RACI Matrix