Managing Community Feedback

Getting the right feedback will transform your job as a PM. More scalability, better user engagement, and growth. But most PMs don’t know how to do it right. Here’s the Feedback Engine I’ve used to ship highly engaging products at unicorns & large organizations: — Right feedback can literally transform your product and company. At Apollo, we launched a contact enrichment feature. Feedback showed users loved its accuracy, but... They needed bulk processing. We shipped it and had a 40% increase in user engagement. Here’s how to get it right: — 𝗦𝘁𝗮𝗴𝗲 𝟭: 𝗖𝗼𝗹𝗹𝗲𝗰𝘁 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 Most PMs get this wrong. They collect feedback randomly with no system or strategy. But remember: your output is only as good as your input. And if your input is messy, it will only lead you astray. Here’s how to collect feedback strategically: → Diversify your sources: customer interviews, support tickets, sales calls, social media & community forums, etc. → Be systematic: track feedback across channels consistently. → Close the loop: confirm your understanding with users to avoid misinterpretation. — 𝗦𝘁𝗮𝗴𝗲 𝟮: 𝗔𝗻𝗮𝗹𝘆𝘇𝗲 𝗜𝗻𝘀𝗶𝗴𝗵𝘁𝘀 Analyzing feedback is like building the foundation of a skyscraper. If it’s shaky, your decisions will crumble. So don’t rush through it. Dive deep to identify patterns that will guide your actions in the right direction. Here’s how: Aggregate feedback → pull data from all sources into one place. Spot themes → look for recurring pain points, feature requests, or frustrations. Quantify impact → how often does an issue occur? Map risks → classify issues by severity and potential business impact. — 𝗦𝘁𝗮𝗴𝗲 𝟯: 𝗔𝗰𝘁 𝗼𝗻 𝗖𝗵𝗮𝗻𝗴𝗲𝘀 Now comes the exciting part: turning insights into action. Execution here can make or break everything. Do it right, and you’ll ship features users love. Mess it up, and you’ll waste time, effort, and resources. Here’s how to execute effectively: Prioritize ruthlessly → focus on high-impact, low-effort changes first. Assign ownership → make sure every action has a responsible owner. Set validation loops → build mechanisms to test and validate changes. Stay agile → be ready to pivot if feedback reveals new priorities. — 𝗦𝘁𝗮𝗴𝗲 𝟰: 𝗠𝗲𝗮𝘀𝘂𝗿𝗲 𝗜𝗺𝗽𝗮𝗰𝘁 What can’t be measured, can’t be improved. If your metrics don’t move, something went wrong. Either the feedback was flawed, or your solution didn’t land. Here’s how to measure: → Set KPIs for success, like user engagement, adoption rates, or risk reduction. → Track metrics post-launch to catch issues early. → Iterate quickly and keep on improving on feedback. — In a nutshell... It creates a cycle that drives growth and reduces risk: → Collect feedback strategically. → Analyze it deeply for actionable insights. → Act on it with precision. → Measure its impact and iterate. — P.S. How do you collect and implement feedback?

