10 November 2026 · 20 min read

Team charter: a guide to your team's culture, and how it should change

What is a team charter?

Tomasz has run a team of eight for three weeks. This morning he opened a blank document called "Team charter" and has been looking at it for forty minutes. He has read four guides. All four say to start with purpose, then goals, roles and norms. He has typed "Purpose:" and stopped. The team meeting where he wants to show it is at two.

The trouble is not that he does not know what goes in it. It is that he suspects the document, once written, will do what the values poster in reception does: sit there being agreed with.

Tomasz is invented. His suspicion is worth taking seriously, and the rest of this guide does.

A team charter is a team's culture, written down: the values it holds, the skills it is building, and the plain agreements that make both visible in an ordinary week, from who owns the work to how the team disagrees. It is written by the team that will live by it, it is reviewed on a date, and it changes when the team runs into something it did not plan for.

Here is the argument of what follows. A charter that is written once is a values poster for one team, and it fades the same way. A charter that is reviewed, and rewritten when a challenge shows a gap, is the closest thing a team has to a culture it chose on purpose.

Team charter or project charter?

A project charter says what a piece of work is, who is paying for it and when it ends, and it is for the sponsor. A team charter says how a standing group behaves and what it values, it is for the people in it, and it is only finished when the team is. A team that runs projects needs both, and they should not be the same document.

Why a team charter is a culture document

Most guides treat a charter as a list of rules: reply within a day, cameras on, no meetings on Friday. Rules are the visible part, and they matter. But a rule with nothing under it is the first thing to go when the week gets hard, because nobody remembers why it was there.

The culture model MeaningFuel is built on draws culture as an iceberg. Above the waterline is behaviour: what people actually do on a Tuesday. Below it are the values and beliefs that decide that behaviour when nobody is checking. Culture as a Product goes through the model in full. A charter that lists only rules is all tip, and it melts. A charter that lists only values is all ice under water that nobody can see. The useful charter joins the two: each value it holds is paired with something you could watch somebody do.

That joining matters because the same value means different things in different rooms. "We take ownership" is a careful handover to one team and staying late to another, as When your values show up differently on every team shows. A team charter is where a team says what the company's values mean here.

Values, skills and mindsets

Values and skills do different jobs, and a charter is better for naming both.

• A value says what matters to the team. Accountability, Trust, Respect. It decides what people do when two good things pull in different directions.
• A skill says what the team is getting better at. Feedback, Collaboration, Communication. A skill is a mindset as much as a technique: a team that is "building Feedback" has agreed that asking for comment on the work is normal, not a sign of weakness.

Two or three of each is plenty. A team that holds nine values holds none of them, because nobody can say them from memory. Take the values from the company's own where it has them, and say what each one looks like on this team. Company values examples has more on choosing values that someone could act on.

What goes in a team charter?

Seven parts. The names change from guide to guide; the work does not. Under each, what goes wrong when it is missing.

1. Why the team exists. One sentence a new starter could repeat to a friend. Without it, every request looks equally urgent and the loudest one wins.
2. The values we hold. Two or three, each with one behaviour someone could watch. Without it, the rules have no reason behind them, and the first busy week breaks them.
3. The skills we are building. Two or three, each with what practising it looks like this quarter. Without it, the team has a list of manners and no direction to grow in.
4. How the work gets done. Who owns a piece of work, who looks at it before it ships, what "done" means, and where everyone can see what is in progress. Without it, the charter is a statement of intent with no plan attached.
5. Who decides, and how we talk. Which decisions belong to one person and which to the team; where questions go and how fast a reply is owed. Without it, decisions get made twice, in different rooms.
6. How we disagree. What is fair to say about the work, what is not fair to say about each other, and how to repair a remark that landed badly. Without it, disagreement goes quiet and comes out sideways.
7. How and when it changes. A review date, the name of the person who calls it, and what the team does when a challenge shows the charter is wrong. Without it, the document has no future.

The fourth part is the one most guides give a line to, and it deserves more. In a study of 32 teams of MBA students competing in a business strategy simulation, the highest sustained performance came from teams whose charters and performance strategies were both of high quality (Mathieu and Rapp, Journal of Applied Psychology, 2009). Students in a simulation are not your sales team, and it is one study. But the pairing is the useful part. A charter that describes only what the team values is half a document. The other half says how the work will be done.

