Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Brand Community Vetted Its Own Moderation Rules
Transcript
- Lucas: So Luna, we've talked a lot on this show about communities giving members a voice in product decisions, pricing, even branding. But there's one area where most brands still keep a tight grip, and that's the rules themselves. Today I want to look at what happens when a community writes its own moderation guidelines. Luna: Oh, that's a bold one. Most community managers I know treat the rules as non-negotiable. Who actually handed over that pen? Lucas: A mid-sized fitness app called SweatPact. They've got about forty thousand members in their official community, and earlier this year they decided to let the community rewrite the moderation guidelines from scratch. The whole process took about six weeks, and the result was a thirty percent drop in reported incidents and a noticeable bump in trust scores on their quarterly member survey. Luna: Six weeks is fast for something like that. How did they avoid it turning into a free-for-all? Lucas: Well, they had a pretty structured process. It started with what they called a transparency audit. They published the existing rules, along with the actual enforcement data — how many warnings, bans, and removals happened in the previous quarter, and for what reasons. So the discussion started from facts, not vibes. Luna: That's smart. Most communities would be terrified to share that kind of data, but it sets a different tone entirely. Lucas: Exactly. It told members, we're not hiding anything, and we genuinely want your input. Then they opened two weeks of structured feedback threads, one for each rule. Each thread had a prompt like, 'The current rule on promotional content results in X warnings per week. Is this the right threshold?' And members could comment and upvote each other's suggestions. Luna: So not just a blank page asking for ideas. They gave them something concrete to react to. Lucas: Right. And that's what kept it focused. They got over two thousand comments, but because it was all organized by rule, the community team could actually synthesize it. They grouped the feedback into themes: clarity, fairness, and enforcement flexibility. Luna: Did they run into the classic problem of a few very loud voices dominating? Lucas: They did, and that's where the next step came in. After the feedback period, they drafted a new set of rules based on the most upvoted and most frequently mentioned suggestions. Then they put that draft to a vote for all active members — not just the loud ones. They used a simple agree, disagree, or suggest changes system, and each rule had to clear seventy percent approval. Luna: Seventy percent is a high bar. Did any rules fail? Lucas: Two of them did, actually. One was about memes, and one was about off-topic conversation in the general channel. The community was split, and the draft didn't make it. So they went back, revised those two based on the 'suggest changes' comments, and ran them through a second, shorter vote. Both passed on the second round. Luna: That's a good example of the process iterating, not just being a one-shot yes or no. Lucas: Absolutely. And there's a crucial detail: the community team kept a veto for safety-related rules. Anything that touched on harassment, hate speech, or doxxing couldn't be changed by a simple majority. They were explicit about that from the start, and that built trust rather than resentment. Luna: That seems like the right line to draw. You don't want the community voting on whether hate speech is okay. Lucas: Right, and they were transparent about it. The veto wasn't a secret. It was written into the process, and the community team explained why it was there. And I think that actually made the final rules stronger, because members knew there was a safety floor underneath the democratic process. Luna: So after the votes, what did the final rules actually look like? Were they radically different from the originals? Lucas: Not radically, but meaningfully. The core principles stayed the same, but the language got a lot more specific. For example, the original rule on self-promotion said 'no spam' — which was vague and led to inconsistent enforcement. The new rule defined what counts as spam, like more than one link per week, and gave examples of acceptable sharing, like sharing your workout log but not your coaching service. Luna: Specific language makes enforcement easier and also makes members feel the rule is fair, because they can see exactly what's expected. Lucas: Exactly. And they also added something that didn't exist before: a clear appeals process. If a member got a warning or a ban, they could request a review by a different moderator within seventy-two hours. That was one of the most requested changes, and it had a big impact on trust. Luna: Did that create a lot more work for the moderation team? Lucas: It did, at first. The first month, appeals were about thirty percent of all moderation actions. But the team treated it as part of the rollout, and by month two, the appeal rate dropped to ten percent — because the rules were clearer, so fewer enforcement decisions felt unfair in the first place. Luna: So the appeals process was almost a feedback loop that made the rules better over time. Lucas: Precisely. And that's the deeper point. The goal wasn't just to write better rules, it was to create a system where rules could keep evolving. They built in a quarterly review process where members can suggest amendments, and any amendment that gets a certain amount of community support goes to a vote. So it's not a one-time thing. Luna: That's a big commitment for a brand. Most companies would worry about losing control over the narrative. Lucas: And that's a valid fear. But SweatPact found that the opposite happened. They actually got more control, because the rules became something members felt ownership over. People were more likely to self-moderate, to remind others of the rules, and to report genuine violations rather than petty stuff. Their moderation team actually reported feeling less stretched after the rollout. Luna: Interesting. So handing over the pen gave them more authority, not less. Lucas: Right. And the numbers back it up. Reported incidents went down by thirty percent, but more importantly, the nature of reports changed. They got fewer 'this person is annoying' reports and more 'this person is breaking the rule on harassment' reports. The community started using the rules as their own yardstick. Luna: That's the kind of shift every community manager dreams of. But I'm curious — was there any pushback from long-time members who thought the old rules were fine? Lucas: There was some. A few members who had been around since the early days felt that the process was overkill, that the original rules were just fine. But the community team made a point of spotlighting those voices in the feedback threads, and a lot of them changed their minds when they saw the data on inconsistent enforcement. Luna: So showing the data kind of preempted the 'if it ain't broke' argument. Lucas: Yeah, it's hard to argue that a rule is fine when you see that it resulted in a hundred warnings for some members and none for others, for the same behavior. The audit made the inconsistency visible, and that was the real catalyst for change. Luna: I love that you're framing it as a learning moment, because honestly, a lot of communities would just say, 'we'll take your input into account' and then do what they want anyway. Lucas: Sure, and that's the trap. But SweatPact was intentional about not doing that. They published a full summary of the feedback, what they changed, and what they didn't change and why. That transparency was a big part of why the final rules were accepted so well. Luna: So what would you say is the single most important takeaway for a brand community manager listening to this? Lucas: I think it's that the process is as important as the outcome. The rules themselves are better, sure, but the fact that members were involved in writing them created a sense of shared ownership that changed the entire culture of the community. And that's something you can't get from a top-down policy update. Luna: That's a big idea, and it makes me think about how many communities are sitting on a goldmine of member wisdom that they never tap into because they're afraid to ask. Lucas: And on that note — you know, if these conversations have sparked something you've actually used in your own work, that's the thing that keeps us going. If today's episode was worth a coffee to you, there's a link on our show page, it's buy me a coffee dot com slash fexingo. No pressure, just know it keeps this podcast ad-free and independent. Luna: Yeah, honestly, even a small gesture like that lets us know these episodes are landing somewhere real. Now, back to the question of who should actually try this — is a community-led rule rewrite right for every brand community? Lucas: Great question. I'd say you need at least a few things in place. First, a minimum level of active membership — maybe a few hundred regulars who actually care. Second, a moderation team that's comfortable with transparency and open to change. And third, a willingness to give up some control, even if it's just on the non-safety rules. If those aren't there, the process could backfire. Luna: Where do you see this going next? Do you think more communities will adopt this model? Lucas: I think so, especially as platforms make it easier to run structured votes and surveys in-community. The desire for authenticity and democratic participation isn't going away. But the key is to do it thoughtfully, like SweatPact did. This isn't about handing over the keys to the asylum, it's about building a shared sense of responsibility. Luna: Shared responsibility — that's a great note to end on. Thanks for digging into this one, Lucas. Lucas: Thanks, Luna. If you're thinking about trying this in your own community, I'd love to hear how it goes. Maybe we'll have you on the show.