That’s the thing about feedback—you can’t just ask for it once and call it a day. I learned this the hard way. Early on, I’d send out surveys after product launches, thinking I was doing enough. But here’s what happened: responses trickled in, and the insights felt either outdated or too general by the time we acted on them. It hit me: feedback isn’t a one-time event—it’s an ongoing process, and that’s where feedback loops come into play. A feedback loop is a system where you consistently collect, analyze, and act on customer insights. It’s not just about gathering input but creating an ongoing dialogue that shapes your product, service, or messaging architecture in real-time. When done right, feedback loops build emotional resonance with your audience. They show customers you’re not just listening—you’re evolving based on what they need. How can you build effective feedback loops? → Embed feedback opportunities into the customer journey: Don’t wait until the end of a cycle to ask for input. Include feedback points within key moments—like after onboarding, post-purchase, or following customer support interactions. These micro-moments keep the loop alive and relevant. → Leverage multiple channels for input: People share feedback differently. Use a mix of surveys, live chat, community polls, and social media listening to capture diverse perspectives. This enriches your feedback loop with varied insights. → Automate small, actionable nudges: Implement automated follow-ups asking users to rate their experience or suggest improvements. This not only gathers real-time data but also fosters a culture of continuous improvement. But here’s the challenge—feedback loops can easily become overwhelming. When you’re swimming in data, it’s tough to decide what to act on, and there’s always the risk of analysis paralysis. Here’s how you manage it: → Define the building blocks of useful feedback: Prioritize feedback that aligns with your brand’s goals or messaging architecture. Not every suggestion needs action—focus on trends that impact customer experience or growth. → Close the loop publicly: When customers see their input being acted upon, they feel heard. Announce product improvements or service changes driven by customer feedback. It builds trust and strengthens emotional resonance. → Involve your team in the loop: Feedback isn’t just for customer support or marketing—it’s a company-wide asset. Use feedback loops to align cross-functional teams, ensuring insights flow seamlessly between product, marketing, and operations. When feedback becomes a living system, it shifts from being a reactive task to a proactive strategy. It’s not just about gathering opinions—it’s about creating a continuous conversation that shapes your brand in real-time. And as we’ve learned, that’s where real value lies—building something dynamic, adaptive, and truly connected to your audience. #storytelling #marketing #customermarketing

Developer shares feedback...DevRel team nods enthusiastically...feedback vanishes into the void like a sock in a dryer. Three months later, same developer stops bothering. Can you blame them? Here's the absolutely maddening bit: most teams aren't ignoring feedback because they're incompetent or malicious. They're drowning in it. Discord messages, conference notes, survey responses...it's like trying to drink from a fire hose while blindfolded and riding a unicycle. The solution isn't collecting MORE feedback (good grief, no). It's treating feedback like you'd treat sales leads. Score it. Track it. Move the good stuff to your roadmap. Actually SHIP something based on it. At Stateshift we've helped teams transform this chaos with a stupidly simple system: centralize everything in one place, score each piece (1-5 on relevance, clarity, source credibility), review weekly, and...here's the revolutionary part...actually tell developers when their idea ships. Microsoft research found that feedback loops are one of the biggest factors in developer productivity. Yet most companies treat developer feedback like junk mail. When you close the loop...when developers see their suggestion in your release notes...that's when magic happens. They become advocates. They tell their friends. They stick around. The benchmark? Turn 10-20% of collected feedback into roadmap items. Ship 70-80% of those within a release cycle or two. Anything less and you're just performing theatre. Stop collecting feedback to feel good about "listening." Start treating it like the growth engine it actually is. ℹ️ I just wrote up a blog post digging into this in more detail. Link is in the first comment below 👇 #DeveloperRelations #ProductManagement #DeveloperExperience #CommunityBuilding #DevRel

The Paradox of Growth: The Bigger You Get, the Less You Know I came across something that stuck with me: When companies scale, they gain users — but lose understanding. Not because they stop caring, but because their customer feedback starts living everywhere — support tickets, sales calls, forums, surveys, social media, and app store reviews. That thought really made me pause. I’ve seen this firsthand. When a company is small, every piece of feedback feels personal — every bug report or review has a face behind it. But as you grow, those voices scatter across platforms and departments. Support sees the frustration, sales hears the hesitation, leadership sees the numbers — and somehow, everyone’s looking at the same customers, but no one’s hearing them anymore. That, in my opinion, is the quiet cost of growth. This is the problem Enterpret is solving — by helping teams stay in tune with their customers even as they scale. Here’s how it works: → It collects real-time customer feedback from 55+ channels — support tickets, sales calls, social media (X, Reddit, Instagram, Facebook), app store reviews, community forums, surveys, Slack, and more. → It analyzes all that feedback using AI and tells you exactly what to fix or build next. → It maps everything through a customer knowledge graph that connects feedback, complaints, and requests by channel, user, and payment data. → It even provides a chat interface where you can directly ask questions, and AI agents that flag bugs or issues automatically. That’s why teams like Notion, Perplexity, Canva, Chipotle, and The Farmer’s Dog use it — to make sure customer voices never get lost in the noise. In my view, the real lesson here isn’t about using more tools — it’s about staying close to the people you build for. Here’s how I’d approach it: ✅ Centralize every piece of feedback — even if it’s messy. ✅ Look for patterns instead of isolated complaints. ✅ Use AI systems like Enterpret to uncover the “why” behind what customers say. Because in the end, growth shouldn’t make you deaf. It should make you listen better — just faster. How does your team make sure you’re hearing what customers really mean, not just what they say? #CustomerFeedback #AIProducts #ProductStrategy #VoiceOfCustomer #Enterpret #Leadership