A team charter example

Twelve lines for a team of eight. The team is invented, and so is every name in it. Copy what fits, and change any line you cannot imagine your team saying out loud.

1. Why we exist. We make sure a customer's problem is solved by the first person who touches it, or handed to the right person with the story attached.
2. Value: Accountability. Every piece of work has one named owner and one reviewer before it ships. The owner decides when it ships, and says so when it slips.
3. Value: Trust. Questions go in the team channel, not in private messages, so the next person finds the answer. A direct question gets a reply by the end of the next working day, even if the reply is "not yet".
4. Value: Respect. Nobody is talked over. Whoever was interrupted finishes first.
5. Skill: Feedback. Before anything ships, the owner asks one person "what would you change?" and writes the answer down, whether or not they take it.
6. Skill: Collaboration. Anything that will take more than two days goes on the board on Monday, with what "done" looks like in one sentence, so nobody finds out on Friday that two of us built the same thing.
7. Who decides. The owner decides, after asking the people the work touches. If two of us disagree and it cannot wait, Asha decides and says why in the team channel.
8. Meetings. Monday planning is thirty minutes. Anyone can say "we are not deciding this today", and the item moves to Thursday.
9. Repair. If a remark landed badly, the person who heard it says "that landed badly" and the speaker says "say more". It costs ten seconds and it is nobody's fault to say.
10. When we are split. A meeting with even one person on a screen is run as if everyone were. A decision made in a room is written in the channel the same day.
11. When something keeps going wrong. Anyone can name it at Monday planning. If it happens a third time, it goes on the agenda for the next review as a question about this charter, not about a person.
12. Looking again. We read one line of this aloud at the start of Monday planning. We review all of it when someone joins or leaves, and on the date in the calendar invite that Asha owns.

Notice what is not there. No line says "excellence" or "we are one team". Every value has a behaviour beside it that you could watch somebody do, or fail to do, on a Tuesday. That is also why it will survive an argument: a line that says "we value accountability" means one thing in each room. A line that says who owns the work, and that they say so when it slips, does not.

A team charter template

If you would rather fill in blanks than edit a draft, the same seven parts as sentences to finish:

• We exist so that ___.
• We hold ___, which here means ___. We hold ___, which here means ___.
• This quarter we are building ___, and practising it looks like ___.
• Every piece of work has ___ who ___ before it ships, and "done" means ___.
• ___ decides, after asking ___. Questions go in ___, and a direct question gets a reply by ___.
• We disagree about the work ___. We raise anything about a person ___. When a remark lands badly, we say ___.
• We look at this again on ___, and ___ calls it. When something keeps going wrong, we ___.

Anything you cannot finish in a sentence is not ready to be a clause. Leave it out for now.

A team charter for a hybrid team

Everything above still applies. A hybrid team needs a few more lines, and they are not about which days people come in. They are about the moments when the team is split across a room and a screen, which is exactly when a value like Respect or Trust is easiest to break without anyone meaning to.

Say which decisions are made in writing. If three of the eight are not in the room, a decision made in the room is not yet a decision. It is a conversation, and it becomes a decision when it is written where they can read it. Name the place, and name who writes it.

Run every meeting as if everyone were remote. The person on the screen cannot see who is about to speak, cannot catch the look that says "wait", and cannot lean in. Ask them first, and last. Say who is speaking before you speak. It feels stiff for a fortnight and then it is how the team talks.

Say what "online" means. It is a promise about replies, not about a green dot. Decide what reply time the team owes for a direct question, and write it down, because without a number each person invents their own and then resents everyone else's.

Plan for the handover, not the day. The failures in a split team happen where one person's work meets another's: the end of the day in one place, the start of it in another. A line about what a handover note must hold earns its place.

Why most team charters are forgotten

Tomasz writes a good charter. The team shapes it in an hour and a half, he reads it aloud, and everyone nods. In March it is on the screen at the start of Monday planning. In April it is not. In May a quiet colleague's suggestion is answered with a joke, and nobody says the word "charter", because saying it would make the joke a big thing. In June a new starter asks whether the team has a way of doing things, and Tomasz has to search for the file.

