Talk Before You Enforce

Let the group talk before anyone builds a fence.

Thread:
Institutions
Level:
collective-choice, in the governance column
File:
wiki/patterns/talk-before-you-enforce.md

draft

no piece explains this yet: write one?

Talk Before You Enforce Sketch from above: five mannequins stand in a ring around a round rug, which is hatched, with small arcs of speech coming from them toward its middle. Away to the front right, a fence panel lies flat on the ground, unused. The people are the group sharing a system, from the pattern's context, with problems to deal with. The rug is the solution, the focus: a place set aside for the group to talk, such as a chat channel or a regular check-in. The speech arcs are a problem being raised there first, in front of everyone, instead of decided by an admin alone. The fence panel is technical enforcement, such as quotas, permissions, and bans: set aside, not built, and still there if the group chooses to use it later. The metaphor: a meeting ground everyone stands around as equals, where talking comes before fencing anyone in.
Fig. 3

Let the group talk before anyone builds a fence.

Context

A group sharing a system has started to have problems: someone uses too much storage, someone installs something without asking, rules are unclear.

Problem

The admin’s instinct is to reach for technical enforcement: quotas, permissions, bans. These are quick, but they put the admin in charge of discipline and skip the group’s own judgment. Members experience the rules as imposed from above.

Forces

  • Technical enforcement is fast and needs no meeting. Talking takes time.
  • In experiments, letting people talk sharply increased cooperation, even with no enforcement. Sanctions worked best when combined with communication and chosen by the group (Covenants With and Without a Sword).
  • Lasting institutions use graduated sanctions and low-cost conflict resolution (Governing the Commons).

Solution

Therefore, set up a place for the group to talk, and raise each problem there before building any enforcement tool.

Actions

  • A chat channel or a regular check-in.
  • If enforcement is needed, let the group choose it, and start with the smallest response that works.
  • The admin carries out the group’s decision instead of imposing their own.

Consequences

  • Positive: rules feel like the group’s own, and many problems are settled without sanctions.
  • Negative: responses are slower, and someone has to host the conversation. Urgent problems such as a security incident may need an admin to act first and explain afterwards.

Mark up this page on GitHub