Knowledge Base entry

How should you handle controversial topics that split your mod team?

A practical answer page built from the knowledge base source.

Internal disagreement within a mod team is healthy when it involves genuine deliberation and unhealthy when it results in paralysis, factionalism, or unpredictable inconsistency that members can see and exploit. How a mod team structures its decision-making for controversial cases determines whether disagreement becomes a constructive resource or a corrosive problem. The first principle is that controversial decisions should not be made unilaterally. When a moderation question splits the team, any single moderator acting alone — enforcing their interpretation regardless of the team's lack of consensus — undermines the team's collective authority and creates precedents that other mods then feel pressure to follow or reverse. Holding the decision until consensus or a structured resolution process is reached is better for the community even when it creates a short-term delay. For persistent disagreements that cannot be resolved through discussion, a vote with majority or supermajority threshold is a practical resolution mechanism. The terms of this process — what vote threshold is required, whether the head moderator or founder has a tie-breaking vote, how the decision will be communicated to the community — should be established before a crisis, not in the middle of one. Many experienced mod teams document their decision-making procedures in a private moderators-only wiki page so that these questions have clear answers when they arise. When the disagreement is not about a specific case but about the community's direction — which topics are within scope, how strictly rules should be enforced, whether the community should change its purpose — a broader community input process may be appropriate. Posting a discussion thread asking members for their views on a specific policy question both distributes the decision-making burden and gives the mod team social license to implement whichever direction the community endorses. This approach works best for rule changes rather than specific user actions.