Nobody was careless. The charter did what it was built to do, once. The design was the problem: it spends all of its repeating on day one, and it has no way to hear about May.

Three bodies of research have the same shape, and none of them is about charters. Say so before leaning on them.

A review of 839 assessments of distributed practice in 317 experiments in 184 articles found that the study gap that gave the best retention grew as the time the material had to be remembered grew (Cepeda and colleagues, Psychological Bulletin, 2006). Those were tests of remembering words and text, not of teams. They do not show how a team keeps a norm. They are a fair reason to doubt that one workshop can hold anything for a year.

Resilience training is a different intervention again. Across 42 samples in 37 studies it had a small effect (d = 0.21) that faded: d = 0.26 soon after the training, against 0.07 at later follow-up (Vanhove and colleagues, Journal of Occupational and Organizational Psychology, 2016). That was training given to everybody, not a charter. It says that an effect measured soon after the day is not the effect on a Tuesday months later.

And in a WorkNest survey of 1,017 HR professionals and business leaders, 45% experienced an initial improvement before the problematic behaviour returned, and just 6% of organisations said behaviour improved permanently following intervention (WorkNest, via HRreview, 21 August 2026). That was about toxic behaviour, and it reports what respondents said, not a measured relapse. We went through that survey in Month four: why culture fixes fade, because the shape matters more than the number: the fix works, and then the week closes over it.

None of this proves that a charter fades. It explains why you should not be surprised when one does, and why a charter that is only ever written is the weakest version of the idea.

How to review and change a team charter

The fix is not a better document. It is putting the document back on the table, in small pieces, on a schedule that does not depend on anyone remembering, and letting it change when the team learns something. It is the case The Two-Minute Habit makes for culture in general, applied to one team.

Read one line aloud at the start of the Monday meeting. One, not the lot. The team hears the whole charter in twelve weeks, and it never takes a minute.

Put a date and a name on the review. "We will revisit this" is a wish. "Asha calls it on the first Monday of March" is a calendar invite.

Review it when someone joins or leaves. The change in the room is the moment the charter is most likely to be wrong, and the new starter is the one person who can read it as a stranger.

Delete the line nobody can say. Ask the team to write the charter from memory in five minutes. The lines that come back are the culture. The lines that do not are decoration, and a charter with fewer lines that people can say beats a longer one they cannot.

When a challenge is raised, look under the rule

The most useful review is not the one in the calendar. It is the one a problem forces. The third missed handover, the meeting where the quiet colleague was laughed off again, the mistake nobody mentioned until a customer did: each is the culture telling the team where the charter is thin.

The temptation is to add a rule. Sometimes that is right. More often the rule was already there, and what broke was underneath it. So the review asks three questions:

1. What keeps happening? Said as an event, never as a person: "handovers arrive without the story", not "Sam's handovers".
2. Is it a value or a skill? If people know what to do and choose not to, a value is missing or means different things to different people. If they want to and cannot, it is a skill the team has not built yet.
3. What changes? A line rewritten; a value added, or one dropped because nobody could say what it meant here; or a skill the team works on for a fortnight on purpose.

A team that keeps hiding mistakes has a different problem from a team that keeps missing handovers, and the charter should say so. Blame culture is the first; Working in silos is the second. If the challenge is that people have stopped saying what they think, Psychological safety at work is the place to start.

Let it lose an argument in public. When someone cites a line to settle a disagreement and it settles it, say so. When it does not settle it, change the line. A charter that is never wrong has never been used.

How to tell it has gone cold

Things that happen in a room, never adjectives:

• The file's last-edited date is the day it was written.
• A new starter has never been shown it.
• Somebody proposes a rule the charter already has.
• A meeting breaks a line and nobody mentions it.
• The same problem has come up three times and the charter has not changed.
• Asked to name one value from it, three people cannot.

If it has gone cold, the answer is the same as it was in the first place: sit down together and do it again, shorter. The team that rewrites its charter every year is not failing. It is checking.

How MeaningFuel helps a team live its charter

Writing the charter and changing it are the team's job, and nothing should take that away. What MeaningFuel carries is the part that fades: keeping the values and skills in front of people between reviews, and giving a team focused help when a challenge shows a gap.

The daily insight: values and skills, every working day

