Team norms: examples, how to agree on them, and where the written version lives (2026)

Most team norms fail the same way: they are agreed in a workshop, written on a slide, and never read again. Six weeks later the team runs on the habits it had before, the new hire learns the real rules by breaking them, and the slide describes a team that never existed. The norms that hold are the ones that are specific enough to check, short enough to read, kept somewhere the team already looks every day, and reviewed on a date someone owns.

That is the whole method. A norm is a sentence about behaviour, not a value: "we answer a question in the team channel the same working day" is a norm; "we communicate openly" is a wish. The list is one page. It lives in the team's channel, not in a folder. It has an owner and a review date. And in a team where people write in more than one language, the norm about language is the first one to write down, because every other norm depends on whether the people it concerns can read it.

This guide is the craft first — what team norms are and what they are not, what a norm needs to be followed, examples by category — then how a team agrees on its own in an hour, a template you can copy, a filled-in example for a team of twelve on three sites, the documented place the norms live in the tools you already pay for, and one way the written version stays readable by every member.

What team norms are — and what they aren't

Team norms are the rules a team has agreed about how it works together: how fast people answer, how meetings run, how decisions are made and where they are written, when people are reachable, how feedback is given, and what language the team writes in. A norm describes behaviour that anyone on the team can observe, so the team can tell whether it was kept without a manager deciding. The list is short — a team that can recite its norms has the right number — and it is agreed by the people it binds, which is what separates a norm from a policy.

The term is easy to confuse with four neighbours, and the confusion is why norm documents get long.

Two of the five are the team's to write: the norms and, as a section inside them, the meeting ground rules. The rest arrive from above. A norms page that restates the remote work policy or the values is longer than it needs to be and is read less for it.

What a norm needs to be followed

Four things, each of which is missing from most norm lists.

1. A behaviour, not a quality. "Be responsive" cannot be kept or broken. "A question in the team channel gets an answer, or an 'I'll get back to you by Thursday', the same working day" can. If a norm has no verb a person could do by five o'clock, rewrite it.
2. A trigger and a boundary. Say when the norm applies and where it stops: in the team channel, during the team's core hours, for decisions that affect more than one person. A norm with no boundary is applied to everything, which means nothing.
3. A place where the written version lives and is read. A norm on a slide in a shared drive is a norm the new hire never sees. The written version belongs where the team already looks every day — pinned in the team's channel — and the people it binds must be able to read it, which in a team across languages is a decision, not an assumption.
4. An owner and a review date. One name, one date three months out. The owner does not enforce the norms; the owner opens the page on the date, asks "which of these did we actually do?", and deletes the ones nobody kept. A norms page that only grows is one nobody reads.

A test that catches most weak norms: read the sentence aloud and ask whether a colleague could point to a day last week when it was kept or broken. If not, it is a value wearing a norm's clothes.

Team norms examples by category

The categories below cover what most teams argue about. A team needs a norm in each category where it has had the argument, and none where it has not. Eight to twelve norms in total is typical; twenty is a policy.

Communication and response times

• A question in the team channel gets an answer, or a named person and a date, the same working day. Email is two working days. Nothing urgent goes by email.
• Direct messages are for the two people in them. Anything someone else might need to know goes in the channel, so the record is in one place.
• Threads, not new messages, for replies: one topic, one thread, readable from the top a month later.

Meetings

• No agenda, no meeting: the agenda is posted in the channel the day before, with the decision each item needs. The meeting agenda template covers the form.
• Decisions are read back in the last five minutes and written down the same day, with an owner and a date for each action item.
• Default length is twenty-five minutes; cameras are each person's choice; one person late does not restart the meeting.

Decisions

• Every decision that affects more than one person has one owner, is written in the team channel the day it is made, and names the reason — so it can be revisited when the reason changes rather than relitigated when someone forgets it.
• Silence for two working days after a proposal in the channel is agreement.
• A decision made in a direct message or a hallway is not made until it is in the channel.

Written status

• Each person posts a short status in the channel by the set time: done, next, blocked. Nobody is asked for a status in a meeting that was already posted.
• The status is three lines, not a report; links go to the thing, not to a summary of the thing.

Availability and focus

