Why Written Dialogue Rules Beat Assumed Norms

Have you ever sat in a meeting, a family dinner, or a comment thread where everyone seemed to be playing by a different rulebook, and nobody could say whose rulebook was correct? I have. And for a long time I assumed the problem was the people. It usually isn't. It's that the group never wrote anything down.

Most groups run on assumed norms: a loose, unspoken sense of how disagreement should go, who gets to interrupt, what counts as an attack versus a challenge. Assumed norms feel natural because they're invisible. Nobody has to sit through a policy meeting to establish them. They just accumulate, the way a trail forms in a field because enough people walked the same way.

The trouble is that a trail only works if everyone is actually walking the same path. In my experience running dialogue spaces, the moment a group grows past a dozen or so regular participants, or the moment a real disagreement lands, the trail turns out to have been three or four different trails all along, and everyone is furious that the others aren't staying on "the" path.

This is the case for written dialogue rules over assumed norms: not because writing things down is more official or more impressive, but because it's the only way to find out, before the disagreement happens, whether the group actually agrees on what fair conversation looks like.

What We Actually Mean by "Assumed Norms"

An assumed norm is any standard for behavior that a group relies on without ever stating it. "We don't talk over each other here." "We assume good faith." "We keep things respectful." These sound like rules. They function more like vibes, because nobody has defined the words doing the load-bearing work. What counts as talking over someone? Is a firm rebuttal disrespectful, or is disrespect only tone, only insult, only repetition?

Social psychologists have a name for a related phenomenon: pluralistic ignorance, the situation where most members of a group privately reject a norm but assume, incorrectly, that everyone else endorses it. The research goes back decades, most famously in studies of college drinking norms, where students overestimated how comfortable their peers actually were with heavy drinking. The same mechanism shows up in dialogue spaces. People assume the room has agreed on a standard for civility that, when you actually ask around, turns out to be six different private standards wearing the same word.

I think this is the real argument for writing rules down. It isn't about control. It's about finding out, honestly, whether the group agrees before you need the agreement to hold weight.

Why Groups Default to Unwritten Norms Anyway

Nobody sits down and decides "let's leave this ambiguous." Unwritten norms are the default because writing things down feels formal, and formality feels cold. A new community wants warmth. It wants to feel like friends talking, not like a courtroom. So the founders skip the document, and for a while it works, because the founding group actually does share a private culture. They grew up in similar rooms, read similar books, learned dialogue from the same handful of mentors.

The unwritten norm works exactly as long as the group stays homogeneous and small. Add new voices, and the shared culture that made the informality possible is gone, but the informality remains, now unmoored from the thing that used to hold it up. What was once "we all just know" quietly becomes "the founders know, and everyone else is expected to guess."

What Written Rules Actually Do

A written rule does something an assumed norm structurally cannot: it separates the standard from the person enforcing it. When a norm is unwritten, every act of enforcement is also an act of interpretation, delivered by whichever person happens to be moderating that day. That person becomes the norm, personally, in that moment. Disagree with the call, and you're not disagreeing with a rule. You're disagreeing with a person, and the conversation about the disagreement becomes a conversation about that person's judgment, their tone, their history in the group, everything except the actual question of what happened.

A written rule redirects that energy. When the rule exists on a page, the moderator can point to it rather than own it. "Here's the guideline we agreed on, here's how this applies" reads completely differently than "I've decided this crossed a line." The first is a shared reference. The second is a personal verdict, and personal verdicts breed resentment even when they're correct.

I've also come to think written rules do something for the participants who never break them. They tell a quiet majority what's actually expected, instead of leaving them to infer it from watching who gets corrected and who doesn't. Inference is a slow, error-prone way to learn a culture, and it teaches the wrong lesson as often as the right one: that the rule is "don't get caught" rather than "here's the standard."

Where Written Rules Go Wrong

Written rules aren't magic, and a rulebook nobody reads is just as useless as no rulebook at all. I've seen groups write exhaustive codes of conduct that function as legal cover rather than lived practice, dense enough that new members skim past them and old members only cite them as weapons. A written rule that's too long, too legalistic, or too rarely revisited becomes its own kind of assumed norm: everyone assumes it says something reasonable, because nobody has actually read it recently.

The fix isn't to abandon the written rule. It's to keep it short enough to read in five minutes, concrete enough to apply without a debate about definitions, and alive enough that the group revisits it when it stops fitting the conversations actually happening. A rule that never gets amended is a rule the group has stopped taking seriously.

Written Rules vs. Assumed Norms, Side by Side

The pattern running through every row is the same. Assumed norms are cheap until the group needs them, and written rules are cheap after the group needs them. Most groups are optimizing for the wrong side of that trade.

What the Research Suggests

