Customer Feedback Collection Methods

“Loop engineering” is a hot buzzphrase after mentions of it by Boris Cherny (Claude Code’s creator) and Peter Steinberger (OpenClaw's creator) went viral on social media. Loops are now a key part of how we get AI agents to iterate at length to build software. In this letter, I’d like to share my 3 key loops, shown in the image below, for building 0-to-1 products. These loops guide not just how I build software, but also how I decide what software to build. Agentic coding loop: Given a product specification and optionally a set of evals (that is, a dataset against which to measure performance), we can have an AI agent write code, test its work, and keep iterating until the code is bug-free and meets its specification. This idea of closing the loop took off around the end of last year, and it has been a game changer in enabling coding agents to work longer productively without human intervention. For example, over the weekend, I was building an app for my daughter to practice typing, and my coding agent could easily work for around an hour, using a web browser to check what it had built multiple times before getting back to me, without needing my intervention. The engineering loop executes quickly. Every few minutes, the coding agent might build and test a new version of the software. I hear frequently from developers who are finding new ways to engineer more effective engineering loops. This is an active area of invention! Developer feedback loop: In this loop, a developer examines the current product and steers the coding agent to improve it. Last year, a lot of developers (including me) were acting as the QA (quality assurance) function for our coding agents, manually finding bugs and then asking the agent to fix them. But with coding agents much more able to test their own code, the amount of time we need to spend on this function has decreased significantly. This allows us to make higher-level product decisions, such as what key features to offer, where the UI needs improvement, and so on. The developer-feedback loop operates over time intervals between tens of minutes and hours — that's how frequently a developer might review a product and give feedback. In the case of the typing app, I changed my mind a few times about the visual design, what cat costumes she can unlock as she learns (she loves cats), and the user flow for a grown-up to log in and steer the child's learning experience. When a developer has a clear vision for what to build, it is still a lot of work to translate that vision into a specification for a coding agent to implement. Further, after the developer has seen an implementation, they might update (or perhaps clarify) the spec to steer it toward what they want. If you find that the system repeatedly runs into certain problems, building a set of evals for the agent becomes useful. [Truncated for length. Full text: https://lnkd.in/gKDQ6H9s]

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

A Zara store manager notices a jacket selling out on Tuesday. By the weekend, more are on the way. That loop is the entire business model. That feedback loop is a big reason Zara's parent company is worth more than H&M and Gap combined. What makes it possible: Zara's store managers feed sell-through data back to the warehouse within 24-48 hours. Not reports filed at the end of the week. Not monthly aggregations sent to a regional office. Within hours of a trend emerging on the shop floor, the signal is already moving upstream and the factory can respond. Most retailers work the opposite way. Data moves up the chain slowly, gets analyzed at head office, and decisions flow back down on a seasonal or quarterly basis. By the time a response hits the store floor, the trend that triggered it is usually over. Case studies consistently cite Zara selling through its stock ~11-12x per year, with very little left over to discount. Fashion retailers that restock on longer cycles end up sitting on excess inventory and putting everything on sale to clear it. This isn't a technology story. H&M has also invested heavily in store tracking technology and data tools. The real difference is organizational. H&M store managers largely execute the display plans set by headquarters. Zara store managers actively relay customer demand signals back to HQ: what's moving, what customers are asking for, what's sitting. Those inputs shape production and allocation decisions at pace. One analysis estimates ~25% of Zara's parent company's spending goes to labor: more than many competitors. But that workforce isn't just executing tasks. It's feeding the system that determines what gets made and shipped. The traditional retail model treats stores as distribution endpoints. Corporate decides, stores execute. Information flows one way: down. Zara flipped it. Stores became sensing mechanisms. Information flows up, decisions flow down, then loop back again. Continuously.

Had an insightful conversation over the weekend with a colleague about a common pitfall in CX programs: relying solely on surveys and ignoring other valuable insights. Here are some key takeaways: Ease of Implementation Surveys are easy to deploy and manage, providing quantifiable data that’s simple to analyze. This makes them an attractive option for many organizations, especially those with limited resources. Tradition and Comfort Many companies stick to surveys because it’s what they’ve always done. Changing this entrenched practice can be challenging, especially if the leadership team prefers traditional methods. Resource Constraints Surveys can be cost-effective, making them appealing for smaller organizations that may not have the budget for more sophisticated tools. Organizational Silos Feedback often gets trapped within departmental silos, preventing insights from being shared and acted upon. Lack of Ownership Without clear ownership of the feedback loop, survey results can end up being ignored. It’s crucial to have designated teams responsible for analyzing feedback and driving action. Inadequate Analytics Capabilities Many companies lack the analytical capabilities - people and tech - to turn survey data into meaningful insights. Cultural Resistance Taking action on feedback requires change, which can be met with resistance. Companies need a culture of continuous improvement to effectively address feedback. Short-Term Focus Organizations sometimes prioritize short-term gains over long-term improvements, leading to reluctance in making significant changes based on feedback. Here is where we ended in terms of actions to take: 1. Integrate Multiple Data Sources: Combine survey data with digital analytics, social listening, and customer journey mapping for a comprehensive view of the customer experience. 2. Foster a Customer-Centric Culture: Encourage leadership commitment, employee training, and recognition programs that reward customer-centric behavior. 3. Invest in Analytics: Enhance analytics capabilities to turn data into actionable insights. 4. Close the Feedback Loop: Implement a closed-loop feedback system and communicate changes to customers. 5. Design Thinking and Customer Co-Creation: Use design thinking methodologies to deeply understand customer needs and co-create solutions. 6. Cross-Functional Collaboration: Promote collaboration across departments to discuss feedback and develop action plans. 7. Measure Impact and Iterate: Continuously measure the impact of changes and iterate to improve further. What are you doing to get out of the CX-as-a-survey (CXaaS) trap? #customerexperience #cx #surveys #analytics #designthinking #customercentric

There is absolutely no point in gathering feedback from employees without creating feedback loops and USING feedback to inform improvement. WHAT IS AN EMPLOYEE FEEDBACK LOOP❓ An employee #feedbackloop is just one of many feedback loops in organizations. It is a structured process where people provide input or comments about their work experiences, job satisfaction, or performance, and this #feedback is used by the organization to make improvements, enhance employee engagement, and create a better working environment. That last part is where many organizations fall down... they don't USE feedback to inform improvements. This is a huge missed opportunity!! Employee feedback is a powerful way for organizations to identify improvement areas. Also, when people see that they are taken seriously, they feel heard and valued, and this feeling can significantly enhance engagement and job satisfaction. There is a real danger in asking for people's feedback and then ignoring it...or failing to acknowledge it. People lose engagement and trust... slowly they stop giving feedback.... and the organization struggles to improve. 💥 CREATING FEEDBACK LOOPS 💥 If you are thinking of creating/improving your employee feedback loops, here are some high-level steps to guide you: 1️⃣ Identify the type of feedback required 2️⃣ Select Feedback Methods 3️⃣ Regularly Collect the Feedback 4️⃣ Analyze and Share Results 5️⃣ Take Action 6️⃣ Follow Up 7️⃣ Track Progress: 8️⃣ Celebrate Successes 9️⃣ Iterate and Improve: Every single one of these 9 steps are important. And not very difficult. All it takes is good leadership and organization. Remember that feedback should not be a once-off effort. It is important to aim towards creating a feedback culture, where regularly giving and receiving feedback is encouraged and valued. Consistency is key! _______________________________________ I'm Catherine McDonald- Lean Business and Leadership Coach. Follow me for insights on Lean, Leadership, Coaching, Strategy and Organizational Behaviour

A support agent solved a login issue in 38 seconds. The customer gave them 1 star. The answer was correct. The issue was resolved. The customer was just annoyed they had to contact support in the first place. I shared this story. What happened next was more interesting than the story itself. Smart support people looked at the same interaction… and disagreed completely. One camp said: This should never have hit support. If customers contact you for basic issues, your self serve is broken. Another said: No, this is valuable feedback. The rating isn’t about the agent. It’s telling you the journey is broken upstream. A third said: The real mistake is using this interaction to evaluate support performance at all. Same ticket. Same transcript. Same 1 star. Three different conclusions. Most support teams don’t have a ticket problem. They have an interpretation problem. Is this: a support issue a product issue a self serve issue or a measurement issue? If your team answers that question differently every time… You’re not improving anything. You’re just having different conversations about the same problem. The hardest part of support isn’t solving tickets. It’s agreeing on what the ticket is evidence of. Until you do that… Every metric will be debated. Every decision will feel incomplete. And every improvement will fix the wrong thing.

Every company says they listen to customers. But most just hear them. There's a difference. After spending years building feedback loops, here's what I've learned: Feedback isn't about collecting data. It's about creating change. Most companies fail at feedback because: - They send random surveys - They collect scattered feedback - They store insights in silos - They never close the loop The result? Frustrated customers. Missed opportunities. Lost revenue. Here's how to build real feedback loops: 1. Gather feedback intelligently - NPS isn't enough - CSAT tells half the story - One channel never works Instead: - Run targeted post-interaction surveys - Conduct deep-dive customer interviews - Analyze product usage patterns - Monitor support conversations - Build customer advisory boards - Track social mentions 2. Create a single source of truth - Consolidate feedback from everywhere - Tag and categorize insights - Track trends over time - Make it accessible to everyone 3. Turn feedback into action - Prioritize based on impact - Align with business goals - Create clear ownership - Set implementation timelines But here's the most important part: Close the loop. When customers give feedback: - Acknowledge it immediately - Update them on progress - Show them implemented changes - Demonstrate their impact The biggest mistakes I see: Feedback Overload: - Collecting too much data - No clear action plan - Analysis paralysis Biased Collection: - Listening to the loudest voices - Ignoring silent majority - Over-indexing on complaints Slow Response: - Taking months to act - No progress updates - Lost customer trust Remember: Good feedback loops aren't about tools. They're about trust. Every piece of feedback is a customer saying: "I care enough to help you improve." Don't waste that trust. The best companies don't just collect feedback. They turn it into visible change. They show customers their voice matters. They build trust through action. Start small: 1. Pick one feedback channel 2. Create a clear process 3. Act quickly on insights 4. Show results 5. Scale what works Your customers are talking. Are you really listening? More importantly, are you acting? What's your approach to customer feedback? How do you close the loop? ------------------ ▶️ Want to see more content like this and also connect with other CS & SaaS enthusiasts? You should join Tidbits. We do short round-ups a few times a week to help you learn what it takes to be a top-notch customer success professional. Join 1999+ community members! 💥 [link in the comments section]

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

HR doesn’t need more dashboards. It needs better listening. Most people teams measure what’s easy…like engagement scores or turnover. But the best teams? They build feedback loops that help them predict problems, not just react to them. This post gives you 11 of the most useful, often-overlooked loops you can implement across the employee lifecycle: 🟢 Week 2 new hire check-ins (capture early impressions) 🟠 Post-interview surveys (from both sides) 🔵 Onboarding reviews (day 90 is your goldmine) 🟡 Skip-level 1:1s (cross-level truth-telling) 🟣 Quarterly team health check-ins (lightweight, manager-led) …and 7 more. 📌 Save this if: • You’re building a modern HR function • You want fewer “We should’ve seen this coming” moments • You believe listening is strategy Which feedback loop is missing in your company?