Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / The Overlooked Skill That Makes Brand Communities Fail
Transcript
- Lucas: There's this stat I keep coming back to — something like 80 percent of brand communities never get past fifty active members. And the reason is almost never that the topic isn't interesting. Luna: So what kills them? Lack of budget? Wrong platform? Lucas: Neither. It's a missing skill in the person running it. Most community managers are hired for their ability to moderate — keep things civil, approve posts, maybe post a weekly question. But the skill that actually makes a community work is something else entirely. Luna: What's that? Lucas: The ability to design what I'd call a participation loop. A sequence where a new member takes one tiny action, gets immediate value from that action, and is then nudged toward a slightly bigger action. Without that loop, a community is just a chat room with tumbleweeds. Luna: Give me a concrete example of a loop that works. Lucas: Let's use a B2B SaaS company I've been watching — they make project management software for product managers. They launched a Slack community last year targeting product managers at mid-size tech companies. Standard playbook: invite list, welcome channel, a few icebreaker questions. And it flopped. Luna: How many members did they get before it stalled? Lucas: About 200 signups in the first month, but fewer than 15 people ever posted. The rest lurked and then ghosted. The problem was that the ask on day one was too high — 'introduce yourself and tell us about your biggest product challenge' — and the reward was invisible. No one replied to most intros, so members felt like they shouted into the void. Luna: Right, the social reward didn't happen fast enough. Lucas: Exactly. So they rebooted it. This time, every new member was placed into a small cohort of about ten people based on their company's revenue range. The first action wasn't an intro post — it was a one-click poll: 'Which feature do you ship most often? A. Dashboard, B. Notifications, C. Integrations.' Once you answer, you immediately see how your answer compares to others in your cohort. Luna: Oh, that's smart. The poll gives instant social proof and a tiny dopamine hit. Lucas: And it costs almost zero effort. Then, after the poll, the system prompts: 'Reply to someone whose answer surprised you.' That's step two. And because the cohort is small, responses are almost guaranteed — the community manager makes sure at least two people reply to every new member within 24 hours. Luna: So you're engineering the reward, not hoping it happens naturally. Lucas: That's the skill. Most community managers think their job is to set up a space and let the magic happen. The ones who succeed treat the community like a product feature — they define the user journey from first click to habitual contributor. Luna: What happened after the reboot? Did it take off? Lucas: Within 90 days they hit 350 active members — defined as anyone who posted or replied at least once in the past week. And their churn rate among members who completed the poll plus reply sequence was under 5 percent. Compare that to the first launch where almost nobody stuck around. Luna: That's a huge swing. So the secret isn't the topic or the platform — it's the sequence of actions you design. Lucas: Exactly. And there's one metric that predicts whether a community will survive its first 90 days better than anything else. It's the percentage of new members who complete what I call the 'first-value action' within 48 hours of joining. Luna: Define first-value action. Lucas: It's the smallest possible action that gives the member something useful back — a poll result, a personalized recommendation, a direct reply from someone knowledgeable. In the Slack group, that was the poll. In a different community I've seen, it was a 'roast my landing page' thread where you post your page and get three specific critiques within an hour. Luna: So the action has to be useful in itself, not just a signal that you're present. Lucas: Right. If the first action is 'tell us about yourself' with no guaranteed return, you've already lost most people. The best communities hide that intro step behind the value step. You get something first, then you're invited to introduce yourself. Luna: This reminds me of how Duolingo does it — the first lesson is so easy you feel like you've already made progress before you even commit to the app. Lucas: Exactly the same principle. And I think the reason so many brand communities fail is that companies hire community managers based on their communication skills or their network, not their ability to design these loops. It's a design problem, not a content problem. Luna: So if someone is starting a community tomorrow, what's the one thing they should focus on? Lucas: Map the first three actions a new member takes. For each action, ask: what do they get back immediately? If the answer is 'nothing for at least 24 hours,' redesign the action. And the first action should take less than ten seconds. Luna: Ten seconds. That's a tight constraint. Lucas: It forces you to be honest about whether you're actually providing value or just asking for attention. Most community onboarding flows are a series of asks with no immediate reward. Flip that around and suddenly the retention numbers change dramatically. Luna: I've seen that in practice with a small Discord for freelance designers. They had a channel called 'feedback first' where you could post a design and get feedback within an hour. New members were encouraged to post there before introducing themselves. It worked because the feedback was useful even if nobody replied to your intro. Lucas: That's a perfect example. The feedback channel is the value engine. The intro channel is just social glue. Most communities get the order backwards. Luna: And the community manager in that case wasn't a designer — they just set up the system and recruited a few power users to guarantee fast replies. Lucas: Which brings up another point — the community manager doesn't have to be the expert. They have to be the architect of participation. They design the loop and make sure it's staffed, either by themselves or by recruited members. Luna: That's a very different job description from what most companies post. Lucas: It really is. Most job listings ask for 'experience with Slack or Discord' and 'excellent written communication.' Those are table stakes. The real differentiator is systems thinking — can you design a behavior cycle that scales? Luna: So if I'm a marketer listening and I want to audit my own community, what's the quickest way to check if the loop is broken? Lucas: Look at the first five messages a new member sees. If more than two of them are from the community manager making announcements or asking questions, your loop is broken. Ideally, the first messages a new member sees should be from other members responding to something the new member contributed. Luna: Okay, that's a clean diagnostic. Lucas: And if you're the one making all the announcements, you haven't designed a participation loop — you've designed a broadcast channel that you're calling a community. Luna: Yeah, and the listener can feel that difference immediately. Lucas: Honestly, if today's episode sparked an idea you might actually use in your own community — or if it saved you from launching a Slack group that would have died at 15 members — that's exactly the kind of thing that makes producing this show worth it. If that resonates, there's a link where you can buy me a coffee — buy me a coffee dot com slash fexingo. It's the smallest gesture, but it's what keeps these conversations ad-free and focused on what actually works. Luna: Yeah, it's a nice way to say 'this was useful' without a big commitment. Lucas: Exactly. And back to the design piece — I think the next frontier for brand communities is applying this loop thinking to retention, not just onboarding. Once someone has joined and posted once, how do you keep them coming back without annoying them? That's where most communities plateau. Luna: What's the retention version of the ten-second action? Lucas: A weekly 'two things' thread — share two things you learned or two things you're stuck on. It's low effort, it surfaces useful content, and it gives lurkers a reason to check in. You don't need to comment — just reading the thread is valuable. That's a loop that sustains itself.