Team Norms Examples That Change Actual Behavior

What is a team norm, and what makes one work?

A team norm is an agreed rule about how a team behaves, and it changes behavior only when it names three things: an observable action, the moment that triggers it, and what happens when someone skips it. Most published norms name none of the three. That is why a charter written at the January offsite is dead by March and nobody mentions it.

Compare two lines I have seen on real charters. The first: "we communicate openly." The second: "if a date is going to slip, you post it in the team channel within 24 hours of knowing." One is a value with a verb attached. The other is something a stranger could sit in your Tuesday stand-up and tick as kept or broken.

That tick test is the whole difference. If nobody in the room can tell in the moment whether the norm was followed or broken, it is a sentiment, and sentiments do not survive a bad quarter.

Teams land in the vague version for an understandable reason. Norms get written at an offsite, in a good mood, by people describing who they want to be. Naming an actual behavior feels small next to that, so the list gets rounded up into values and filed.

Twenty team norms, vague version and usable version

Below are twenty norms I have seen written down, each rewritten into a version a team can check. Read the first half as what the team meant and the second as what they should have written.

• "We communicate openly" becomes "if a date is going to slip, you post it in the team channel within 24 hours of knowing."
• "We respect each other's time" becomes "meetings end at 50 past, and anything unfinished goes on next week's agenda before anyone stands up."
• "We hold each other accountable" becomes "every decision leaves the meeting with one named owner and a date, written into the notes."
• "We assume positive intent" becomes "if a message reads as sharp, you ask the sender what they meant before you reply or forward it."
• "We value transparency" becomes "no decision lives only in a DM, and the project board is readable by anyone without asking."
• "We are customer-focused" becomes "every spec opens with one sentence naming who asked for this, in their words."
• "We welcome feedback" becomes "feedback goes to the person first and to their manager second, never in the other order."
• "We support each other" becomes "if you finish early, you post your spare capacity in the channel instead of starting something new."
• "We are data-driven" becomes "a claim about users arrives with a number and a link, or it gets labelled a hunch in the doc."
• "We are inclusive" becomes "in any meeting over four people, the facilitator asks the two quietest for their read before the decision."
• "We protect work-life balance" becomes "messages written after 18:00 are scheduled to send at 08:00 unless the subject line says urgent."
• "We stay aligned" becomes "the weekly update says what changed since last week, not what happened last week."
• "We escalate early" becomes "a blocker older than one working day goes to the owner and the manager the same day."
• "We care about quality" becomes "nothing merges without one reviewer who wrote none of it."
• "We document decisions" becomes "any decision that took more than 20 minutes gets three lines in the log that day."
• "We respect deep work" becomes "Tuesday and Thursday mornings carry no internal meetings, and the calendar block is there to prove it."
• "We disagree and commit" becomes "objections get raised in the room, and nobody reopens the decision in a side channel afterwards."
• "We share credit" becomes "whoever did the work presents it, including when a director is in the room."
• "We onboard well" becomes "a new joiner gets a named buddy, one shipped task in week one, and a daily question slot."
• "We learn from our mistakes" becomes "every incident gets a written note within 48 hours naming the cause and the fix, and naming no person."

Do not adopt all twenty. Pick the five that name the failures your team actually repeats, and leave the rest.

How to write a norm your team will follow

The rule has three parts, and a norm missing any one of them will drift back into a value within a month.

1. Name the action, in the verb form somebody performs. "Post the slipping date," not "be transparent about timelines." If you cannot picture a person doing it, neither can they.
2. Name the trigger. The moment the norm fires: when a date slips, when a decision is made, when a message lands badly. A norm with no trigger applies always, which means it applies never.
3. Name the response. What a teammate does the first time it is skipped. Usually one sentence in the moment, which is cheap enough that people will actually do it. Save escalation for a pattern.

Write them with the team, using examples of things that have already gone wrong. The prompt that works is not "what do we value here." It is "what went wrong in the last month that we would rather not repeat, and what would somebody have had to do differently on the day it happened."

Role clarity is not a soft preference here. Bernuzzi, Sommovigo, Maffoni, Setti and Argentero found in the Journal of Change Management (2023) that role clarity carried the link between how employees read an organizational change and how resilient they were through it, and that supervisor support strengthened that link. Ownership norms are the ones that do that job on a team, which is part of why they tend to be the ones that stick.

