Rules lose authority when people can see they are never updated or applied. Every building has one: the laundry room sign limiting residents to two machines, dated years ago, ignored by everyone including the person who taped it up. The sign is not neutral. Each day it hangs there unenforced, it teaches residents that posted rules in this building are suggestions, and that lesson transfers to the rules that actually matter.
We tend to talk about rules as if writing them were the whole job. Draft the policy, ratify it, post it, done. But a rule is closer to a shared appliance than to a monument. It gets used daily, it wears, it drifts out of alignment with reality, and it needs someone checking on it. This piece is about why that maintenance has to be shared, and what the evidence says happens when it is.
How a rule actually works
A rule does its work through expectation, not enforcement. When the parking arrangement on a block functions, it is because each driver expects the others to honor it and expects violations to get noticed. Enforcement events are rare; the anticipation of them is constant. This is what makes rules cheap compared to guards and cameras, and it is also what makes them fragile. The expectation only survives while people keep seeing evidence that the rule is alive: a violation corrected, an outdated clause revised, an exception explained, the same visibility that makes queues feel fair.
Once that evidence stops, decay is quick and quiet. The first unpunished violation is information. The fifth is a new norm. Nobody voted to kill the rule, but it is dead, and the written version becomes a small monument to the moment people stopped tending it.
The economist who counted working commons
The strongest evidence about what keeps shared rules alive comes from Elinor Ostrom, who spent decades studying communities that manage common resources: fisheries, pastures, forests, irrigation systems. Standard theory said these commons should collapse, since each user has an incentive to take too much. Ostrom went and looked. Across hundreds of documented cases, from Swiss mountain pastures to Spanish irrigation canals to Maine lobster fisheries, she found communities sustaining shared resources for generations, and in 2009 that fieldwork earned her the Nobel Memorial Prize in Economic Sciences, the first ever awarded to a woman.
Her book Governing the Commons, published in 1990, distilled what the durable arrangements had in common into a set of design principles. Two of them matter most for this essay, because both are forms of maintenance, and in the successful cases both were done by the community itself rather than outsourced.
Watchers who answer to their neighbors
The first principle is monitoring, done by the resource users or by people accountable to them. The Spanish irrigation communities Ostrom studied elected their own canal inspectors from among the farmers. This sounds like a detail and is actually the load-bearing wall. A distant enforcer checks the rule occasionally and misses the context; a neighbor sees daily whether water is being taken out of turn, and knows when a violation was desperation rather than greed. Just as important, monitoring by peers keeps the rule's legitimacy circulating. When your fellow farmer verifies compliance, the rule stays yours. When only an external authority checks, the rule becomes theirs, something to evade rather than uphold.
The everyday translation: a rule with no assigned watcher is already half abandoned. If a group cannot name who notices violations of its policy, the honest description is that nobody does.
Small penalties, applied early
The second principle is graduated sanctions. In the communities that lasted, a first violation drew something mild: a quiet word, a token fine, a public noting. Repeat offenses escalated. This pattern beats the dramatic alternative on every axis. Because the first sanction is small, monitors actually impose it instead of looking away, so violations get addressed while they are still cheap. Because escalation is predictable, nobody can claim surprise. And because minor lapses are treated as lapses rather than crimes, a farmer who bent the rules in a drought year can be sanctioned lightly and remain a member in good standing instead of becoming an enemy of the system.
Contrast the workplace or condo board that ignores a rule for two years and then makes a shocking example of one unlucky violator. That style produces the worst of both worlds: long decay punctuated by punishments everyone reads as arbitrary. Review the rule after it fails, not years later, while the failure is still small enough to discuss without a villain; here as everywhere, trust is built in the follow-up.
What shared maintenance looks like in practice
For any rule your group actually depends on, the upkeep reduces to a short cycle that must rotate among members rather than falling forever on one founder.
- Name the current watcher, out loud, with an end date to the shift.
- Log violations and responses, even one line each, so patterns are visible instead of anecdotal.
- Schedule a standing review, and let usage evidence drive revisions.
- Retire what you will not enforce. A pruned rulebook is stronger than a padded one.
The rotation is not just fairness. It is how the group keeps collective ownership of the rule, which is the thing the rule runs on.
Give one rule a birthday
Choose a single rule you share with others: the chore split, the group chat's self-promotion policy, the visitor parking arrangement. Give it an annual review date and put it on the calendar this week. At the review, ask three questions. Did anyone watch it this year? What happened when it was broken? Would we write it the same way today? Shared rules need shared maintenance, and a birthday is the smallest unit of maintenance a group can commit to without forming a committee.