Team norms are the shared, agreed rules for how a team works together: how you communicate, run meetings, make decisions, give feedback and handle disagreements. Good norms are specific (“we reply to direct messages within one working day”), agreed by the whole team rather than imposed, written down where everyone can see them and reviewed every few months.
Setting them usually takes a single workshop of an hour or so, and it prevents many of the everyday frustrations that slow teams down, from meetings that start late to confusion over who owns a decision. This guide explains why norms matter, the main types, a step-by-step process for creating them, examples and a template you can adapt, and how to keep them alive once they are agreed.
What Are Team Norms?
Every team already has norms, whether or not anyone has written them down. If meetings always start five minutes late, or people send urgent requests at 10pm and expect a reply, those are norms. The difference with explicit norms is that the team chooses them on purpose instead of drifting into them.
The idea is closely linked to Bruce Tuckman’s well-known model of team development, in which groups move through forming, storming, norming and performing. Agreeing norms early helps a team get through the “storming” stage of friction faster and with less damage to working relationships.
Team Norms vs Policies, Values and Charters
People often mix these terms up, so it helps to separate them:
| Term | What it covers | Example |
|---|---|---|
| Company policy | Organisation-wide and legal rules | Annual leave, data protection, expenses |
| Team values | Broad principles the team cares about | Openness, respect, quality |
| Team norms | Specific, observable day-to-day behaviours | “Meetings start on time and end with named actions” |
| Team charter | A wider document that can include purpose, roles, goals and norms | A one-page team agreement for a new project |
Norms sit underneath company policy and turn values into behaviour. If a value is “respect”, a norm might be “we do not interrupt, and we use the raise-hand button on calls”.
Why Team Norms Matter
Clear norms pay off in several practical ways:
- Fewer misunderstandings: people stop guessing what others expect, from response times to what “done” means.
- Psychological safety: Google’s widely cited Project Aristotle research into effective teams found that psychological safety, the sense that you can speak up or admit mistakes without being punished, mattered more than who was on the team. Norms about respectful challenge and blameless reviews help build that safety.
- Faster decisions: knowing who decides, and how, removes long email chains and repeated debates.
- Easier onboarding: new starters can read how the team works instead of learning by trial and error.
- Fairer workloads and wellbeing: agreed boundaries on out-of-hours messages and focus time protect people from burnout.
Types of Team Norms, with Examples
Most norms fall into a handful of categories. Use these as prompts when you draft your own.
| Type | Questions it answers | Example norm |
|---|---|---|
| Communication | Which channel for what? How fast should people reply? | Urgent issues go by phone or a tagged message; email replies within one working day |
| Meetings | When do we meet? Is there always an agenda? | No agenda, no meeting; start and finish on time; actions recorded before we leave |
| Decision-making | Who decides? Consensus, vote or owner decides? | The work owner decides after consulting; big decisions need input from everyone affected |
| Feedback | How and when do we give feedback? | Feedback is specific, private if critical, and given within a week |
| Conflict | What happens when we disagree? | Disagree in the room, commit once decided; escalate to the lead after two unresolved discussions |
| Availability and hours | When can we be contacted? | No expectation of replies outside core hours; use scheduled send for late messages |
| Accountability | How do we track commitments? | Every task has one named owner and a due date on the team board |
How to Create Team Norms: A Step-by-Step Process
You can do this in a 60 to 90 minute session, in person or on a video call with a shared whiteboard.
- Explain the purpose. Tell the team you want to agree how you work together, and that the norms will be reviewed, not set in stone.
- Look back. Ask everyone to think of the best and worst team they have worked in. What behaviours made the difference? Capture themes on sticky notes.
- Identify friction points. Ask what currently frustrates people: meeting overload, unclear priorities, late handovers. These show where norms are most needed.
- Draft norms by category. Use the table above as prompts. Write each norm as a specific, observable behaviour. “Respect each other” is a value; “we do not interrupt” is a norm.
- Prioritise. Dot-vote to choose the most important five to ten. Too many norms are impossible to remember.
- Agree how norms are upheld. Decide what happens when someone breaks one, for example a friendly reminder from anyone, not just the manager.
- Write them down and share them. Put them in the team’s shared space, pin them in your chat tool and include them in onboarding.
- Set a review date. Revisit them after about three months and whenever the team changes significantly.
Sample Workshop Agenda
| Time | Activity | Output |
|---|---|---|
| 0 to 10 min | Purpose and ground rules for the session | Shared understanding of why you are doing this |
| 10 to 25 min | Best and worst team reflection | Themes on sticky notes |
| 25 to 40 min | Current friction points | A short list of problem areas |
| 40 to 65 min | Draft norms by category | Specific, behaviour-based statements |
| 65 to 80 min | Dot-vote and refine wording | Five to ten agreed norms |
| 80 to 90 min | Agree upkeep and review date | Owner for the document and a date in the diary |
Facilitation Tips
- Ask people to write ideas silently first, then share. It stops the loudest voices setting the agenda.
- If someone suggests a vague norm, ask “what would that look like on a normal Tuesday?” until it becomes observable.
- Have someone other than the manager facilitate if possible, so people feel freer to be honest.
- Test each draft norm with one question: would a new starter know exactly what to do after reading it?
Norms for Remote and Hybrid Teams
Distributed teams rely on norms even more, because many of the cues you pick up in an office disappear. Useful areas to agree on include:
- Channels: which tool is for quick chat, which for decisions, and where the official record of decisions lives.
- Cameras: on by default for small discussions, optional for large briefings, with understanding for bandwidth or personal circumstances.
- Hybrid fairness: if one person joins remotely, everyone joins from their own laptop so the remote person is not at a disadvantage.
- Status and focus time: use calendar blocks and status indicators so colleagues know when you are heads-down.
- Time zones: a set of overlap hours for live collaboration, with written asynchronous updates outside them.
A Simple Team Norms Template
Copy this outline into your team’s shared document and fill in each line together:
- Our core hours are … and we do not expect replies outside them.
- We use … for quick questions, … for decisions and … for urgent issues.
- Meetings have an agenda shared by … and end with named actions.
- Decisions about … are made by …; we record them in ….
- When we disagree we …, and if we cannot resolve it we ….
- If someone forgets a norm, anyone can ….
- We will review these norms on ….
Keeping Norms Alive
The most common failure is agreeing norms in a workshop and never mentioning them again. A few habits prevent that. Managers should model the norms visibly, because teams copy what leaders do more than what they say; our article on leader vs manager explores that difference. Spend five minutes in a monthly retrospective asking which norm is working and which is being ignored. Update norms when projects, tools or team members change. And treat breaches as a chance to clarify, not to blame; a norm that is regularly broken may simply be the wrong norm.
Signs Your Team Needs to Reset Its Norms
- The same disagreement keeps coming back because nobody knows who has the final say.
- People are unsure whether a message needs an answer today or this week.
- Meetings overrun, and actions from the last one have been forgotten.
- New starters say it took months to understand “how things really work”.
- A few people do most of the talking while others stay silent, then raise concerns privately afterwards.
A Worked Example
A six-person marketing team kept missing deadlines because requests arrived by email, chat and in passing, with no single list. In a one-hour session they agreed three norms: all requests go on the shared board with a due date, the board is reviewed in a 15-minute Monday stand-up, and anything added after Wednesday lands in the following week unless the team lead agrees otherwise. None of these rules is complicated, but because everyone agreed them together, they stuck, and arguments about priorities moved from corridors into one short weekly conversation.
Common Mistakes to Avoid
- Imposing norms from the top. People follow rules they helped create far more readily.
- Being vague. “Communicate well” cannot be followed or checked.
- Too many norms. Keep the list short enough to remember.
- Ignoring quieter voices. Use written input or anonymous voting so everyone contributes.
- Conflicting with policy or the law. Norms cannot override employment contracts, flexible working arrangements or reasonable adjustments. In the UK, the right to request flexible working and duties under the Equality Act 2010 still apply, so check with HR if a norm might affect them.
Norms also connect to how you manage the work itself; our guide to product and service management covers the processes they sit alongside. For more on management and workplace topics, browse our Business section.
Frequently Asked Questions
What are examples of team norms?
Common examples are starting meetings on time with an agenda, replying to messages within one working day, giving every task one named owner and not expecting replies outside core hours. The best norms are specific enough that anyone can tell whether they are being followed.
What is the difference between team norms and team values?
Values are broad principles, such as respect or openness. Norms are specific, observable behaviours that put those values into practice day to day.
How many team norms should a team have?
Five to ten is a practical range. Fewer may miss important areas, while a long list is hard to remember and uphold.
Who should set team norms?
The whole team should agree them together, usually with the team lead or a neutral colleague facilitating. Norms imposed by a manager alone are less likely to stick.
How often should team norms be reviewed?
Review them after about three months, then at least once or twice a year, and whenever the team, its tools or its way of working changes significantly.
What should you do when someone breaks a team norm?
Start with a friendly, private reminder and assume good intent. If the same norm is broken repeatedly by several people, discuss it at a retrospective, because it may need rewording or replacing.
Final Thoughts on Team Norms
Team norms turn unspoken expectations into a short, shared agreement that everyone can see and improve. Book one 60 to 90 minute session, agree five to ten specific behaviours, write them down and put a review date in the diary. That small investment pays back quickly in calmer meetings, faster decisions and fewer avoidable disagreements.
