Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Small Community Drove a Product Name Change
Transcript
- Lucas: So, Luna, when was the last time a brand community actually changed a product decision? Not just tweaked a feature, but genuinely steered the ship? Luna: Honestly, most of the time it feels like the community is just there to validate what the company already decided. But there are exceptions. Lucas: And that's what I want to dig into today. There's a case from earlier this year that I've been chewing on: a small B2B SaaS company, maybe three hundred active members in their community, managed to get a product name changed. Not a minor feature, the actual name of the product. Luna: Okay, that's a big deal. How did that even happen? Lucas: So, the company was launching a new analytics tool, and they'd internally named it 'Pulse.' Generic, right? But the community had been calling it 'Signal' in their conversations for months, because the beta was codenamed Signal. When the company announced Pulse, the reaction was immediate. Luna: So the community felt a sense of ownership over the name because they'd been using it organically? Lucas: Exactly. And the company didn't just dismiss it. They had a community manager who was really tuned in, and she noticed a thread that was gaining traction. It wasn't a hundred people complaining, but it was a consistent, well-argued case from about fifteen active members. Luna: Fifteen out of three hundred doesn't sound like a lot. How did they avoid the vocal minority trap? Lucas: That's the key question. The community manager didn't just take the thread at face value. She set up an anonymous poll, separate from the public thread, to gauge broader sentiment. And that's where it got interesting: over two hundred members participated, and sixty-eight percent said they preferred 'Signal' and felt it better represented the tool's purpose. Luna: So the loud voices were actually aligned with the silent majority. That's rare. Lucas: Right. And that's the first lesson: you can't just rely on the loudest voices in the room, but you also can't ignore a well-reasoned argument. The poll gave the company the confidence to take the feedback seriously. Luna: But they still had to navigate the internal politics. I imagine the product team had their reasons for choosing 'Pulse.' Lucas: Oh, absolutely. The product manager had trademark concerns about 'Signal' because of other products in the space. But instead of just shutting it down, they went back to the community with that constraint. And that's the second lesson: be transparent about the boundaries. Luna: So the community didn't just get what they wanted; they understood why it was complicated. Lucas: Exactly. The company explained the trademark issue and asked if there were alternative names that captured the same essence. And the community responded with a bunch of suggestions. They eventually landed on 'Resonate,' which the company could actually use. Luna: So the community was part of the solution, not just the complaint department. That must have built a lot of trust. Lucas: It did. And the whole process took about two weeks. But here's the thing—the name change wasn't the real win. The real win was that the community felt heard and saw their input shape the product. That's the kind of thing that turns casual users into advocates. Luna: So, what would you say to a brand manager listening right now who's thinking, 'My community is too big, or too apathetic, to do this'? Lucas: I'd say size doesn't matter as much as the quality of the conversation. In this case, three hundred active members was enough. And apathy can be a symptom of not giving people a reason to care. When you open up real decisions to them, you'd be surprised how many step up. Luna: Yeah, that makes sense. It's like inviting people to help paint the wall instead of just asking them what color they'd like. Lucas: And that's a good segue to something else. This whole process reminded me of why we do what we do with this podcast—creating something that’s ad-free and community-supported. We don't have sponsors telling us what to cover, and that gives us the freedom to explore topics like this without any strings attached. Luna: It's true. And if you've found value in these conversations, maybe you've even applied something to your own community, consider supporting the show. It’s a small gesture that keeps this going. Lucas: The link is buy me a coffee dot com slash fexingo. That’s all it takes to keep these episodes ad-free and independent. Luna: And we're back to the naming story. So, after the community voted, what happened with the actual launch? Lucas: The launch was a success, but more importantly, they tracked something interesting: the churn rate for customers who joined during that period was thirty percent lower than their typical cohort. They attribute a lot of that to the sense of ownership those early users felt. Luna: That's a powerful number. It’s not just about the name, it’s about the story behind it. People love to be part of a story. Lucas: Exactly. And the company even documented the whole process in a blog post, giving credit to the community members who suggested the name. That public acknowledgment reinforced the relationship. Luna: So, what are some practical takeaways for our listeners who might want to do this without it backfiring? Lucas: First, make sure you have a community manager who is actually listening and can surface the good ideas from the noise. Second, use private polling to validate that an idea has broad support. Third, be transparent about constraints like trademarks or technical limitations. Luna: And fourth? Lucas: Fourth, be willing to say 'yes' when it makes sense. Not every suggestion needs to be adopted, but when the community is right, you should be able to admit it and change course. Luna: It sounds so simple, but it requires a lot of humility from the company side. Lucas: It does. And that's why so few brands do it well. They're afraid of setting a precedent that the community can just demand things. But in this case, the precedent was positive—it showed that the company listens and that the community's voice matters. Luna: I mean, we've seen what happens when brands ignore that voice. Remember the backlash when Coca-Cola changed the recipe in the eighties? They had to bring back the original. But this is different—this is bringing the community into the decision from the start. Lucas: Right. New Coke was a lesson in not listening. This is a lesson in co-creation. And the scale is different—a small B2B community versus a global consumer brand. But the principle holds: when you give people a stake, they become invested in the outcome. Luna: So, for our listeners who are thinking about starting a community or strengthening an existing one, what's the one thing you'd tell them to try this week? Lucas: Find one decision you were planning to make without community input and open it up to them. It could be as simple as a new feature name, a tagline, or even the theme for your next virtual meetup. Give them a real choice, with constraints, and see what happens. You might be surprised. Luna: And if it works, you might just find yourself with a more loyal community and a better product. It's a win-win. Lucas: It's been a good conversation. Next time, we're going to look at how communities can help with beta testing in a way that doesn't feel like free labor. That's a tricky one. Luna: Looking forward to it. Thanks for joining us.