A company's culture in MeaningFuel is the values it holds and the skills it encourages, ticked from a list, and it is what the daily insight works on. Each working day everyone gets one short insight on one of them, and every value and skill the company chose takes its turn. When a team charter takes its values from that same list, the morning email is quietly reinforcing the charter between reviews.

The values that bear on most charters are Teamwork, which is people pulling together toward a shared goal; Trust, which is believing in each other and in leaders; and Accountability, which is owning your commitments and their results, including when they go wrong. The skills are Collaboration, working jointly with others to produce shared work; Communication, saying things clearly and listening well; and Feedback, giving honest comment on work and asking for it. In an ordinary week a reader might meet a line on asking for help before the struggle starts, and another on saying back what you heard. Those are the mindsets a charter's lines depend on, arriving from outside the team, on a Wednesday, for as long as the company keeps it running.

That does not enforce a clause. A problem cannot be chosen for the daily culture: that is what a module is for.

When a challenge is raised: a module

When the review finds a real problem, a module is booked for that team: a short course of daily lessons on the problem it has, ten lessons, one each working day over two working weeks. Each problem has a course of its own: Learning from Mistakes for a blame culture, Working Well Together for working in silos, Clear Communication for communication breakdowns, On the Same Side for internal conflict. Each person on the team is invited and chooses for themselves whether to take part.

Working Well Together is the nearest to a charter. In its first week the team chooses its own three norms and rehearses them daily: offers, asks, credit and turn-taking. That is a charter in miniature, chosen by the people who have to keep it. The idea borrows from CREW (Civility, Respect and Engagement in the Workplace), a programme from the US veterans' health service built on a team choosing its own norms. The team lead runs two ten-minute debriefs, halfway and at the end, from a written guide, with check-ins after, which is the part of a fix that usually has nobody's name on it. What the team learns there is good material for the next version of its charter.

What Tomasz could read

Insights is live whenever you look, and a summary arrives weekly or monthly, as you choose. Tomasz could read how much of his team takes part, week by week, pooled, with nobody named. That is a line about attention, and it is all it is. It cannot tell him whether anyone is following the charter, and it does not try to. A team can answer every morning and still talk over the quiet one. A falling line tells him where to go and ask, and a steady one tells him nothing about Monday's meeting.

What it does not do

It does not write the charter, check it or enforce it, and it promises no result. It keeps the values and skills the company chose in front of people every working day, and offers a focused fortnight when a team meets a problem it cannot talk its way out of. Whether the charter changes is still a decision the team makes.

Questions managers ask

How long should a team charter be?

Short enough to read aloud in a meeting without losing the room. That is a rule of thumb, not a finding: no study we have read gives a number. If a line needs a paragraph to explain it, it is probably two lines, or none. Two or three values and two or three skills is enough.

Who should write a team charter?

The team, with the manager speaking last. A charter handed down is a rulebook, and a charter the team wrote is an agreement, and only an agreement can be held up in a meeting with "we said we would". The manager goes last so the quietest voice is heard before the most senior one.

How often should a team review its charter?

On a date written into it, whenever someone joins or leaves, and whenever the same problem comes up three times. Quarterly is a sensible place to start, and that is a habit, not a finding. The review can be short: read it, strike what nobody can say, and ask what the last challenge showed was missing.

Should a team charter include values?

Yes, two or three, each with a behaviour beside it. A charter without values is a list of rules with no reason behind them, and rules without reasons are the first thing dropped in a hard week. Take them from the company's values where it has them, and say what each one means on this team.

Is a team charter the same as company values?

No. Company values say what the company holds. A team charter says what those values look like on this team on a Tuesday, adds the skills the team is building, and changes when the team learns something. Keeping your culture when you double covers what happens when a company grows past the point where values can be learned in the corridor.

Next Monday

Tomasz reads the first line of the charter aloud at the start of Monday planning. Nobody says anything. It takes eleven seconds.

The following Monday he reads the second.

In the ninth week, Priya says the handover line is not working: it is the third time a customer has had to tell their story twice. Nobody argues. At the review they decide it is not a missing rule but a skill the team has not built, and they rewrite the line. The charter is one line better, and it was the team that found it.

• Team Charter
• Teamwork
• Managers
• Hybrid Teams
• Workplace Culture