Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How Community Managers Turn Feedback Into Product Roadmaps
Transcript
- Lucas: We talk a lot about how communities build brand loyalty, but there is a specific mechanical failure that happens when those communities stop feeding directly into product decisions. It turns out that most companies treat their Discord or Slack groups as customer support channels first, and product research labs second. That hierarchy creates a massive blind spot in your roadmap. Luna: Exactly. You end up with a product team that builds what they think people want, while the actual users are shouting into the void about things they actually need. It is a disconnect that kills retention faster than any bug. Lucas: Let us look at a concrete example from the last few years. Notion became a household name not just because of its interface, but because they treated their community as a co-creation engine. They did not just listen; they published their own internal roadmaps in public channels. When a user suggestion gained enough traction in the community, it moved to the top of the engineering queue. This transparency turned passive users into active evangelists who felt ownership over the final product. Luna: But that level of transparency requires a massive operational shift. Most companies are terrified of promising something they cannot deliver, so they keep the roadmap locked away. How do you balance honesty with feasibility? Lucas: The answer lies in separating signal from noise, which is where community managers become critical. They are not just moderators keeping the chat clean; they are data analysts who categorize sentiment. At Figma, for instance, they use a tagging system in their forums that maps directly to Jira tickets. If three hundred people tag a feature request as 'critical workflow blocker,' it bypasses the usual triage phase. It is systematic, not emotional. Luna: So it is less about listening harder and more about having better infrastructure for capturing intent. What happens when the loudest voices in the community want something that contradicts the broader user base? Lucas: That is the classic trap. You get captured by your power users. I remember reading an internal memo from a mid-sized project management tool that realized sixty percent of their feature requests were coming from twenty percent of their users. Those power users had complex, custom workflows that the other eighty percent found confusing. The decision was to deprioritize the niche request and simplify the core experience. It caused a brief revolt in the Slack group, but retention stabilized because the new users could actually onboard without friction. Luna: That is a tough call to make publicly. How do you explain to the power users that you are abandoning their wishlist without losing their trust? Lucas: You frame it as scalability. You tell them that to serve the mass market, you have to remove complexity. It is a strategic trade-off, not a dismissal. But here is the bigger issue: even if you implement the right features, you might still fail if you do not measure the outcome correctly. Most companies track vanity metrics like message volume or daily active users. Those do not tell you if the community is improving the product. Luna: Right. High activity does not equal high value. You can have a very noisy community that is actually frustrated and looking for alternatives. What metrics should we be watching instead? Lucas: Look at adoption rates of newly released features. If you release a change based on community feedback, does usage go up? Or does it sit flat? Then look at churn correlation. Did the customers who engaged with the feedback loop stay longer than those who did not? A study from two years ago showed that customers who submitted at least one feature request and saw it implemented had a thirty-five percent lower churn rate over twelve months. That is a direct revenue lever hidden in your chat logs. Luna: Thirty-five percent is significant. But implementing every good idea is impossible. So how do you decide which ones to pick without burning out your engineering team? Lucas: You prioritize by effort versus impact. And you let the community help you score that. Some platforms now allow users to vote on feature requests. The ones with the highest votes and lowest estimated implementation cost rise to the top. It democratizes the prioritization process. However, you have to be careful about gaming the system. Power users will organize campaigns to push their pet projects to the top, skewing the data. Luna: So you need guardrails around the voting mechanism itself. Otherwise, you are just building a popularity contest rather than a product strategy. Does this work for B2B companies as well, or is it mostly a B2C phenomenon? Lucas: It works exceptionally well for B2B, especially in enterprise software where sales cycles are long. Salesforce has a community called Trailblazer that essentially functions as a beta testing ground for new modules. Enterprise clients submit detailed requirements, and Salesforce engineers engage directly in the threads. It reduces the risk of building useless features because the buyers are validating the demand before code is written. It shifts the cost of R&D onto the validation phase. Luna: That makes sense. You are getting paid to test your ideas by the people who would buy them. But what about the legal side? If a community member suggests a feature and you build it, do they have any claim to it? Lucas: Generally no, provided you have clear terms of service. Most community guidelines state that all submissions become the intellectual property of the company upon posting. It is standard practice, but it is worth reiterating. The bigger risk is not IP theft; it is reputation damage. If you ignore a widely supported suggestion, the backlash can be severe. You have to close the loop. Tell them no, and explain why. Silence is louder than rejection. Luna: Closing the loop is often the hardest part operationally. It takes time to write personalized responses or update status pages. Do smaller teams struggle with this more? Lucas: Absolutely. Small teams lack the dedicated community manager role. The founder ends up being the face of the company, which leads to burnout. The solution is automation mixed with human touch. Use bots to acknowledge receipt of a suggestion instantly. Then, have a human review the weekly digest. You do not need to reply to every single comment, but you must reply to the trends. If ten people ask for the same thing, send a single pinned post addressing that trend. Luna: A pinned post acts as a public record. It shows progress without requiring constant individual attention. Is there a danger in becoming too reactive to community demands though? Like, losing your own vision? Lucas: There is. Steve Jobs famously said customers do not know what they want until you show it to them. You cannot build the next iPhone by asking users what they need in a forum. The key is to distinguish between incremental improvements and paradigm shifts. Listen to the community for tweaks, optimizations, and bug fixes. Keep your vision for the big leaps. Blend the two, but do not let the crowd steer the ship entirely. Luna: So the community manager is the filter, not the funnel. They let the useful data through but block the noise that could derail the strategy. It is a gatekeeping role disguised as facilitation. Lucas: Precisely. And that role is evolving. With AI tools now available, community managers can use natural language processing to analyze thousands of comments in minutes. They can identify emerging themes that humans might miss. It scales the insight generation process. But it still requires a human to interpret the context. An AI might flag a spike in negative sentiment, but it takes a person to understand if it is about a pricing change or a server outage. Luna: Technology helps, but the culture has to support it. If the product team ignores the insights anyway, the whole system collapses. How do you force cross-departmental alignment on this? Lucas: You tie it to compensation. Make community health a KPI for product leaders. If retention drops, the product lead owns that, regardless of whether it was a bug or a missing feature. When incentives align, departments start talking to each other. You stop seeing community as a cost center and start seeing it as a revenue driver. That cultural shift is harder than any technical implementation. Luna: I love that. Financial skin in the game usually solves these organizational silos quickly. What about the visual aspect? How do you present this data to stakeholders who are not technical? Lucas: Dashboards. Simple, clean dashboards that map community sentiment to business outcomes. Show the correlation between feature requests and renewal rates. Executives respond to numbers, not anecdotes. When you can prove that one dollar spent on community management yields four dollars in retained revenue, the budget discussions become easy. It becomes an investment, not an expense. Luna: Four to one return. That is a compelling ratio. It changes the conversation from 'do we need this team' to 'how can we scale this team.' Are there any common pitfalls you see companies fall into when trying to replicate this model? Lucas: They try to copy the platform, not the process. They buy a Discord server and hire a moderator, expecting magic to happen. But without the integration into the product cycle, it is just a chat room. The magic is in the feedback loop closing back to engineering. If you skip that step, you are just building a social club, not a business asset. Luna: Social clubs are fun, but they do not pay the bills. It seems like the real value is in the operational discipline required to maintain that loop. It is unglamorous work. Lucas: It is. And that is why it is a competitive advantage. Everyone wants to be the cool startup with the vibrant community. Fewer are willing to do the boring work of tagging, categorizing, and reporting. But that boring work is where the intelligence lives. It is the difference between guessing and knowing. Luna: Knowing exactly what your customers need before they even fill out a survey. It feels like a superpower when you get it right. Do you think this approach will become standard for all software companies within five years? Lucas: I think it will become the baseline for survival. As competition intensifies, product features alone are not enough. The ecosystem around the product becomes the moat. Companies that fail to integrate their community into their product strategy will find themselves commoditized. The ones that thrive will be the ones that make their users feel like partners. Luna: Partners, not just consumers. That is a fundamental shift in how we view the customer relationship. It moves beyond transactional interactions into relational equity. Lucas: Exactly. Relational equity compounds over time. A user who helped build a feature feels protective of it. They defend it against competitors. They advocate for it to peers. That is organic growth that no ad spend can buy. It is built on trust and transparency. Luna: Trust is the currency of the modern economy. And communities are the banks. It is a powerful metaphor that really underscores the importance of getting this right. Lucas: I am glad you put it that way. It reminds us that we are managing assets, not just hosting chats. Every interaction is a deposit or a withdrawal from that trust account. Luna: And we have seen plenty of withdrawals lately. It is refreshing to focus on the deposits. Before we wrap up, we want to mention something important about how this show operates. Lucas: We deliberately do not run ads on these episodes. We believe that keeping the content free and accessible is part of our commitment to the business community. If you find value in these conversations and want to support that choice, the link is buy me a coffee dot com slash fexingo. Luna: Your support directly funds the research and production quality that keeps these episodes running. It allows us to dig deeper into topics like this without compromising our independence. Lucas: Thank you for considering it. Now, back to the question of relational equity. How do you measure the intangible feeling of partnership in hard numbers? Luna: Through net promoter scores tied to community engagement levels. Users who are highly active in the community consistently report higher NPS. It quantifies the qualitative bond. Lucas: So the metric exists. It just requires linking two different data sets. Customer satisfaction and community participation. When you overlay them, the pattern becomes undeniable. Engagement drives satisfaction, which drives retention. Luna: And that cycle reinforces itself. The more satisfied users are, the more they engage. The more they engage, the better the product gets. It is a virtuous circle. Lucas: A virtuous circle that rewards patience and consistency. It is not a quick fix. It is a long-term strategy for building a resilient brand. What do you think is the first step a CEO should take tomorrow morning to start this journey? Luna: Audit the current feedback channels. See where the data is sitting and who is responsible for acting on it. Break down the wall between support and product. Lucas: Break down the wall. Start the conversation. It might seem small, but it signals a shift in priority. And sometimes, that signal is enough to unlock the potential already inside your organization.