Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How Communities Turn Critics Into Co-Designers
Transcript
- Lucas: The hardest part of community management isn't keeping the chat active. It's handling the people who show up to burn it down. Most brands treat criticism as noise to be filtered out, but a few companies have figured out how to treat it as raw material for product development. Luna: Right, because those are usually the most engaged users. They just happen to be engaged in a negative direction. How do you flip that energy without looking like you're ignoring them? Lucas: You don't flip it by arguing. You flip it by giving them access. I've been looking at a few SaaS companies that use Discord not just as a help desk, but as a co-design studio. They invite the loudest critics into private channels where they can see the actual backlog and vote on features. It changes the dynamic from adversarial to collaborative almost overnight. Luna: That is a bold move. Letting the people who threaten to churn see your unfinished work seems risky. Do they actually stick around once they realize the product isn't perfect yet? Lucas: They stay because they feel ownership. There is a specific case with a project management tool that had a massive backlash over their new interface. Instead of rolling back the change or issuing a generic apology, they opened a 'Design War Room' channel. They posted wireframes, asked for brutal feedback, and implemented three changes based on those comments within two weeks. The same people who were threatening to leave started posting screenshots of their new workflows. Luna: So the key is visibility. Showing them the machine works, even if it's clunky right now. That builds more trust than a polished feature launch ever could. Lucas: Exactly. It signals that you value their expertise over your ego. But this requires a very specific operational structure. You can't just open a channel and hope for the best. You need dedicated moderators who understand product logic, not just customer service scripts. If a critic asks why a feature isn't there, the answer can't be 'we'll look into it.' It has to be 'here is the current priority list, and here is how your suggestion ranks against our technical constraints.' Luna: That level of transparency is rare. Most brands hide behind vague promises. Why do you think so few companies attempt this radical honesty? Lucas: Fear of losing control. Marketing teams are trained to sell the finished product, not the messy process. Admitting that a feature is half-baked feels like admitting weakness. But in a community context, it’s actually a strength. It shows you’re listening and adapting in real time. Luna: I wonder if this works for physical products too. Can you co-design a sneaker or a coffee blend in a Slack group? Or is this only for digital goods? Lucas: It absolutely works for physical goods. We saw this with a small craft beer brand that used Instagram DMs and a private Discord server to let customers vote on hop varieties for their next seasonal release. They didn't just ask for a preference; they sent samples to fifty active community members first. Those members created video reviews, which became the core content for the public launch. The critics who said the initial draft was too bitter helped refine the recipe until it hit the mark. Luna: That’s fascinating. They turned the sampling phase into a content creation engine. So the product quality improves, and you get free marketing material at the same time. Lucas: Precisely. It’s a double win. But it requires a shift in how you measure success. Traditional metrics look at net promoter score after launch. This approach looks at engagement depth during development. Are the right people talking? Is the conversation getting more constructive over time? Luna: And what about the risk of bad actors? Sometimes these groups attract trolls who aren't interested in helping, just causing drama. How do you separate the constructive critics from the chaos agents? Lucas: You filter for history, not just sentiment. In those successful cases, they require a minimum tenure in the community before you can access the Design War Room. You also set clear norms. If someone violates the code of conduct, they lose access immediately. No exceptions. This protects the psychological safety of the genuine contributors. Luna: So it’s a gated privilege. You earn the right to shape the product by being a good citizen of the community first. Lucas: Yes. And that gatekeeping is crucial. It prevents the space from being hijacked by bad faith actors. Once the core group is established, they often self-police. They’ll call out someone who is being unhelpful, which reinforces the culture you’re trying to build. Luna: I love that. Peer accountability is usually stronger than top-down rules. It makes the community feel like a real place, not just a corporate broadcast channel. Lucas: It does. But there is one major hurdle: bandwidth. Managing a co-design program is resource-intensive. You need product managers, designers, and community leads all aligned. If you promise input and then deliver nothing, you destroy trust faster than any bad product decision ever could. Luna: That’s the trap. Opening the door and then slamming it shut when the board says no. How do you manage expectations when the community’s wish list doesn’t match the company’s budget? Lucas: You communicate the trade-offs clearly. If a requested feature is too expensive to build, you explain the cost-benefit analysis. You might say, 'This would take six months of engineering resources. Here is a simpler workaround we can implement in two weeks instead.' It shows respect for their intelligence and gives them an immediate win while they wait for the bigger solution. Luna: Giving them a tangible interim solution is smart. It keeps the momentum going even when the big dream is delayed. Does this model scale to larger enterprises? Or does it only work for smaller, agile teams? Lucas: It scales, but it requires decentralization. Large companies can’t have everyone talking to the central product team. Instead, they create regional or niche-specific pods. A gaming company might have separate design channels for different genres. Each pod has its own lead who aggregates feedback and presents it to the main product council. It’s like a franchise model of community engagement. Luna: Franchise model. I like that. It allows for local relevance while maintaining global consistency. So the critics aren't shouting into a void; they're shouting into a focused ear. Lucas: Exactly. And that focus increases the signal to noise ratio. When feedback comes from a specialized group, it’s easier to act on. You aren’t drowning in general complaints; you’re getting targeted insights from experts. Luna: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Lucas: Yeah, it really helps keep the research deep and the commentary sharp. Thanks for considering it. Luna: Back to the scaling question. What happens when the community grows too large for individual attention? Do you lose that personal touch? Lucas: You automate the low-value interactions and humanize the high-value ones. Chatbots handle basic FAQs. Humans handle the complex design discussions. This tiered approach ensures that the most valuable voices still get a human response, even as the total volume of messages explodes. Luna: So automation supports the relationship rather than replacing it. That’s a refreshing perspective on tech efficiency. Lucas: It has to. If you automate everything, you’re just building a better FAQ page. The goal is to create a sense of shared destiny between the brand and the user. That can’t be scripted. Luna: Shared destiny. That’s the ultimate metric, isn't it? Not just sales, but survival together. Lucas: Precisely. When users feel they own a piece of the outcome, they defend the brand during tough times. They become advocates, not just customers. That resilience is invaluable in a volatile market. Luna: Do you think traditional PR firms will ever adapt to this, or will they always view community sentiment as something to be managed rather than cultivated? Lucas: Some are adapting, but many are stuck in crisis mode. They want to suppress negative news, not amplify positive co-creation. The agencies that survive will be the ones that learn to facilitate conversations, not just control narratives. Luna: Facilitators instead of gatekeepers. That’s a significant role reversal for the industry. Lucas: It is. And it requires a completely different skill set. Empathy, patience, and technical fluency. These are hard skills to find, which is why early adopters have such a competitive advantage. Luna: So the moat isn't the technology. It's the culture you build around it. Which is much harder to copy. Lucas: Exactly. Technology is easy to replicate. Culture takes years to nurture. Once you have that, you have a defensible position that competitors can’t simply outspend you on. Luna: What’s the first step for a company that wants to start this journey tomorrow? Where do they begin? Lucas: Start small. Pick one frustrated user segment. Invite ten of them to a closed feedback loop. Listen more than you speak. Implement one small change based on their input. Then repeat. Momentum builds through visible action, not grand announcements. Luna: Small wins that compound into trust. Simple advice, but probably the hardest to execute consistently. Lucas: Consistency is the currency of community. Spend it wisely.