Every team has norms. Most of them were never chosen.

The team that meets for two hours when the problem could have been solved in a Slack message. That is a norm. The team where only the most senior person in the room actually speaks. That is a norm too. The leadership team that has the real conversation in the hallway after the meeting ends. You guessed it.

Unwritten norms do not disappear when you hire good people. They fill the vacuum left by a lack of explicit agreement. And by the time you notice them, they are usually the reason you are losing good people or watching your best ideas die in a meeting that ran out of oxygen.

A team norms workshop is the antidote. Not because norms on a sticky note are magic, but because the conversation about how your team will work together is where psychological safety begins to take shape. This post gives you a full agenda, a set of facilitation tools, and a process that creates norms people actually follow.

‍

What Are Team Norms (And Why Most Teams Get Them Wrong)

Team norms are the agreed behaviours that define how a group works together. How decisions get made. How conflict gets handled. How feedback flows. How meetings run. They are the operating system underneath the org chart, and they sit at the foundation of the Six Levels of High-Performing Teams.

The mistake most managers make is confusing team norms with team values. Values are aspirational. Norms are behavioural. "We communicate openly" is a value. "We share project blockers in the weekly Slack thread by EOD Thursday so nobody gets ambushed in the Friday review" is a norm.

Effective norms have five qualities.

They are specific. Not "we communicate well." Instead: "We respond to direct messages within one business day during working hours."

They are behavioural. A norm describes an action someone can do or not do, not a feeling they should have. Behaviours are observable. Feelings are not.

They are observable. If you cannot tell from the outside whether the norm was followed, it is not a norm. It is a wish.

They are co-created. Norms imposed from the top get tolerated. Norms built by the team get owned. There is no shortcut around this.

They are few enough to remember. Eight to twelve, not forty. If nobody on the team can name them, nobody is following them.

Google's Project Aristotle research, which studied 180 teams over two years, found that the single biggest predictor of team performance was psychological safety. As Harvard professor Amy Edmondson puts it, psychological safety is a shared belief that the team is safe for interpersonal risk-taking. The belief that you will not be embarrassed, rejected, or punished for speaking up.

Team norms are the mechanism through which psychological safety gets built or quietly destroyed. Every norm is a signal. This is what we reward here. This is what we punish.

‍

When to Run a Team Norms Workshop

Not every team needs a formal workshop. But you probably do if any of these are true.

You are a new manager taking over an existing team, and the unwritten rules are not yours. The team has grown by more than 25% in the last year, and the people who joined later are operating from different assumptions than the people who were here first. You have just merged two teams or restructured, and two cultures are colliding inside one room. Conflict keeps surfacing about the same issues. Meeting length. Response times. Who gets the final call. People keep telling you "this is just how we do things here," and nobody can explain when "we" decided. Or you can feel the parking-lot conversations happening, but they never make it back into the room.

Don't wait for a crisis. The teams that run norms workshops proactively are the ones that avoid the kind of dysfunction that requires an emergency intervention.

‍

The Pre-Work (One Week Before)

A workshop is only as good as the thinking that goes into it. Send these questions to participants one week before the session, and give them about 20 minutes to answer.

What is one thing about how this team works that you think is genuinely great, and that you would protect at all costs?

What is one habit, ritual, or pattern on this team that you secretly wish would change?

When you have a tough idea to share, a piece of feedback, or a half-formed concern, do you bring it to the team or do you sit on it? Be honest. Why?

If you could change one thing about how meetings, decisions, or feedback happen here, what would it be?

What is one behaviour you have seen on a previous team that you would love to import here?

Don't make these mandatory. Make clear that the better people engage with the pre-work, the better the workshop will be. You will use these responses to surface patterns and themes before you walk in the room.

Also send a brief explanation of what team norms are and why you are running this session. People who understand the why bring better energy to the how.

‍

The Full Team Norms Workshop Agenda (2.5 Hours)

This agenda works for teams of 5 to 20 people, in person or remote. For remote sessions, use a virtual whiteboard such as Miro or FigJam. For in-person, large sticky notes and wall space work well.

‍

Part 1: Open the Container (20 minutes)

Purpose: create the psychological conditions for honest conversation.

Start with a quick check-in. Go around the room, or break out into pairs for remote: what is one word that describes how you are showing up today?

This is not a fluffy icebreaker. Daniel Coyle's The Culture Code argues that groups who share brief personal disclosures before working together surface more ideas, take more risks, and produce higher-quality outcomes. The check-in is the first belonging cue of the session.

Then set the frame. Say something close to this, in your own words.

"Every team has norms. Some we chose. Most we inherited. Today is about deciding which ones we want, on purpose."

"We are not here to fix individuals. We are here to design the conditions that let this team do its best work."

"By the end of the next two hours, we will have a written set of behavioural agreements that everyone in this room helped build."

"Anything raised today is fair game. Nothing said in this room becomes a performance issue afterwards."

Acknowledge the awkwardness if it's there. "I know this can feel a bit formal for something that should happen naturally. That is actually why we are doing it explicitly. The norms that happen naturally are usually the ones nobody chose."

‍

Part 2: Surface the Norms You Already Have (30 minutes)

Purpose: name the unwritten rules so you can decide which to keep and which to change.

Give everyone five minutes to write answers to two prompts on sticky notes, one idea per note.

Prompt 1. On this team, what gets you rewarded? What behaviours, when someone does them, get praised, promoted, given more responsibility, or talked about positively when the person is not in the room?

Prompt 2. On this team, what gets you punished? What behaviours, when someone does them, get pushed aside, ignored, criticized in private, talked about negatively, or quietly held against people?