• Core hours are the overlap when everyone is reachable; outside them, nobody is expected to answer, and nobody apologises for not answering.
• Two half-days a week are meeting-free for everyone; the calendar shows them as busy.
• Out of office is written in the channel with the date back and the person covering.

Feedback

• Feedback goes to the person first, in private, within a week of the thing it concerns; it names the behaviour and its effect, not the person's character.
• Praise goes in the channel; the rest does not.

Language

• Everyone writes in the language they think in; the team's space is where each member reads in their own language. If the tool cannot do that, the team names one working language and writes down who it costs.
• Anything the whole team must act on — a decision, a deadline, a change of plan — is written, not only said in a call, so the members who read a different language have the same record as the ones who heard it.

The last category is the one most norm lists leave out, and in a team with a Milan office, a Spanish sales lead and a Romanian support desk it is the one that decides whether the other eleven are read.

How to agree on team norms in an hour

Norms imposed by a manager are a policy; norms agreed by the team are kept. The process below takes one meeting and a week of silence.

Before the meeting — collect, one week out. Ask each member, in the channel, for the three things about working together that cost them the most time last month: the unanswered question, the meeting without a decision, the file that arrived in a language they do not read. Anonymity is not needed; specificity is. The answers are the agenda. A team that has had no friction does not need norms yet; it needs a date to ask again.

During the meeting — draft, decide, cut. Group the answers into the categories above and draft one sentence per group that would have prevented the cost. Read each draft against the four tests: behaviour, boundary, place, owner. Argue about the ones people disagree with — the argument is the point, because a norm nobody disagreed with is one nobody will notice — and cut anything that survives only because nobody cared enough to object. End with eight to twelve sentences, an owner for the page, and a review date three months out. Read the list back in the last five minutes.

After the meeting — publish where the team looks. Post the list as a note in the team's channel and pin it, so it is the first thing a new member finds and the thing an existing member is sent to when a norm is broken. The two-day silence rule applies to the norms themselves: if nobody objects in the channel within two working days, the list is the team's. Members who join later read it on their first day and may propose a change at the next review, not before.

On the review date — delete first. The owner opens the page and asks, for each norm, whether a colleague can point to a week when it was kept. The ones nobody kept are deleted or rewritten; the ones everyone kept without thinking are deleted too, because they have become habits and no longer need a page. New norms come from the last three months' friction, collected the same way. The page gets a "last reviewed" line with the date, and the next date.

Nothing above needs a workshop facilitator or a template bought from anyone; it needs one meeting with an agenda and a place to pin the result.

Team norms template

Copy the block below into the team's channel as a note, fill in the brackets, pin it. Delete every row the team did not argue about.

