Explicit is Better than Implicit: Making Culture Visible with Team Charters
summary
Describes a team charter as a tangible document with sections for purpose, values and responsibilities, goals/KPIs, meeting norms, ground rules and duration, with concrete examples like a "connect our customers" purpose statement and a weekly status plus a monthly "Danger Room" demo. Recommends a 5–8 hour workshop (run 12 times over five years) to write one, uses the Zen of Python principles Explicit is better than implicit and There should be one and preferably only one obvious way to do it, and publishes a GitHub template to reuse.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:51Today's Journey
- 1:34Background: The Zen of Python
- 2:33What is a Team Charter?
- 3:32Why Would I Want a Team Charter?
- 7:49What is a High Performing Team?
- 9:46Elements of a High Performing Team
- 13:14Purpose
- 15:16Values and Responsibilities
- 16:49Goals and Measurements (KPI)
- 17:11Meeting Norms
- 18:43Ground Rules
- 20:12Mapping Team Charter to High Performing Teams
- 21:27It's A Living Document
- 23:06Try It At Home: Workshop
related talks
43mEmpowerment in action
26mWe're Agile, We Don't Do Documentation
41mProject Discovery & Liftoff with Agile Chartering
27mInspire Great Culture In Your Organization
20mDesigning Culture
24mRadical Transparency: Leading Engineering With Openness
01h 35mBuilding Awesome Teams Using The Team Collaboration Canvas
52mSecrets of a Strong Engineering Culture