Your leadership team just got some brutal survey feedback and now wants to "stop all this surveying nonsense." Sound familiar? Here's the thing: When feedback stings, the instinct is to shut down the channel. But that's like unplugging the smoke detector because you don't like the beeping. The real issue (most often) isn't the feedback—it's that your leaders weren't prepared to handle it constructively. Here's how to fix this without killing your feedback culture: Only ask what you're willing to act on. If there's absolutely no willingness to change regardless of feedback, don't ask about it. For example, if raises are not happening due to budget constraints, don't ask employees if they want them. You're just creating false hope and inevitable disappointment. Create structured feedback channels with guardrails. Set up something like a Lattice Q&A board with clear submission standards: questions must be business-focused, assume positive intent, and be constructive rather than personal attacks. Have pre-written responses for why questions get deleted and a resubmission process. Equip leaders to handle tough, but fair, feedback. Leaders signed up for roles where they'll face heightened emotions and difficult conversations. Help them build emotional regulation skills through in-house or outsourced management training, referrals to executive coaching, and healthcare options that support access to mental health therapy. Be selective about whose opinions you let affect your decisions and emotional state. Pay attention to constructive feedback from people with positive intent showing up day in and day out to do similar or related, important work. And, let it be okay to ignore the opinions of anonymous dissenters who are not engaging in conversations on how to improve the situation or who have little to no context on similar challenges. Don't let one bad survey experience kill your entire feedback infrastructure. I've seen companies go silent for months or years after tough feedback, only to face bigger culture crises later because issues went underground. Here’s a little insider secret: The issues are still there. People just aren’t talking about them with you, the leaders, anymore. Leaders have a right to a harassment-free workplace, but they also choose roles that require engaging with difficult emotions and perspectives. The solution isn't silence—it's better preparation on how to respond when things get tough. __ 👋 I'm Melissa Theiss , 4x Head of People and Business Operations and advisor for bootstrapped and VC-backed SaaS companies. 🗞️ In my newsletter, “The Business of People,” I share tips and tricks that help People leaders think like business leaders.

Elena Verna gets flooded with 10,000+ customer voices daily at Lovable. Here's why she loves it... Most growth leaders would call this customer feedback hell. Elena calls it competitive advantage. As Head of Growth at Lovable (the fastest growing software company in history with $100M+ ARR), Elena shared something counterintuitive on Enterpret's new Customer Led Growth podcast: "I feel like I'm living in my customers' world and it's shouting at me from every single direction. It's more of a prioritization and filtering problem as opposed to trying to go out and get customer feedback." Her daily routine? 15 minutes, three times a day, making rounds across Reddit, Discord, and LinkedIn. Not responding to everything. Just absorbing patterns. "You have to pull your head out of quantitative data and really open up your mind to qualitative data and start looking for patterns there." This flips everything we thought we knew about VoC. For years, we focused on getting more customer feedback. Surveys, interviews, focus groups. The challenge was always: "How do we hear from more customers?" That was the old problem. The new problem is managing the flood. Your customers are already talking everywhere. On social platforms. In community forums. Through support tickets. The volume is overwhelming. The companies winning today aren't collecting more feedback. They're building systems to filter, prioritize, and act on the feedback flood that already exists. Elena's insight hit home for me. At Asana and Figma, we built VoC programs focused on gathering more voices. Today at Enterpret, we're helping teams manage the voices they already have. The shift from feedback drought to feedback flood changes everything. Your VoC program isn't about collection anymore. It's about intelligent pattern recognition at scale. Listen to the full conversation with Elena where she breaks down exactly how Lovable maintains customer intimacy while scaling at breakneck speed: https://lnkd.in/dh9ceMve What's your experience? Are you still trying to get more customer feedback, or have you shifted to managing what you already have?

