Norms for meetings: write the rules, then make them stick

Most teams treat meeting norms like a poster: write a few inspirational lines about respect and punctuality, pin them to a wiki, and never look at them again. That does nothing. A norm only changes behavior when the team helped write it, it names a specific behavior (not a value), and somebody is willing to enforce it in the room. Everything else is decoration.

So this guide is not a list of nice rules to copy. It is a method for producing norms your team will actually follow, plus a copy-pasteable starter set you can adapt in one session. The short version: co-create them, make each one observable, agree how you will call them out, and revisit them on a schedule. Skip any of those four and you are back to the poster.

Why this is worth a meeting of its own

The cost of meetings that run on autopilot is large and measured. The London School of Economics surveyed more than 3,400 professionals globally in 2024 and found that 35% of business meetings are unproductive, at an estimated annual cost of $259 billion in the US. The same study found that a handful of inclusion behaviors (valuing all contributions, drawing on everyone's insights to avoid groupthink, and staying open to new ideas) could cut the unproductive rate from 35% to 15%. Those are not vibes. They are norms you can name and adopt.

There is also a deeper reason norms work. Google's Project Aristotle studied 180 of its teams between 2012 and 2014 and found the top driver of team effectiveness was not talent or seniority but psychological safety: the shared belief that the team is safe for interpersonal risk-taking. The effective teams shared one observable meeting habit, what the researchers called "equality in distribution of conversational turn-taking," meaning everyone got roughly the same airtime over the course of a meeting. Google's own guidance tells leaders to "define the team behaviors and norms you want to foster." Norms are how you manufacture, on purpose, the conditions that the best teams stumbled into.

Norms vs ground rules vs values: get the language straight

These terms get used interchangeably and it causes confusion, so pin them down before you write anything.

• Values are what you care about: respect, candor, focus. They are real but unenforceable. You cannot catch someone "being disrespectful" in a way two people will agree on.
• Norms (also called ground rules, team agreements, or a social contract) are the specific behaviors that express those values. They are observable. You can tell when one is followed and when it is broken.
• Agenda and logistics are per-meeting decisions (who runs it, how long, what gets covered). Norms sit above those and apply across every meeting of a given type.

Your job is to translate values into norms. Take "we value focus" and turn it into "laptops closed unless you are presenting or note-taking." Take "we value preparation" and turn it into "no agenda, no meeting; the organizer posts one 24 hours ahead or it gets canceled." Now you have something you can hold each other to.

How to set norms that stick: the five-step method

Norms fail when a manager writes them alone and announces them. They stick when the team builds them, because people enforce rules they helped make and ignore rules handed down. Here is the sequence.

A starter set of meeting norms you can adapt today

Do not adopt this list wholesale. Use it as raw material in step two above, keep what fits your failure modes, and rewrite the rest in your team's words. Each one is written to be observable on purpose.

MEETING NORMS: [Team name], adopted [date], next review [date]

PREP
1. No agenda, no meeting. The organizer posts an agenda with a
   stated outcome 24 hours ahead, or the meeting is canceled.
2. Pre-reads go out 24 hours ahead. We read before, not during.
   Meeting time is for discussion and decisions.

IN THE ROOM
3. Start and end on time. We start at :02 (a 2-minute grace
   window) and we stop at the scheduled end, even mid-sentence.
4. Cameras and intent, not multitasking. Laptops closed unless
   you are presenting or taking notes for the group.
5. Make space, take space. If you have talked a lot, hold back.
   If you have been quiet, the facilitator will invite you in.
6. Decisions get an owner and a date, out loud, before we move on.
   "We should" is not a decision.
7. Disagree in the room, not in the hallway. Objections raised
   after the meeting do not count.

AFTER
8. Notes and action items are shared within 24 hours, with an
   owner and due date on every action.
9. If a recurring meeting has no agenda two times running,
   we cancel the series and reassess whether it should exist.

ENFORCEMENT
- Anyone can call a norm. Default phrase: "Norm check, can we
  come back to [parking lot]?"
- The facilitator owns airtime balance (norm 5) and the clock.
- We review and edit this list every [6-8 weeks].

The point of writing them this plainly is that you can settle a disagreement by pointing at the line. "We agreed pre-reads go out 24 hours ahead" ends an argument that "you should have been more prepared" never will.

Make the notes norm automatic, because that's the one that quietly fails

Norms 6 and 8 (decisions get an owner, and notes go out within 24 hours) are the ones that decay first, because they depend on a human remembering to capture decisions in real time while also running the meeting. That rarely survives a busy week. The fix is to take note-taking off the critical path so the norm holds itself up.

For meetings on Google Meet, Scribbl records, transcribes, and summarizes from your browser with no bot joining the call, so the transcript and an AI summary with action items exist by the time the meeting ends. That makes "notes within 24 hours, with an owner on every action" a default rather than a chore someone has to volunteer for. (Teams on Zoom or Teams can do the same; see Scribbl for Teams.) If you would rather build the muscle by hand first, our guide to taking better meeting notes and a reusable action items template will get you there.

Two cautions. First, a recording norm is itself a norm: agree out loud that meetings are recorded, say why, and let people opt a sensitive conversation out. Surprise recording erodes the psychological safety the rest of your norms are trying to build. Second, the tool captures the words; the discipline of turning a decision into an owner-plus-date is still on the facilitator. A transcript of a meeting that decided nothing is just a long document.

Common ways norms fail (and how to avoid them)

• Too many. A list of 20 rules is unmemorable, so the team remembers none. Cap it at 5-8 and cut ruthlessly at review.
• Values disguised as norms. "Be respectful" and "communicate openly" feel good and change nothing because you cannot observe them. Rewrite every line until you could referee it.
• Imposed from the top. A manager-authored list gets nodded at and ignored. The team has to build it. Your role as the leader is to model the norms hardest, because the team watches whether you follow your own rules.
• Set once, never revisited. Teams change, problems change. Norms that are not reviewed become folklore. Put the review on the calendar.
• No teeth. Covered above and worth repeating: an unenforced norm teaches the team that rules are optional. Decide the enforcement mechanism in the room.

Frequently asked questions

How many meeting norms should we have?

Five to eight. Few enough that people remember them without looking, specific enough that each one targets a real failure mode you named. If your list is longer, you are mixing in values (cut them) or duplicating (merge them). You can always add at the next review; starting lean beats starting with a wall of rules nobody reads.

Who should set the meeting norms, the manager or the team?

The team, facilitated by the manager. Norms handed down from a leader get compliance at best and quiet eye-rolling at worst, because people enforce rules they helped write and ignore rules imposed on them. The manager's real job is to run the co-creation session, model the norms most visibly, and be the first to accept a "norm check" when they break one.

What's the difference between meeting norms and a meeting agenda?

An agenda is per-meeting: what this specific meeting will cover, in what order, for how long. Norms are cross-meeting: how the team behaves in every meeting of a given type, regardless of topic. They work together. A strong norm ("no agenda, no meeting") forces the agenda to exist; a strong agenda gives the norms something concrete to operate on. For building the agenda side, see our meeting preparation checklist and meeting management best practices.

How do we enforce norms without making meetings feel like a courtroom?

Make the call-out small, shared, and low-drama. Agree on a single neutral phrase ("norm check") that anyone can say without it being an accusation, and have the facilitator own the two norms that need a neutral referee (airtime balance and the clock). The goal is a quick redirect, not a tribunal. When the leader is the first person to accept a norm check graciously, it stops feeling like policing and starts feeling like the team holding a standard it chose.

Do remote and hybrid teams need different norms?

They need extra ones, not different ones. Distributed teams add failure modes: people talking over each other on video, the in-room group dominating the remote callers, side chats in DMs. Add norms that target those specifically (one conversation at a time, remote people called on first in hybrid rooms, decisions confirmed in writing because nodding does not carry over video). Our guide to managing remote teams goes deeper on the hybrid case.

The bottom line

Meeting norms are not a culture deck. They are a short, blunt, team-written list of observable behaviors, with an agreed way to call out the ones that get broken and a date to revisit them. Build them with the people they govern, keep them few and specific, give them teeth, and automate the parts (notes, action items) that humans reliably forget. Do that and you are deliberately engineering the airtime balance and follow-through that the most effective teams only ever stumbled into.