I'm cautious about overselling numbers in a space this human, but a few data points are worth sitting with.

CPP Inc.'s widely cited Global Human Capital Report found that employees spend an average of 2.8 hours a week dealing with conflict, much of it conflict that traces back to unclear expectations rather than genuine disagreement over substance. That's not a small tax. Across a year, it's more than a full work week spent untangling misunderstandings that a shared, written standard could have prevented from becoming personal in the first place.

Robert's Rules of Order, first published in 1876, exists for exactly this reason: General Henry Robert wrote it after watching a public meeting descend into chaos because the room had no shared, explicit procedure for handling disagreement, only assumptions that turned out not to be shared at all. A century and a half later, that same gap between assumed and written procedure is still the reason most online communities and civic meetings struggle.

The Nielsen Norman Group's well-known 90-9-1 rule for online communities found that roughly 90 percent of participants in a typical group lurk without posting, 9 percent edit or comment occasionally, and only 1 percent create most of the content. That imbalance matters here because it means the vast majority of a community's members are silently forming their sense of "how we talk here" from what they observe, not from anything anyone ever told them directly. If the visible behavior is inconsistent because the norms were never written down, the silent 90 percent absorb that inconsistency as the actual culture.

Research on pluralistic ignorance, going back to work by Deborah Prentice and Dale Miller in the early 1990s, found that group members routinely misjudge how their peers actually feel about a shared norm, often overestimating consensus that doesn't exist. Ambiguity doesn't just make disagreement more likely. It hides the disagreement until it's already a crisis.

A rule people can point to changes what a conflict is about. Instead of litigating who someone is, the room gets to litigate what happened, and that's a conversation people can actually resolve.

How to Write Rules That Hold

I don't think a good set of dialogue rules needs to be long. In my view, the ones that actually get used share a few traits. They name the behavior, not the character. "Respond to the argument, not the person" is usable. "Be respectful" is not, because respect is defined differently by everyone reading it. They're written in plain language a new member can understand on first read, without a glossary of community-specific jargon. And they include something rarer: a stated process for what happens when the rule itself seems wrong, so the rule can evolve without the whole group having to relitigate its legitimacy every time someone questions it.

I've noticed the groups that do this well tend to treat the rules as a living document rather than a founding scripture. They date their revisions. They explain, briefly, why a rule changed. That transparency does something assumed norms can never do: it lets a newcomer see the group's reasoning, not just its current conclusion.

The Deeper Reason This Matters

Underneath the practical case, I think there's something almost dignifying about writing the rules down. An assumed norm treats the group's culture as something you either already know or have to earn through trial and error, which quietly sorts people into insiders and outsiders before the conversation even starts. A written rule treats every reader as someone capable of understanding the standard the moment they arrive. It's a small act of respect, offered before anyone has done anything to earn or lose it.

That's the real difference between the two approaches. Assumed norms ask people to prove they belong. Written rules tell people, up front, exactly what belonging requires.

I don't think this closes the question of how a group should write its rules, how short is too short, how often to revise, who gets to propose a change. Those are worth sitting with, and different groups will land in different places depending on what they're actually trying to build together. But the first choice, whether to write anything down at all, isn't really a stylistic one. It's the choice between a culture people have to guess at and one they can actually read.

If you're building a space for civil dialogue, I'd rather you start there than anywhere else.

Frequently Asked Questions

What's the difference between a written dialogue rule and an assumed norm? A written rule is stated explicitly and exists independent of any one person's memory or mood. An assumed norm lives only in what group members individually believe is expected, which research on pluralistic ignorance shows is often inconsistent from person to person even within the same group.

Don't written rules make a community feel formal or unwelcoming? They can, if they're written like legal contracts. Short, plain-language rules that name specific behaviors rather than abstract virtues tend to feel more welcoming than unwritten norms, because they tell a newcomer exactly what's expected instead of leaving them to guess and risk a public correction.

How often should a group revise its dialogue rules? There's no fixed schedule, but a rule that hasn't been revisited in over a year, or one nobody can explain the reasoning behind, is usually a sign the group has stopped treating it as a living standard. Dating revisions and briefly noting why something changed keeps the rule credible.

Can a small group with a strong shared culture skip written rules? For a while, yes. Small, homogeneous groups often share enough implicit culture that unwritten norms hold up fine. The risk is growth: the moment new members join who didn't absorb that original culture, the group is enforcing standards nobody ever actually told them about.

What's the biggest mistake groups make with written rules? Writing them once and never applying them consistently. A rule that exists on a page but isn't referenced during actual disagreements becomes just as invisible as an assumed norm, and the group loses the main benefit: a shared reference point everyone can point to instead of personal judgment calls.

Last updated: 2026-08-01