The group admin's craft: two hundred members, zero chaos

Every community group starts the same way: a simcha, a class, a street — twenty members, one purpose, pure usefulness. Then it grows. By eighty members the first off-topic wave arrives; by a hundred and fifty, the group holds three arguments a month and the founding admin is privately wondering whether the whole thing was a mistake. It was not a mistake. It was under-administered — because nobody told the volunteer admin that a two-hundred-member group is an institution, and institutions run on craft.

The founding documents: scope and rules

The single highest-leverage act in a group's life happens at creation — or at the reset every mature group eventually runs:

• A one-sentence scope, in the group description. "Announcements and questions for Class 5B" — that sentence is the admin's entire authority. Every future moderation act is just pointing at it. Groups without a written scope are governed by whoever argues longest.
• Three rules, not thirty. The communities converge on the same trio: stay on scope, no forwarded-without-verification content, machlokes goes private. More rules than fit in a pinned message will not be read; three, everyone can recite.
• The class decision. Is this an announcement channel (admins post, members read) or a discussion group (everyone posts, scope governs)? Half of group chaos is a channel that never chose — the same channel-class discipline that runs the kehilla's whole announcement architecture, applied one group at a time.

“A group without a written scope is not a community — it is an argument waiting for its topic.”

kolbo.life

The weekly craft

Posting discipline is modeled, not enforced. The admin who posts on-scope, at reasonable hours, in text rather than five-minute voice notes, trains two hundred people by example. The pinned message carries the rules; the admin's own behavior carries the culture — the group-scale version of the community's texting etiquette.

The gentle redirect is ninety percent of moderation. "Great question — that one's for the private chat / the other group / the office" resolves nearly everything. The craft points: redirect in-channel once (so the norm is public), then privately thereafter; never scold in front of two hundred people — the public rebuke costs more than the off-topic post did.

De-escalation has a protocol. When the argument ignites (and it will — parking, tuition, politics erev elections): first, the admin's calm one-liner invoking scope; second, direct private messages to the principals; third — the mature group's secret weapon — the pause, an hour of admin-only mode announced plainly ("taking a breather, back at 9"). Machlokes starves without an audience; the pause removes the audience without removing anyone's dignity.

The join-and-leave etiquette runs on respect. New members get added with their consent (the courtesy the account-exposure realities make obvious); the departing get to leave without commentary; the removed — rare, for persistent scope-breaking after private warnings — get removed quietly, with a private explanation. Admin dignity is doing all of it as if the whole kehilla were watching, because it is.

The admin's own survival

The volunteer who runs three groups needs the role to be sustainable: share the keys (two admins minimum — coverage for Yom Tov, and the psychological difference between "my burden" and "our rota"); office hours for the inbox (the admin who answers group-management questions at all hours has volunteered for a second job; batch it); and the annual reset — every long-lived group deserves a yearly re-statement of scope and a membership prune of the departed and the double-added. Ten minutes of Elul housekeeping buys a year of order.

Frequently asked questions