The short version
Meetings are culture's highest-frequency artifact. Audit what yours reveal, score them in twenty minutes, and reset them with seven concrete agreements and a four-week test.
If you want to know what an organization actually values, don't read its values page. Sit in three of its recurring meetings. Within an hour you'll know who has power, whether disagreement is survivable, whether decisions are real, and whether people's time is treated as a resource or an assumption.
Meetings are culture's highest-frequency artifact — the most honest one your culture produces, rehearsed in public every week. They're also the easiest thing to change: unlike compensation or org structure, a team can rewrite its meeting norms on a Tuesday. This guide brings together everything we've published on the subject into one process: what to watch, how to score it, which norms to change, and how to roll the changes out without a program.
Your calendar is a policy document. It just was not written on purpose.
Part 1: What a meeting reveals
1. Agendas reveal access to power
Who sets the agenda, and when does it circulate? An agenda sent by the most senior person five minutes before the meeting tells attendees their input is decoration. A shared agenda, open to additions a day early, with each item labeled inform, discuss, or decide, tells them the meeting belongs to the team. A meeting with no stated purpose says other people's attention is free; a meeting with a pre-read says preparation is expected of everyone, including the most senior person in the room.
2. Airtime reveals whose knowledge counts
Track the first three speakers in your next five meetings, and roughly who holds the talk time. When two people hold seventy percent of the talking in a room of eight, the other six are not disengaged — they have correctly inferred the rules. Don't aim for mechanically equal airtime. Ask whether the people closest to the work shape the diagnosis before senior voices frame the answer. If expertise consistently speaks after authority, the meeting is teaching hierarchy rather than judgment.
3. The first disagreement reveals the price of honesty
This is the single most diagnostic moment in any meeting. Watch the ten seconds after someone contradicts the apparent consensus. Do people build on it? Does someone reframe it as a misunderstanding? Does the leader's tone change? If the response is a question, dissent is affordable. If it is a defense — or a polite nod followed by no engagement — you'll get consensus in the room and litigation in the hallway afterward.
4. Decision rights reveal whether clarity is safe
Every recurring meeting should be classifiable: decide, inform, or generate. Most dysfunctional meetings are decision meetings pretending to be discussions, with no named decider — so the decision gets made afterward by whoever has the most access. Ask two attendees, one day later, what was decided. Two different answers is the most common and most expensive culture defect there is. Ambiguity is not an administrative gap; it's a power feature that lets the most senior person reinterpret the outcome later.
5. Follow-through reveals whether words carry weight
A commitment without an owner, a date, and a review point is not a commitment. It is a hopeful sentence. Look at the last commitment from the previous meeting: was it done, changed on purpose, or quietly dropped? A team that never revisits its own commitments is training itself that nothing said in meetings is load-bearing.
6. Invisible work and the freedom to leave
Who takes the notes, books the room, sends the follow-up? If it's consistently the same demographic, you have a documented pattern, not a coincidence — rotate it on a published schedule. And check whether anyone can decline or drop off. If attendance is a loyalty signal, your calendar is a status system, and your team's focused time is the currency being spent on it.
Part 2: The 20-minute meeting audit
Do this with your team, in one sitting, on your most important recurring meeting. Pull the agendas and notes from the last three to five sessions. You're describing, not fixing, so twenty minutes is enough. Score each statement 0 (rarely), 1 (sometimes) or 2 (consistently):
- 1Purpose: every agenda item makes clear whether the group must inform, discuss, or decide — and a new attendee could tell from the agenda what each item was for.
- 2Voice: at least three people who are not the leader substantially shape the discussion, and the people closest to the work speak before the most senior person closes the frame.
- 3Dissent: at least one competing view is invited and visibly explored, rather than parked, without interpersonal penalty.
- 4Decision: the decision-maker is named before discussion, and the record shows what was decided, who owns it, and when it will be revisited.
- 5Follow-through: every action has one owner and a date, and each prior commitment can be traced to completion or an honest revision.
Eight to ten: the meeting reinforces healthy norms. Five to seven: one or two dimensions need redesign. Below five: the meeting is rehearsing a culture you probably don't intend — and it is the fastest culture lever you own.
Running it across several meetings
- Minutes 0–5: list your four recurring meetings and write each one's purpose in one sentence. Cross out any you cannot state without hedging.
- Minutes 5–10: for each, name who spoke most and who spoke least last time. No commentary yet.
- Minutes 10–14: recall the last disagreement in each. Was it resolved, deferred, or quietly dropped?
- Minutes 14–18: find the last three decisions. Can anyone point to where they're written down and who owns them?
- Minutes 18–20: pick one norm to change this week — one, with an owner and a review date.
Part 3: From etiquette to observable behavior
Most teams try to fix meetings with etiquette — "be respectful," "come prepared," "stay on topic." Etiquette fails because it is unobservable and therefore unenforceable. Replace each vague norm with a behavior anyone can see and verify:
- "Be respectful" becomes: critique ideas, not people — and the facilitator names it when the line is crossed, regardless of who crossed it.
- "Decisions get made" becomes: every item is labeled, and decide items name the decision-maker in the first two minutes.
- "Everyone's heard" becomes: the first pass on any major question goes round the room before open discussion.
- "We disagree well" becomes: the facilitator asks one person by name to make the strongest case against the leading option — and thanks the hard part of what they said.
- "Meetings end on time" becomes: the last three minutes are a fixed closeout — decisions, owners, dates, read back aloud.
A team's real norms are not what it says about itself. They are what it does in the third minute of a disagreement.
Part 4: Seven agreements for the reset
A useful norm changes behavior at a recognizable moment. These seven are deliberately concrete. Adapt them, don't adopt them — cut what doesn't fit, and add the rule your team argues about hardest.
1. Every item has a job
Label each item inform, explore, recommend, or decide, with the desired output and the person leading it. The meeting type goes in the invite title. If an item has no job, it doesn't belong on the agenda; if the meeting only informs, ask whether a document would work better — and default to the document. No agenda, no meeting: anyone can cancel it without penalty.
2. The pre-read replaces the update
State what attendees must read or bring and how long it should take, and send it at least a working day ahead. Open with five minutes of silent reading so nobody is punished into bluffing. The discussion then starts at the disagreement rather than at the summary — and most of the hour was the summary. If materials arrive late, the owner chooses whether to postpone or use the time for questions instead of pretending everyone prepared.
3. Expertise speaks before authority
On any question where they want real input, the most senior person speaks last and says so out loud: "I have a view; I'll hold it until the end." Hear first from the people closest to the work. This protects independent judgment without turning hierarchy into a taboo.
4. Disagreement names evidence and risk
Disagreement is expected. Anyone challenging a proposal states the evidence they see, the risk they infer, and what would change their view. Whoever raises the first objection gets a follow-up question, not a rebuttal — "what would have to be true for you to be right?" At moments of tension, the facilitator asks, "What are we not saying because it may be inconvenient?" and waits long enough for an answer.
5. Decision rights are named before debate
Write the decision-maker's name at the top of the agenda, next to the decision, along with who recommends and who contributes. Participation does not imply veto power, and saying so is a kindness — it tells people whether they're being consulted or overruled. The decider explains the choice after hearing input, especially when choosing against the majority. Anyone, including guests, can ask "what are we deciding here?" at any point.
6. Silence is checked, not interpreted
Before closing a consequential item, ask for objections, missing perspectives, and dependencies. Silence may mean agreement, uncertainty, deference, or fatigue; the meeting doesn't pretend to know which. Rotating facilitation helps here — when running the room is a skill rather than a rank, the facilitator can pull in quiet voices and stop settled points being re-litigated.
7. Commitments leave with an owner and a date
Close by reading back decisions and actions, and give anyone thirty seconds to correct the record. Within 24 hours, post a written decision record — what was decided, why, who's affected, who owns the next step, when it will be revisited — where affected non-attendees can read it. "The team" is not an owner. Begin the next meeting by reviewing that record.
A decision that exists only in the memory of the people who attended is not a decision. It is a rumor with momentum.
Part 5: The four-week test
Don't launch the norms across the organization. Pick one recurring meeting — ideally the one people complain about most — and add one change per week:
- 1Week 1: spend fifteen minutes drafting the agreements together (don't hand them down), post them in the invite description, and add the pre-read with five minutes of silent reading.
- 2Week 2: add item labels and the named decision-maker to each decide item. Assign one person, publicly, to call violations for the month.
- 3Week 3: hand facilitation to someone who has never run it, and cut the scheduled time by a third.
- 4Week 4: add the fixed three-minute closeout, then re-run the audit. Keep, rewrite, or remove each agreement on evidence — and decide whether the meeting still needs to recur at all.
Delete anything that's being ignored: an unenforced rule teaches people that rules here are decorative. If the team spends more time administering an agreement than benefiting from it, simplify it. Review every recurring meeting each quarter, with cancellation as a legitimate outcome.
How to tell whether it worked
- Decision latency: how long between an item appearing and a decision being made.
- Airtime spread: whether the same two people still hold most of the talking.
- Rework: how often a settled question comes back a second time.
- Opt-in: whether people would still attend if attendance were optional.
- Audit score: whether the 0–10 score moved after four sessions.
Only then offer the agreements to a second team. Adoption spreads faster from a team that visibly runs better than from an all-hands announcement. And none of it requires permission from above.
The point isn't process discipline for its own sake. Every rule above redistributes a small amount of power — from seniority to argument, from access to documentation, from the loudest voice to the clearest one. Do that consistently for a quarter and you will have rewritten the most frequently rehearsed script your culture has.
Related resource
Team Norms Template
A one-page template for writing down how your team meets, decides, and disagrees — then reviewing it every quarter.
Get the Team Norms Template