[Team name] — how we work together
Agreed: [date] · Owner: [name] · Review: [date three months out] · Last reviewed: [date]
Response times: a question in [channel] gets an answer, or a name and a date, by [time or "same working day"]. Email: [two working days]. Urgent: [call or message, never email].
Where things are written: anything another member might need is in [channel], not in a direct message. One topic, one thread.
Meetings: agenda in [channel] by [the day before], with the decision each item needs. Decisions read back in the last five minutes; written in [channel] by [the same day]. Default length [25 minutes].
Decisions: one owner each; written the day they are made with the reason. Silence for [two working days] after a proposal is agreement. Not in the channel, not decided.
Status: each member posts done / next / blocked in [channel] by [time, day]. Nobody repeats a posted status in a meeting.
Availability: core hours [time range, time zone]; outside them, no answer is expected. Meeting-free: [days or half-days]. Out of office: date back and cover named in [channel].
Feedback: to the person first, in private, within [a week]; the behaviour and its effect. Praise in [channel].
Language: each member writes in [their own language / the team's working language]; anything the whole team must act on is written in [channel], not only said in a call.
Changes: proposed in [channel], decided at the review; new members read this page on day one.

The brackets are deliberate: a norms page with no blanks left to fill was copied, not agreed, and the team will treat it that way.

A filled-in example: a team of twelve on three sites

A distributor of professional kitchen equipment with its office in Bologna, a sales lead in Valencia and a four-person support desk in Cluj. Twelve people, three languages, one team channel, and a client who joins the channel for the duration of each installation project.

Equipment team — how we work together
Agreed: 14 October 2026 · Owner: Giulia (ops) · Review: 14 January 2027 · Last reviewed: 14 October 2026
Response times: a question in #equipment gets an answer, or a name and a date, the same working day. Email: two working days. Urgent: a call, never email.
Where things are written: anything another member might need goes in #equipment, not in a direct message. One installation, one thread, from the order to the handover.
Meetings: the Monday agenda is in #equipment by Friday noon, with the decision each item needs. Decisions are read back in the last five minutes; the recap is in the channel the same day. Default length 25 minutes; Thursday afternoons are meeting-free for everyone.
Decisions: one owner each, written the day they are made with the reason. Silence for two working days after a proposal in #equipment is agreement. A decision made by phone with the client is written in the thread before the end of the day, or it did not happen.
Status: done / next / blocked in #equipment by 10:00 CET on Monday and Thursday. Support posts the week's open tickets by count, not by list.
Availability: core hours 10:00–16:00 CET; Cluj is one hour ahead and Valencia's lunch is later, so nobody expects an answer between 13:00 and 15:00 anywhere. Out of office: date back and cover named in the channel.
Feedback: to the person first, in private, within a week. Praise in #equipment, in your own language.
Language: everyone writes in their own language — Italian, Spanish or Romanian — and reads the channel in theirs; the client reads it in German. Anything the whole team must act on is written in the channel, not only said in the Monday call. The installation checklist is a note in the channel, not an attachment.
Changes: proposed in #equipment, decided at the January review; new members and each project's client read this page on day one.

Three of the twelve norms came from last quarter's friction: the Romanian support desk had been learning about changed delivery dates from the client rather than from the team, because the change was agreed by phone in Italian and never written; the Valencia lead was answering Bologna's messages at midnight; and the installation checklist existed in two languages, one of them a version behind. Each norm names the behaviour that would have prevented the cost, and the language norm is the one the team argued about longest.

Where the written version lives in the tools you already use

Each suite has a place to pin or save a page the team reads, and each stops at a different point. The language of the record is the same everywhere: the one it was typed in. Documented behaviour only, from the vendors' own pages, with the month each page was checked:

The pattern is the same in all four. The norms page exists once, in the language it was typed in, and the member who reads another language reads that or a copy somebody made. The translation each suite documents belongs to the reader's own screen or to the call while it runs, not to the record — which is why the language norm in the example above costs the Bologna team a second copy of every page, and why the copy is a version behind. What a meeting leaves behind follows the same rule; where the transcript and summary go after the call is the longer version.

How the norms stay in one channel every member reads

InterMIND is a communication space where a team's work lives in a channel, so the norms have an obvious home: the channel of the team they bind — the equipment team, the clinic's front desk, the agency's account group — and that channel is where the Monday call, the status posts and the decisions happen too. Posted as a note — a rich-text message with headings and bold lines, edited later from its own menu — the norms are read by each member in their own language, with the original a toggle away, and pinned so the current version is the first thing a new member finds; with edit history switched on, the earlier wording of a changed norm appears above the current text with its timestamp, which is the review trail the owner's "last reviewed" line points to. The installation checklist in the example is the same kind of note, in one place, not an attachment in two languages. During the Monday call the norms, or the agenda written under them, go on everyone's screen next to the video tiles with Share to conference, and each participant reads them in their own language while the sharer edits live. When the call ends, the recap is written from the meeting itself — the summary, the decisions read back, the action items with owners — and arrives by email, as a message in the channel and as a link in the calendar event, readable by every signed-in member in their own language; any member can edit it, every edit keeps author and revision history, and the channel keeps the recap of every past session next to the norms that governed it. If the master copy of the page stays in a document tool, its updates land in the channel by email: the channel's host gives it an address of its own, and a message sent there appears as a regular message with the sender named and attachments kept.

The people a team's norms bind are not always employees. The client who reads the installation thread for three months, the freelance installer, the distributor's order clerk: an external member of the channel joins by email onto a free account and reads the norms, the thread and its history like everyone else, in their own language. A person without an account is a guest of one meeting — they join the Monday call by link, from a phone, at no cost, hear it live in their own language, and get no record afterwards.

The host provides the space and, on a paid plan, pays only for the members active in the previous 28 days — joined a meeting, wrote in a chat or asked the assistant. Members who go quiet keep their access at no cost, which is what a norms page needs: the colleague on parental leave who comes back in March still finds the page, and the January review, where they left them.

• Open a complete recap — a real record rendered by the same code that writes yours.
• Try the live demo — no signup; speak, and hear the room translated per listener.

Team norms as a craft survive every tool: somebody still has to collect the friction, run the hour, write sentences with verbs in them, pin the page and open it on the review date. What does not have to survive is the second job — keeping a translated copy of the norms, the checklist and every recap by hand, one language at a time, for the office that reads the other one.

FAQ

What are team norms?

Team norms are the agreed, written rules of how a team works together day to day: how quickly people answer, how meetings run, how decisions are made and recorded, when people are reachable, how feedback is given and what language the team writes in. A norm describes a behaviour anyone on the team can observe, so the team can tell whether it was kept. Norms are agreed by the people they bind, which is what makes them norms rather than a policy handed down.

What are some examples of team norms?

"A question in the team channel gets an answer, or a name and a date, the same working day." "No agenda, no meeting; decisions are read back in the last five minutes and written down the same day." "Every decision has one owner and is written in the channel with its reason." "Core hours are 10:00 to 16:00; outside them nobody is expected to answer." "Feedback goes to the person first, in private, within a week." "Everyone writes in their own language; anything the whole team must act on is written, not only said in a call." Each names a behaviour, a place and a boundary.

How do you establish team norms?

Collect, in the channel, the three things about working together that cost each member the most time last month. In one meeting, draft one sentence per group of answers, test each for a behaviour, a boundary, a place and an owner, argue about the contested ones, and cut the rest to eight to twelve. Post the list as a note in the team's channel, pin it, and treat two working days of silence as agreement. Put one owner's name and a review date three months out on the page, and on that date delete before you add.

What is the difference between team norms and ground rules?

Ground rules usually govern one setting — a meeting, a workshop — and say how people behave inside it: who speaks, for how long, what leaves the room. Team norms cover the whole of the team's working day: the chat, the decisions made between meetings, availability, feedback and language, with meeting ground rules as one section among several. A team working agreement is, in most teams, the same thing as team norms by another name.

How many team norms should a team have?

Enough that each one answers an argument the team has actually had, and few enough that members can recite them: eight to twelve is typical, twenty is a policy. A norm nobody disagreed with is one nobody will notice being broken, and a norm everyone keeps without thinking has become a habit and can come off the page. The review date exists so the list shrinks as well as grows.

Where should team norms be documented?

Where the team already looks every day: pinned in the team's channel, as a note members can read on a phone without asking anyone, not as a slide in a shared drive. In Teams, Slack, Google Workspace and WhatsApp the page lives in the channel, canvas, Doc or group chat in the language it was written, and a member who reads another language reads a per-reader translation or a copy. InterMIND keeps the note, the chat and every meeting's recap in one channel, read by each member in their own language, next to those tools rather than instead of them.

How often should team norms be reviewed?

Every three months, by the named owner, on a date written on the page. The review starts with deletion — norms nobody kept and norms that have become habits — and adds only what the last quarter's friction asks for. A page that has not changed in a year is either a team that has not changed or a page nobody opens; the "last reviewed" line tells a new member which.

Sources: Microsoft — Take meeting notes in Microsoft Teams; Microsoft — Translate a message in Microsoft Teams; Google Chat — Use Automatic Translation in Chat; Google Meet — "Take notes for me" in Google Meet; Slack — Pricing; Slack — Customize data retention in Slack; Slack — Export your workspace data; Slack — Guide to AI features in Slack; Slack — Meeting agenda template (canvas); WhatsApp — How to export your chat history; WhatsApp — Privacy policy; WhatsApp blog — Introducing message translations. The Teams meeting-notes page, the Slack canvas template page and the Google "Take notes for me" page checked October 2026; the Teams message-translation page, the Slack pricing, retention, export and AI-features pages, the Google Chat translation page and the WhatsApp pages checked August 2026. Vendors change plans, features and language lists over time; check their pages for the current state.