Use sticky notes for a reason. Individual brainstorming first. Everyone writes their own ideas before anyone speaks. You do not want to filter ideas through whoever is loudest in the room.

Once everyone has written, put all the notes on the wall. Cluster them by theme as a group. Read them out. Look for patterns.

This is the most revealing part of the workshop. Across teams we've facilitated, the "punished for" notes consistently surface things people have not said out loud before. Punished for admitting uncertainty. Punished for challenging the plan in public. Punished for bringing a half-formed idea. Punished for being the one who slows the meeting down with the question everyone else also had.

These are not failures of character. They are failures of norms. And naming them is the first step to replacing them.

‍

Part 3: Define the Norms You Want (40 minutes)

Purpose: co-create explicit behavioural agreements across four dimensions.

Break the team into small groups of 3 to 5 people and assign each group one of these four dimensions.

Each group has 10 minutes to draft 3 to 5 behavioural norms for their dimension. Prompt: "Complete this sentence. On our team, we agree to..."

Then share back. Each group presents, the full team reacts, modifies, and builds on. Focus the discussion on behaviours, not values, and push for specificity. "We agree to give feedback directly" is fine. "We agree to use the SBI model (Situation, Behaviour, Impact) when giving critical feedback, and to do it in private first unless the situation is urgent" is better.

‍

Part 4: Vote, Prioritize, and Commit (25 minutes)

Purpose: land on 8 to 12 norms the whole team will actually adopt.

Give each person five dots (physical or virtual) to vote on the norms they think are most important. The top vote-getters become the core operating norms. Discard or defer the rest. Too many norms are as bad as none.

For each selected norm, ask the full team: "Can everyone commit to this?" If someone cannot, that is worth knowing now. Dig into it. Sometimes it surfaces a legitimate objection that improves the norm. Sometimes it reveals an underlying tension that needs a more direct conversation.

Write the final norms on a single document that everyone can access.

‍

Part 5: Build in Accountability (15 minutes)

Purpose: turn agreements into action.

Norms die without accountability mechanisms. Before you close, decide five things together.

Where the norms live. A shared doc. The team channel header. The back of every meeting agenda. Pick a home that the team actually sees more than once a quarter.

When you revisit them. A 30-minute review at the start of every quarter is the lightest cadence that actually works. The question becomes: is this norm still serving us, or has it stopped?

How new hires get them. Every new team member reads the norms in their first week and brings questions to their second 1:1. Onboard people into the norms, not just the work.

What happens when someone violates a norm. Not punishment. Permission to call it out kindly and directly in the moment. "Hey, we agreed we would not do that. Can we try again?" If you cannot call it out, the norm is decorative.

Who goes first. Almost always: the leader. The norm is dead the first time the manager visibly breaks it.

The fourth decision is the most powerful. Teams that give themselves permission to call out violations kindly and directly in the moment are the teams where norms actually change behaviour.

‍

Close: Reflection and Appreciation (10 minutes)

End with two rounds.

Round 1, Reflection. One word or short sentence from each person: what is one thing you are taking away from this conversation? Keep it tight. No long speeches. Everyone goes.

Round 2, Appreciation. Each person names one other person in the room and one specific thing they appreciated about how that person showed up today. Be concrete. "I appreciated how Sara pushed back on the meeting norm even though it was uncomfortable" lands harder than "I appreciated everyone being so open."

Recognition is a norm reinforcement tool. It signals what the team values, and it ends the session on a note of psychological safety rather than fatigue.

‍

What to Do After the Workshop

The workshop is one day. The hard work is the 90 days after. Writing norms is the easy part. Living them is where most teams quietly let it die.

Here is what actually makes them stick.

Week 1. Visibility. Pin the norms somewhere the team sees every day. The top of your team channel. The first slide of your weekly meeting. The header of every shared agenda doc. Out of sight is out of mind, and out of mind is back to the unwritten rules you just spent two and a half hours surfacing.

Weeks 2 to 4. The leader goes first. Whatever norms the team set, the manager models them first and loudest. If the norm is "we surface blockers in stand-up, not after missing a deadline," the manager surfaces theirs first. Pick the norm that is hardest for you personally to follow, and follow it on purpose so everyone sees you doing it. Culture is what you reward day-to-day minus what you tolerate day-to-day. As the manager, you set both.

The 30-day check-in. Run a 20-minute team conversation. Which norms are showing up in our day-to-day? Which feel theoretical? Where have we drifted? Sometimes a norm sounds great in the workshop and turns out to be the wrong norm in practice. Edit it. Norms are not sacred. They are tools.

Live calling-out. Build the muscle of catching norm violations in the moment, in the room, kindly. "Hey, we agreed we would not interrupt during stand-up. Let's let Priya finish her thought." The first time this happens it will feel awkward. By the third time it will start to feel like culture. By the tenth it will be the culture. If the team only ever talks about norms in the abstract and never in the moment, they are not norms. They are a wishlist.

The 90-day review. Schedule a 30-minute team meeting at the 90-day mark. Three questions. Which norms are working? Which need to be edited? Is there a norm we missed that we now know we need? Then ship the updated list and pin it again.

The point of team norms is not perfection. It is self-awareness. A team that has explicit agreements and misses them occasionally is infinitely healthier than a team that has no agreements and is confused about why things feel off.

Want to know where your team's psychological safety stands before you run the workshop? Take our free Team Dynamics Assessment, a diagnostic that benchmarks your team across safety, communication, conflict, and performance. If you would rather run this conversation with help, we facilitate team norms sessions for scaling teams. Book a strategy session.

‍

Frequently Asked Questions: