RunsheetFacilitation

Team Charter

ComplexityMedium

Time2-4 h

Participants3-12

FormatWorkshop

MaturityCanonical

Preparation

What needs to be ready before start

Materials

Whiteboard or Miro board with sections Purpose, Goals, Stakeholders, Roles, Working Agreements, Decision Rights, Cadence; sticky notes; pens; template for final charter.

People / roles

One facilitator who guides through sections and keeps energy; all team members (three to twelve); one stakeholder representative (for example sponsor) for phase 1; one scribe for final charter.

Pre-read

Client briefing (why does team exist?); stakeholder list; known constraints (budget, time, tooling); existing charters of similar teams as reference.

Time needed

2-4 h

Setup

Mark sections on board. Invite sponsor or stakeholder to phase 1. Phones away, no parallel Slack work. Announce charter as living document.

Core question

The one question this method answers

Why does the team exist, how does it measure success, and how does it collaborate so everyone knows what to expect from each other?

Flow

Marker: Sektion

Step	Duration	Action	Hint
1Section 1: Purpose and stakeholders	30-45 min	Sponsor or stakeholder describes mission and expectations in 10 min. Team formulates own purpose sentence. Stakeholder list with expectations per stakeholder.	If sponsor expectation and team understanding diverge strongly, clarify immediately. Charter without shared purpose is theater.
2Section 2: Goals and success measures	30-45 min	Concrete goals for next 6-12 months. Success measure per goal (for example North Star Metric, OKR hint). Define quarterly review cadence for goals.	Goals are not activities. "We develop feature X" is activity, "Time-to-First-Value falls from 6 to 3 weeks" is goal.
3Section 3: Roles and responsibilities	30-45 min	For each role (PM, Tech Lead, Designer, etc.) clarify: what is responsibility, what authority, what interface to other roles? Sketch RACI or DACI per key decision.	Role conflicts are more common than people conflicts. Work through concrete examples per interface (for example PM <-> Tech Lead).
4Section 4: Working Agreements	30-45 min	Work rules for communication, meetings, async work, decision making. Maximum 7-10 rules. Every rule with concrete behavior expectation.	Rules must be checkable. "We communicate respectfully" is not checkable, "We respond to pings during working hours in under 4 h" is.
5Section 5: Cadence and review	15-30 min	Define recurring appointments (standup, planning, retro, review). Charter review cadence (for example quarterly). Ownership for charter maintenance.	Charter will be revised in first quarterly review anyway. First version does not need to be perfect, only honest.

Artifact

What comes out at the end

Form

Team Charter document with five sections (Purpose, goals, roles, Working Agreements, Cadence), team list, stakeholder list with expectations and charter review date. Maximum 3-5 pages.

Versioning / ownership

Quarterly review with change log at beginning. Larger reorganization (new mission, new team members with significant role) creates v2; keep old version as snapshot.

Tool alternatives

Confluence page in team space
Notion page with database links
Markdown in team repo under docs/team/
Google Doc with comment function

team-charter-markdown.md

Template for team purpose, roles, ways of working, interfaces, and review date.

Team Charter

Purpose

Why does this team exist?

Goals

Roles

Role	Person	Responsibility

Ways of working

Meetings:
Communication channels:
Decision paths:

Interfaces

Which teams do we work with, and how?

Review

When do we review the charter?

Example output

Concrete filled scenario, fictional example

team-charter-beispiel.md

Concrete filled scenario, fictional example

Team Charter — Discovery Team "Activate" (Q3 2026)

Purpose: We help solo tax advisors like Sabine experience our product's aha moment in the first 30 days.

Q3 goals:

Activation Rate from 22% to 38%. Success measure: Amplitude, Cohort 90 days.
Time-to-First-Value under 3 min. Success measure: event tracking.

Stakeholders: CPO (expectation: monthly review), Customer Success (handoff protocol), Sales (lead-qualification feedback), Engineering Platform (tooling support).

Roles:

Anna (PM): Discovery, prioritization, stakeholder communication.
Ben (Tech Lead): Architecture, spike reviews, tech interfaces.
Lisa (UX Researcher): Interview wave, synthesis, insights repository.
Marcus (Designer): Prototyping, design review, pattern library.

Working Agreements:

Standup Mon/Wed/Fri 9:30, max 15 min.
Async update by Tue and Thu 18:00 in #activate-async.
Code review within 1 working day.
Discussions over 5 messages in Slack -> 30 min sync call.
Decisions via DACI with Anna as A.

Charter formulated by team without aligning sponsor expectation.

What to do

Sponsor required in phase 1. If asymmetry between sponsor expectation and team purpose, clarify before charter completion.

Stop criteria

Done signals checkable in under a minute

Team does not exist durably, charter is bureaucracy for one-time task.

Sponsor or stakeholder unavailable, purpose alignment impossible.

Team members over 12, charter discussion becomes too large.

Workshop scheduled under 90 min, five sections not feasible.

Acute team conflict, charter workshop becomes stage instead of tool.

Team not autonomous enough, Working Agreements overwritten by organization anyway.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods