A team should not have to renegotiate itself every day.

01The monthly debate

You’ve had this argument before. Probably last month.

Someone ships a change on a Friday. Someone else asks whether that’s allowed. Nobody is sure, so the thread fills with what people remember: a rule from an old team, a preference from a former manager, an incident from two years ago that half the room never saw.

The thread ends with a vague agreement and no written line. Four weeks later the same question returns with different people in it, and the team spends its energy renegotiating itself instead of doing the work. New colleagues learn the rules by breaking them.

A written guideline gives the question a standing answer. It says what the team may do, under what conditions, and why. The next person to ask gets a link instead of a debate.

02The distinction

A norm lives in memory. A guideline lives where people can point to it.

A norm is something most people believe the team does. A guideline is the version someone wrote down, with a reason and an owner, that the team agreed to keep. Norms drift quietly as people come and go. Guidelines change on purpose, through a proposed change everyone can see.

03Three principles

Write down the answers people keep asking for.

1. 1

   Write it as something you can do.

   “Be careful with releases” gives nobody a decision. “Releases ship Monday to Thursday; Friday needs the on-call go-ahead” does. Phrase each guideline as an action a new colleague could take tomorrow, with the condition that changes it. If you can’t tell whether someone followed it, it isn’t finished.

2. 2

   Keep the reason next to the rule.

   Guidelines without reasons turn into folklore. When the reason sits beside the line, people can tell a sensible exception from a careless one, and the team can retire a guideline once its reason is gone. The reason for “Release days” is the on-call rota. Change the rota, and the guideline is up for review.

3. 3

   Change it in the open.

   When practice moves, propose a change instead of quietly ignoring the line. The current and proposed text sit side by side, the people the guideline affects weigh in, and the old version steps back into history. The team keeps one current answer and a record of how it got there.

04In Particulars

Guidelines the team can read, cite and change.

Each guideline lives on the team’s charter as a short rule with its explanation, and every change becomes a new version with who made it and a readable diff. When Particulars reads the channels you choose and finds a rule the team keeps following, it can propose it as a guideline. The team decides whether to adopt it.

Illustrative team. The guideline is what was agreed; the history shows how it changed.

05What becomes possible

Spend the monthly debate on something new.

Once guidelines are written and kept current, the questions that used to return every month get a link. New people act with confidence in their first week. And exceptions become signal: when one line keeps bending, you can see it, and decide whether to change the rule or the practice.

• Answer “can we just do this?” with a link, not a meeting.
• See where practice keeps drifting from a line.
• Retire the lines whose reasons are gone.

“A team should change its mind on purpose, not by forgetting.”

The Particulars thesis