Don't be that person that collects community feedback, and lets the report sit on the share drive. No shade, this happens to the best of us. It often happens simply because there isn't the right process in place for your team to use that community input. This post is part 2. Yesterday in part 1, I shared 5 tips for improving data collection with communities to have more relevant, usable data. Today, we're talking about how to use that data in decisions. 5 TIPS ON HOW YOUR INTERNAL PROJECT TEAM CAN USE COMMUNITY DATA TO INFORM DECISIONS 📍Tip 1: Have a meeting to interpret the data. ↳  You gain clarity by having the full project team talk about the data. What matters most? What context is missing? 📍Tip 2: Determine criteria for making the decision. ↳  It shows transparency, and it also helps the team build a framework for balancing the different elements (financial feasibility, outcomes, mission alignment, etc.). 📍Tip 3: Identify who is the ultimate decision maker. ↳  In collaborative work, we sometimes skip this step -to our detriment. Identifying roles around accountability is important. 📍Tip 4: "Projectize" the process. ↳  Often teams don't use data because they haven't identified decision points. By projectizing your community engagement you have a chance to identify objectives, deliverables and clear decision points. 📍Tip 5: Have the community engagement findings visible. ↳  Don't rely on your memory. Print out the key findings or have them projected on a screen so that you can see the actual words and priority themes from the community when you make the decision. TL;DR ✓ Start with better quality data from communities. ✓ Develop a clearly defined process for making the decision of interest. That's it. Be intentional about the process and it's easier than you think to make sure you are leverage community data in your decisions. What would you add? What do you find helps to ensure teams incorporate community input into decisions?

Every proposal I've reviewed promises "community participation in monitoring." Almost none deliver it. The language is everywhere. "Beneficiaries will be actively involved in the M&E process." "Community feedback will inform program adaptation." "Participatory approaches will ensure accountability to affected populations." Then implementation starts. And here's what actually happens: The M&E team designs the tools. The M&E team defines the indicators. The M&E team collects the data. Communities answer the questions they're given. The results go to the donor. At no point did a community member influence what was measured, how it was interpreted, or what changed because of it. After 20 years in this field, I've come to an uncomfortable conclusion: most participatory M&E in development is participation in name only. Here are 5 signs your participatory M&E is actually extractive: 1️⃣ Communities provide data but never see the results. If the findings travel upward to the donor but never travel back to the people who provided them, that's extraction. 2️⃣ The indicators were set before any community consultation. If communities are asked to provide data against definitions they had no role in shaping, they're data sources, not participants. 3️⃣ No program decision has changed because of community input. Participation without influence is theater. If community feedback sits in an annex and never reaches a decision-maker, the process serves the report, not the people. 4️⃣ The same questions are asked quarter after quarter with no visible response. Communities are perceptive. When they see that nothing changes despite their input, participation fatigue sets in. Attendance drops. Trust erodes. 5️⃣ There's no budget line for feedback to communities. Translation, accessible summaries, community meetings to share findings, if these aren't budgeted, participation was never the real intention. Here's what programs that do it well look like: ✅ They share findings with communities within 30 days. ✅ They track which decisions changed because of community feedback. ✅ They let communities define what "success" means in their context. ✅ And they treat downward accountability as seriously as upward reporting. Participatory M&E was designed to shift power. In most programs, it hasn't shifted anything except the workload onto communities who give their time and get nothing back. Most M&E systems are accountable upward to donors. Very few are accountable downward to communities. Something needs to be changed. Does community feedback actually influence decisions in your program? #MonitoringAndEvaluation #MEL #ParticipatoryME #Accountability #InternationalDevelopment #CommunityEngagement #AdaptiveManagement