Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / Why Your Community Needs a Member Spotlight Program
Transcript
- Lucas: So I've been digging into something a lot of community managers talk about but rarely execute well — the member spotlight program. And I found a case that actually has numbers attached, which is rare. Luna: I feel like every Slack group I'm in has tried some version of 'member of the month' and it either feels forced or dies after two cycles. Lucas: Exactly. That's the pattern. But there's a 400-person Discord for indie SaaS founders — they call it 'Build in Public HQ' — that started a weekly 'Community MVP' spotlight back in January. And the results are pretty concrete. Over six months, active participation — meaning someone posts at least once a week — went up 34 percent. And peer to peer support threads increased by 28 percent. Luna: Wait, those are big jumps. What were they doing differently from the typical 'shout out the loudest person' approach? Lucas: That's the key. They designed it to avoid exactly that pitfall. First, the spotlight criteria are not based on post count or reaction scores. Instead, they spotlight someone who gave unusually helpful feedback in a thread, or who onboarded a new member, or who shared a resource that helped multiple people. The community manager picks from a private log she keeps — she doesn't announce the criteria publicly. Luna: So it's not a competition. You can't game it because you don't know what will earn the spotlight. Lucas: Right. And the second thing is that the spotlight comes with a tangible benefit — early access to the group's weekly newsletter or a beta slot for a member's product. But here's the detail that I think makes the biggest difference: the spotlight is delivered by the previous week's MVP, not by the community manager. Luna: Oh, that's smart. It becomes a peer to peer recognition loop instead of a top-down pat on the head. Lucas: Exactly. And it creates this subtle pressure on the person receiving it to pay it forward the next week. They're not just getting a badge — they're now the person who gets to pass the torch. The community manager told me that within four weeks, they had a chain of people who were actively looking for ways to help others because they wanted to be the one to give the next spotlight. Luna: That's a beautiful mechanic. But I have to ask — does this risk creating an in-group of spotlight receivers? Like, do the same people keep getting it? Lucas: She shared the data. In 26 weeks, 22 different people received the spotlight. Only two people got it twice, and they skipped at least eight weeks between. The criteria deliberately rotate — one week it might be about onboarding, the next about technical help, the next about sharing a failure story. That variety pulls in different kinds of contributors. Luna: So it's not just rewarding the extroverts who write long posts. It rewards the person who quietly DMs a new member a useful template. Lucas: Exactly. And that's the group's biggest insight — they started seeing lurkers emerge. People who had been silent for months sent a message saying, 'I don't normally post but I saw so-and-so help someone in that thread and it made me want to contribute too.' The spotlight became a model for the kind of behavior they wanted. Luna: I love that. It's almost like the spotlight isn't really about the person being recognized — it's about showing everyone else what's possible. Lucas: That's a great way to put it. And it's worth mentioning that they did one more thing that I think is crucial — they never spotlight the community manager or any moderator. The spotlight is exclusively for regular members. That keeps it from feeling like a staff award. Luna: Have you seen other communities try similar things and fail? What's the common mistake? Lucas: The biggest one is making the spotlight too predictable — like 'top contributor by message count.' That just rewards people who are already loud. Then the quiet helpful people never get recognized and eventually feel invisible. Another common mistake is tying the spotlight to a prize that's too big, like a $500 gift card. That turns it into a competition and kills the collaborative vibe. Luna: Makes sense. So the prize should be meaningful but not so valuable that people start gaming the system. Lucas: Right. In this case, the early access to the newsletter is a small thing — the newsletter goes out to everyone anyway a day later. But the perceived value is high because it signals status. And the beta slots are free for the giver, so it costs the community nothing. Luna: I want to try this in a couple of the Slack groups I manage. But I'm worried about the time commitment — how long does it take the community manager each week? Lucas: She said about 15 minutes. She keeps a running document where she jots down a potential candidate whenever she sees something worth flagging. Then on Friday she picks one, writes a two-paragraph blurb, and sends it to the previous MVP to post. That's it. Luna: Fifteen minutes a week for a 34 percent engagement bump. That's a no-brainer. Lucas: And think about the ripple effect. Those 22 people who got spotlighted are now more invested in the community. They're more likely to recruit friends, more likely to defend the community norms, more likely to stick around when they hit a rough patch with their own product. Luna: So it's not just a vanity metric. It's building a core of loyal members who feel seen. Lucas: Exactly. And that's the kind of thing that compounds. If you run this for a year, you've created 52 moments where someone felt genuinely appreciated by their peers. That's a community culture you can't buy. Luna: You know, this reminds me of why we keep this show ad-free. A couple of dollars a month from listeners is what keeps these conversations going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Lucas: Yeah, it really does make a difference. And it lets us keep digging into specific tactics like this without any sponsor pressure. Luna: So back to the spotlight — one thing I'm wondering: how do you handle it if someone declines the spotlight? Like, what if they're introverted and don't want the attention? Lucas: The community manager said that's happened twice. In both cases, she simply said 'no problem' and gave the spotlight to someone else that week. But she also asked if they'd be open to a private thank-you instead — a direct message from her. Both said yes. So you can still acknowledge them in a way that feels comfortable. Luna: That's a good backup. And it respects the person's boundaries. I think a lot of community programs force recognition on people who don't want it. Lucas: Exactly. The rule should be: the spotlight is an offer, not a summons. And if someone says no, you don't make a big deal about it — just move on. Luna: So what about the long-term sustainability? Does the effect wear off after six months? Lucas: She shared month-by-month data, and actually the engagement rate kept climbing — slowly — through month six. But she's planning to introduce a small twist at month nine: a 'community choice' spotlight where members can nominate someone with a one-sentence reason. That adds a new layer of engagement. Luna: I like that. It gives the community a voice without turning it into a popularity contest because it's just one additional slot alongside the manager's pick. Lucas: Right. And she's careful to only add that after the norm is established. If you start with member nominations, the loudest people win. But if you build a culture of manager-curated recognition first, then when you open nominations, people have a model for what kind of behavior deserves the spotlight. Luna: That's a smart sequencing. So for anyone listening who wants to start this, what's the first step? Lucas: Start a private log. Today. Just a simple doc where you note one person each day who did something helpful. You don't need to announce the program yet. Collect data for two weeks. Then you'll have a backlog of genuine candidates, and you can launch with real examples from day one. Luna: That's doable. And it means you're not scrambling for a spotlight recipient in week one. Lucas: Exactly. Then decide your criteria — which should map to the behaviors you want to encourage. If you want more new member onboarding, spotlight people who welcome new members. If you want more technical depth, spotlight people who answer tough questions. The spotlight is a signal about what the community values. Luna: And keep the prize small and social — early access, a shout-out, a custom role. Nothing with a dollar value that could be gamed. Lucas: Right. And then just commit to doing it every single week for three months. The consistency matters more than the production value. A simple post from a peer with a genuine reason will outperform a slick graphic that feels corporate. Luna: I think that's the core insight: the spotlight works because it's authentic and peer-driven. The moment it becomes a corporate program, it loses its magic. Lucas: Exactly. And if you can keep that human element, you're not just rewarding individuals — you're building a community where people want to be generous because they've seen it modeled and they know it will be seen. Luna: I'm going to try this in my design community. I'll let you know how it goes in a few months. Lucas: Please do. I'd love to hear what twists you add. And if anyone else tries it, feel free to reach out — we might do a follow-up episode with your results. Luna: Alright, I think that's a solid plan for this week. Next time, let's talk about something I've been noticing — communities that use data dashboards to track member health, but in a way that feels creepy versus helpful. Lucas: That's a good one. There's a fine line between knowing your members and surveilling them. Let's figure out where that line is.