Team norms and team values do different jobs

A value states what a team believes matters. A norm states what the team does on a Tuesday, in a specific moment, whether or not anybody feels like it that day. Both are legitimate. They just do different work, and the damage comes from writing one and expecting the other to happen.

Values usually arrive from the company and apply to everybody in it. Norms belong to one group of six or ten people and describe how that group handles slipping dates, disagreement, feedback and credit. A norm that never gets demonstrated is dead on the page.

If you want a vocabulary for sorting a norms list, the 12 Cs of Trust covers the ground most norms try to protect: Clarify (who owns what, by when), Consistency (the same standard on a bad week), and Caring (what the team does when somebody is underwater). The 12 Cs are a scored behavioral framework rather than a charter, so use them to check your coverage. The norms stay in the team's own words.

Who enforces a norm

Whoever is in the room when it is broken, which most of the time is not the manager. That is the honest answer, and it is the one nobody wants, because the norm only works if ordinary people will say an awkward sentence at an awkward moment.

Norms about speaking up are doing work that Amy Edmondson documented in Administrative Science Quarterly in 1999: people privately weigh the interpersonal risk of raising something before they raise it. A norm that names the exact action lowers what they have to weigh, because the person is not judging the situation from scratch. They are pointing at a line the team already agreed to.

Then there is the case everybody avoids. The person breaking the norm is the manager, and the room goes quiet. A norm survives its first senior violation or it does not survive at all, so settle that before it happens. Agree that anyone can say "that one is on the list" without it counting as a confrontation, and as the manager, say it about yourself the first time you slip.

When to review them

Every 90 days, 30 minutes, list on screen. Two norms should come off.

The first is the one nobody has had to invoke in three months. It reads well, it was never the actual problem, and it is taking one of your five slots. The second is the one that gets broken most weeks with no response. Keeping that one is worse than dropping it, because every unenforced line teaches the team that the list is optional, including the four lines that were working.

Then check whether the behavior underneath the norms has moved, which is a different question from whether the norms are being followed. That is what a behavioral score is for, and I have written up the mechanics in how to measure trust. A team can follow all five norms and still coordinate badly.

FAQ

What are examples of team norms?

Usable examples name a behavior and the moment it applies: post a slipping date in the team channel within 24 hours of knowing, end every meeting with one named owner and a date per decision, send feedback to the person before their manager, and ask the two quietest people in the room for their read before a decision is made. Norms phrased as values, such as we communicate openly, are not examples of anything a team can follow.

What is the difference between team norms and team values?

A value states what a team believes matters. A norm states what the team does on a Tuesday, in a specific moment, whether or not anyone feels like it. Values usually come from the company and apply to everyone. Norms belong to one team of six or ten people and describe how that group handles slipping dates, disagreement, feedback and credit. Values are chosen. Norms are enforced, which is why they change behavior.

How many norms should a team have?

Five is a working set. Six is pushing it. A list of twelve is a list nobody has read since the offsite where it was written. Choose the five that name the failures your team actually repeats this quarter, review them in 90 days, and retire whatever has stopped earning its place. A short enforceable list beats a complete unenforceable one every time.

Who should write the team norms?

The team writes them, in a working session, using examples of things that have already gone wrong. A manager who arrives with a finished list gets compliance for about three weeks. The useful prompt is not what do we value. It is what went wrong in the last month that we would rather not repeat, and what would somebody have had to do differently on the day it happened.

What do you do when someone breaks a norm?

Name it in the moment, in one sentence, without a meeting. That is the whole intervention, and it works because it is cheap enough to do every time. Escalate only on a pattern, not on a first instance. If the breach came from the most senior person in the room and nobody says anything, the list is finished, so agree in advance how the team will flag that case.

How often should team norms be reviewed?

Every 90 days, in a 30-minute session with the list on screen. Retire two kinds of norm. The first is the one nobody has had to invoke in three months, because it was never the real problem. The second is the one that gets broken weekly with no response, because keeping it teaches the team that the whole list is optional.

The reason to get this right is not tidiness. A team that can name what it does under pressure can also tell when it has stopped doing it, and that is the earliest warning you get. If you want a baseline before you write the list, the team trust score takes about three minutes and tells you which behaviors your norms need to cover.

Related reading