Team Manifesto

Purpose

A Team Manifesto is a co-created document that articulates why the team exists, what it values, how it works, and what its members promise each other. Unlike working agreements (which focus on behavioural norms), a manifesto captures identity and aspiration — it answers "Who are we at our best?"

At a glance

How to run

1. Purpose question (10 min): Ask: "Why does this team exist? What would not happen if we disappeared?" Each person writes a sentence. Share and synthesise into one team purpose statement.
2. Values brainstorm (10 min): Silent brainstorm: What values define us at our best? Cluster and vote to select 3–5 core values.
3. Principles (15 min): For each value, craft a principle: "We believe in [value], which means we [observable behaviour]." Push for specificity.
4. Promises to each other (10 min): Each person writes one promise to the team. Share aloud. These are commitments, not aspirations.
5. Design the manifesto (10 min): Arrange purpose, values, principles, and promises into a visual document. Assign someone to create a designed version.
6. Close (5 min): Each person signs (literally or metaphorically) the manifesto. Agree on when to revisit it.

Materials needed

• Large paper or digital canvas for drafting
• Sticky notes and markers
• Voting dots
• Timer
• A design template (optional, for the final version)

Pitfalls & common mistakes

• Corporate-speak: Push for authentic language. "We deliver synergistic value" says nothing. "We ship on Fridays and celebrate on Mondays" does.
• Too long: A manifesto should fit on one page. Ruthlessly edit.
• No revisiting: Review the manifesto quarterly. If it feels stale, rewrite it.
• Excluding voices: Every team member must contribute. Silent brainstorming before discussion helps.

Inclusion & accessibility

• Use silent writing before group discussion to include quieter voices.
• Allow contributions in any language, then translate together.
• Make the final manifesto visually accessible (large text, high contrast).
• Post it where all team members can see it daily — including remote members.

Variations

• Visual manifesto: Create it as an illustrated poster or infographic.
• Video manifesto: Record each person reading their promise and compile into a short video.
• Evolving manifesto: Use a living digital document that the team updates as it evolves.

When NOT to use this

• When the team is temporary (less than 2 months) and will disband before the manifesto matters.
• When leadership dictates the manifesto content — it must be co-created to have meaning.
• When there is deep, unresolved conflict — address that before trying to articulate shared identity.

Source & further reading

• Simon Sinek, *Start with Why* (Portfolio, 2009)
• Daniel Coyle, *The Culture Code* (Bantam, 2018)
• Agile Manifesto (agilemanifesto.org) — as a structural inspiration