Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How Brand Communities Turn Conflict into Trust
Transcript
- Lucas: You know that moment in a brand community when one member posts something that sets everyone off? Maybe it's a complaint that feels unfair, or a suggestion that rubs people the wrong way. I've seen community managers freeze — delete the thread, ban the user, hope it blows over. Luna: And that usually makes it worse, right? Because now you've got a bunch of people who want to discuss it, and you've silenced the conversation. Lucas: Exactly. So let's talk about a case where a community manager did the opposite. In mid-2025, the project management tool Basecamp had a user in their online community post a pretty harsh critique of a new feature — basically said the team didn't understand how people actually work. It got heated. Other users piled on. Some defended the company. Luna: That's a powder keg. What did they do — delete the whole thread? Lucas: No, and that's what makes this interesting. The community manager, a woman named Jess, left the thread up. She posted a public reply saying: 'We hear you. We're going to take a day to process this, then we'll come back with a specific response.' She locked the thread temporarily — not deleted — and within 24 hours she posted a detailed note acknowledging the concerns, outlining what they'd change about the feature rollout, and then opened a new thread inviting the community to help shape the revised version. Luna: So she used the conflict as a kind of research prompt. That's smart — it turns a negative into co-creation. Lucas: Right. The immediate effect was that the original critic became one of the most constructive contributors in that follow-up thread. The longer-term effect: Basecamp saw a 15% increase in active participants over the next quarter. Not because the product got better — though it did — but because the community saw that speaking up didn't get you banned. It got you heard. Luna: I think a lot of brands are terrified of that kind of transparency. They worry it'll invite more negativity. But what Jess did was essentially show the community that conflict can be productive. Lucas: And that framework — I'd call it pause, reframe, invite — is the reason it worked. Pause: she stopped the conversation from spiraling without killing it. Reframe: she acknowledged the criticism as valuable input, not an attack. Invite: she brought the community into the solution. Luna: And if these marketing conversations have sparked something you've actually used in your own work — maybe something we said helped you handle a tough comment or rethink a community policy — a couple of dollars a month is genuinely what keeps these going. You can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a small gesture that makes a big difference for us. We don't run ads, so listener support is what keeps the show ad-free and focused on stories like this one. Luna: Alright, back to the Basecamp story. So what about communities that don't have a dedicated community manager? If you're running a Slack group of 200 customers, you can't always afford someone to monitor every thread. Lucas: Great point. The pause step is still doable. You don't need a full-time moderator; you need a rule. In Basecamp's case, the rule was: before you delete anything, set a timer. Give yourself a few hours, or a day, to respond. That alone prevents the knee-jerk deletion that erodes trust. Luna: And for the reframe step, you can use a template. Something like: 'We see your concern. Here's what we're thinking. What did we miss?' That's low-effort but high-impact. Lucas: Exactly. Smaller communities might also want to appoint a couple of trusted members as 'community guides' — not moderators with ban powers, but people who can help steer conversations back on track when things get tense. Basecamp actually did that too after this incident. They created a 'Council of Contributors' — a rotating group of active users who could give feedback on moderation decisions. Luna: That's interesting because it distributes the responsibility. It also signals that the community is collectively responsible for its norms, not just the company. Lucas: Right. And that council ended up writing a new section of the community guidelines that specifically addressed how to disagree constructively. They called it 'The Art of the Strong Opinion, Gently Held.' The guidelines explicitly said: 'Assume good intent, state your case with data, and be open to being wrong.' Luna: I love that. It's a proactive declaration, not a reactive rule. It sets the expectation before conflict arises. Lucas: And it worked. In the six months after the council was formed, the number of flagged posts dropped by 40%, and the average thread length — which is a proxy for engagement — went up. People were having longer, more thoughtful conversations because they felt safe. Luna: So the takeaway isn't just 'don't delete the angry comment.' It's about creating a system where that comment becomes a catalyst for strengthening the community. Lucas: Exactly. So next time you see a heated debate in your community, resist the urge to clean it up. Ask yourself: is this a threat, or is this a raw source of data? If you treat it as the latter, you might just turn a critic into your most loyal member.