Every team has rules. Most of them were written the day after somebody broke one.
Someone forwards a message that was meant to stay in the room, and now there’s a confidentiality norm. Someone talks for eleven minutes, and now there’s a timekeeper. The rule arrives attached to a person, which makes it a verdict about that person rather than an agreement among equals — and everyone in the room knows exactly who it’s about.
Written before
An agreement
No incumbents · nobody's face attached · free to propose
Written after
A verdict
Attached to a person · everyone knows who · costly to propose
A group and team coaching intensive I took had us do it the other way round. Before the first real conversation, before anyone had annoyed anyone, the group filled in a partnership agreement and signed it.
What was on the page
The template is unremarkable to look at, which is part of why it works. Three sections — logistics, goals, working norms — then a signature line for the group leader and one for every member. Three structural mechanics inside it do the heavy lifting:
- A hard end date, defined before the goals are.
- A pre-scheduled mid-cycle check-in, with its own blank on the form.
- A designed exit path — if any of us decide to leave the group prior to the scheduled conclusion, we will appropriately notify the group and the program administrator.
§1 Before we get started
Start date · mid-cycle check-in · end date · frequency · format · who schedules
logistics
§2 What we're working toward
Group goals — specific, measurable, attainable, relevant, trackable
purpose
§3 How we plan to work together
Expectations · ground rules · contact outside meetings
conduct
Signatures
If any of us leaves early, we notify the group
exit
Each of those is quieter than it looks.
The end date is on the form before the goals are. The group agrees on when it stops before it agrees on what it’s for. That single field converts an open-ended commitment into a bounded one, which is the difference between people saying yes generously and people saying yes accurately.
The mid-cycle check-in has its own blank. Not “we’ll revisit this if it’s not working” — a date. Revision is scheduled at signup, so when someone eventually wants to change a rule, they aren’t raising a complaint. They’re keeping an appointment. The footer says it outright: don’t forget to refer to this agreement occasionally and update your expectations or ground rules.
Leaving is a designed path. The exit clause is right there next to the signatures. Groups that don’t write one still have members who leave; they just leave by fading, which everyone reads as a judgment on the group.
Why “while everyone still feels fine” is the load-bearing part
The obvious objection is that a group on day one has no idea what it will need. True. It also has no incumbents, no history, and nobody defending a position.
Ground rules written cold are cheap. Everybody agrees that people should be able to disagree, that the quiet ones should get airtime, that what’s said in the room stays in the room. Those are free opinions at that moment. Six weeks in, each one has a face attached and a cost to whoever proposes it.
I watched why this matters in the same course. During an icebreaker I made a light, offhand comment: family is also a group. Two participants went quiet and stayed quiet for the rest of the session. They told me afterward that was the moment — the phrase hit something personal that neither had agreed to navigate in a professional workshop. Days earlier I had been on the other side of it as a participant, ambushed by my own trigger word.
An agreement would not have prevented that. You cannot pre-clear the English language for eleven strangers’ histories. What an upfront agreement provides is not immunity from conflict; it gives the room a pre-authorised way for someone to say I need to step out of this one without having to explain or justify themselves in public at the worst possible moment. Without one, the only available move is silence — and silence gets read as disengagement.
That’s the case for writing rules early, and it is not really about rules. It’s about who pays the social cost of using them.
The four questions worth stealing
The course also gave a set of contracting prompts, which I now think are a better starting point than a blank “ground rules” box:
- What are we here to accomplish?
- What does success look like?
- What do we need to feel safe?
- What’s outside scope?
Q1
What are we here to accomplish?
Usually answered. Rarely written down.
Q2
What does success look like?
Turns a mood into a criterion.
Q3 · answered too fast
What do we need to feel safe?
Ask it concretely: what would make you stop talking?
Q4 · nobody asks
What's outside scope?
Unnamed scope gets drifted into around week three.
The third one is the one people answer too fast. “We need to feel safe” produces platitudes when asked in the abstract. It produces something usable when asked concretely: what would make you stop talking? Do you want to be interrupted or not? If someone disagrees with you, do you want them to do it in the meeting or after it?
The fourth one is the one nobody asks at all. A group that hasn’t named what’s out of scope will drift into it, usually somewhere around week three, and then have an awkward conversation about whether this is a working group or a support group.
The ethics material was blunt about why safety has to be asked about rather than assumed. Safety looks different across norms; expectations about hierarchy, conflict and feedback vary; informed consent means people know what they’re agreeing to and can opt out. A group that imports one culture’s version of directness and calls it a universal ground rule has just written a rule that some of its members cannot use.
The line I now add to any group agreement
One of my own notes from that weekend was: establish norms early, and allow additions and edits by group members. The second clause is the whole thing. A set of norms handed down by whoever convened the group is a policy. A set the group can amend is an agreement, and only the second kind survives contact with a real disagreement.
So the line I add, when I’m the one holding the pen:
Any of us can put a rule back on the table at any meeting, and the person who raises it doesn’t have to explain why.
Not amendable
A policy
Handed down by whoever convened the group. Survives until it's tested.
Amendable by any member
An agreement
Edits are an appointment, not a complaint. Survives a real disagreement.
And no justification required
That last clause matters. Requiring a justification means the only people who ever propose a change are the ones confident enough to argue for it in public — which is precisely the group that needed the rules least.
Check which of your team’s rules were written before the incident and which were written after. Rules written after are usually verdicts, and nobody likes following a verdict.
Comments