Customer Feedback Integration

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

Do you sometimes feel frustration, as you are building a product to get the management off your back, rather than address the users? Here are 6 ways to become user-centric again: 1) Prioritize in a transparent way This is a great place to start. If your backlog is prioritized based on data and potential opportunity, risk, and cost, it will be easier to put forth user-centric initiatives ahead of those that came from upstairs. At the very least, you will have a good basis for an educated discussion. 2) Utilize users' perspective using user stories and personas If your team understands the users and their problems, it will be easier to craft something great that will later appeal to the same users. Just keep up the empathy of creating something by people for other people, and not get some metric magically go up! 3) Understand user problems If everyone in the company can see the themes that come from user feedback, it will be way harder to ignore it in favor of some corporate nonsense. Let those voices be heard by everyone! What if there are 100,000s of voices? Here is where this post's partner comes in: Productboard , and their new release: Productboard Pulse. It's a powerful new tool you can use either as a standalone solution or to elevate your work within an existing Productboard product management suite. This new AI will help you make sense of all the feedback and comments, quickly transforming them into actionable, user-centric tasks. Check out the comments for more details :) Now, back to the post: 4) Have the NPS and user ratings at the forefront The same goes for a single metric representing the general product sentiment. If the number is low or, worse, is going down and everyone can see that, the responsible Product Manager has to react. 5) Focus on your product goals Now, upstairs mandates might not be the only distraction you face when trying to improve your product. To survive them all, focus on one thing: your product goals. This will allow you to demonstrate you are doing what you are asked for and you can use user feedback and points 1-4 to pursue those goals. Thus, it's like killing 2 birds with 1 stone. However, you can also simply: 6) Have the confidence to say "No" Not all company/legal/management requests can be ignored. Sometimes changing the law or a wider company initiative will require you to comply and that is OK! However, there will also be times when someone will try to force your compliance. This is where you need to be confident, and exercise your Product Manager's independence, especially when there is no data to support a specific request. There you go! My 6 ways you can become a user-centric Product Manager. Do you put your users first in your product? Sound off in the comments! #productmanagement #productmanager #usercentricity

Customers are speaking to you through data every day. Just as employees, we should show up to work as our whole selves each day; your customer should too. Beyond the periodic surveys that have long been our comfort zone. Every digital touchpoint, transaction log, and customer interaction offers insights that continuously shapes the CX landscape. The signals are clear, so relying solely on surveys leaves a significant portion of customer insights untapped. As CX leaders, it's imperative to integrate data from multiple channels to uncover the full customer experience. Traditional feedback tools provide a snapshot, but the real story is written in the everyday behaviors and interactions across digital and physical platforms. Analytics is the new way forward. Harnessing real-time data from operational systems, transactional records, and behavioral metrics empowers your company to understand, meet, and anticipate evolving customer needs. Organizations that are blending diverse data streams enjoy a competitive edge. This holistic view is essential for proactive decision-making. And adopting a multi-source data strategy enables you to pivot more swiftly in today’s dynamic market environment. Look beyond the survey; tap into the rich, complex dialogue your customers are engaging you in daily. These insights are critical for designing experiences that drive sustainable growth. PS: The percentages are based on my own observation and are not meant to be accurate. I am also sure I've left off categories. So if you turn this into a debate about either %'s or titles, you've missed the point.

Vibe coding is cool and all, but can we take a minute to show some love for how AI has compressed standard PMM workflows from weeks (if not months) to literal hours? On Friday I got hit with a request to run a messaging gap analysis for a part of the business that isn’t performing where we want it. Pre-AI, this would’ve been such a heavy lift I’d probably have had to throw it into my quarterly OKRs just to justify the time. With AI, I did it in two hours. Two. And it wasn’t some lightweight, “directionally correct” version. I went all in. Here’s what I did: I pulled relevant win-loss interviews from the past two quarters to anchor on what actually influenced purchase decisions. Then I created a Glean agent to mine our customer NPS Slack channel so I could see how existing customers are talking about their experience in real time and in their own language. From there, I queried our Audience Insights Agent to mine Gong calls for patterns — how we’re positioning today, how it shifts by segment, industry, and persona, whether it aligns with what prospects say they need, how they respond during demos, and what gets categorized as “need to have” vs “nice to have.” Next, I cross-referenced all of that against our 2026 product roadmap to understand what exists, what’s coming, and where expectations could drift. I also pulled a market insight report in Perplexity built from 196+ external sources — analyst research, practitioner forums, competitive assets from 15+ vendors, and broader learning-tech trend and adoption studies — to make sure the view wasn’t purely internal. Once everything was assembled, I fed the reference material into a custom GPT and used it to pressure-test our current messaging across all signals: where it lands, where it doesn’t, what feels thin, and what deserves more attention. The output was a concise report with recommendations on where to pivot. Again, all of this, in two hours, with AI. 🤯

How to fail in an interview Role: Product Owner/Product Management Topic: Product Success 👔 Interviewer: “As a Product Owner, how do you measure the success of a product increment?” 🧑 Candidate: “I check if the increment was delivered on time and within the scope.” 👔 Interviewer: “Let’s add complexity. Imagine this: After a release, the product increment is on time and within scope, but customer adoption is low, and users report it doesn’t solve their problem. Stakeholders are questioning the value delivered. What would you do in such a scenario?” 🧑 Candidate: “I’d ask the team to fix it in the next sprint.” What the Product Owner Should Have Answered: ------------------------------------------------------ Focus on Value: “Timeliness and scope are important, but true success lies in customer satisfaction and achieving business outcomes. I would define success metrics such as NPS, adoption rate, and business KPIs before development.” Validate Assumptions Early: “I’d ensure the increment was tested with users during development, leveraging prototypes or beta testing to validate assumptions.” Feedback Loop: “Post-release, I’d actively collect user feedback through analytics and interviews, identifying gaps and iterating to enhance the product.” Stakeholder Communication: “I’d communicate these learnings with stakeholders, ensuring transparency and aligning future increments to address these insights.” Impact of the Right Answer: ✅ Customer-first approach: Prioritizes delivering real value. ✅ Continuous improvement: Promotes iteration based on feedback. ✅ Stakeholder trust: Demonstrates proactive and transparent ownership. Takeaway for POs: Product ownership isn’t just about delivering features; it’s about delivering outcomes that delight customers and achieve strategic goals. How do you measure success? Let’s discuss below! 🚀 Need Deeper Insights? Join "Agile Interview Hub": Link in the comment section below #Agile #ProductOwner #Interview

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?

When Johnson & Johnson spun off Kenvue, many of the leaders who joined saw it as an opportunity to operate in a fast, agile, stand-alone environment. Now, as Kimberly-Clark acquires Kenvue for nearly $49B, I can’t help but wonder: what happens to that kind of talent next? People who thrive in a start-up-like culture: speed, ownership, experimentation - often find it hard to adjust to a slower, more structured, process-heavy organization. And Kimberly-Clark, while world-class in legacy and discipline, is not known for agility or fast-paced innovation. So the question becomes: will Kimberly-Clark recognize and leverage the entrepreneurial talent they’ve just inherited or will those people eventually walk away, frustrated by hierarchy and pace? In M&A, most of the headlines focus on synergies and cost savings. But cultural integration is where deals often succeed or fail. Especially in consumer goods, where people and creativity drive performance more than any spreadsheet ever will. Curious to hear from my FMCG network: how can established giants like Kimberly-Clark preserve the innovative DNA of the companies they acquire? #FMCG #Growth #Trending #Consumergrowth

Surveys aren't enough. You're missing big opportunities if you rely only on surveys for customer feedback. Customers share what they think all the time—but not always in direct ways. The best brands go beyond surveys to uncover what really matters. Here are 3 overlooked ways to gather customer feedback: 🗣️ Listen to Unsolicited Feedback – Reviews, social media comments, and even casual mentions hold valuable insights. 📞 Tap into Frontline Teams – Customer service and sales teams hear real frustrations and needs every day. 📊 Analyze Behavioral Data – Actions speak louder than words. Where do customers hesitate, drop off, or struggle? Surveys are just one piece of the puzzle. Ready for smarter ways to gather feedback? Get more hacks in this article. #CX #CustomerFeedback #CustomerExperience #VoC #CustomerSurvey

We do not implement every user feedback. Here’s why (+our 3-step process) Since we launched Scripe, we got a lot of user feedback But here's the thing... Trying to implement everything can turn your product into a mess. Here's what I've learned: → Users often want features that don't align with our core vision. While they might be helpful for some, they can clutter the product for others. → Balancing user suggestions and our own insights is key. Our team focuses on innovating rather than firefighting endless feature requests. → Each new feature adds complexity. This means increased costs for development and maintenance, often the resources are better spent on enhancing core functionalities. So, we developed a 3-step process: 1/ Prioritize Essentials → We ask: Does this feature serve most users? Is it aligned with our mission? 2/ Conduct In-Depth Research → Not every request is a "yes." We dig deep into the real needs behind feedback. 3/ Iterate with Insights → We release MVPs and refine them based on actual user behavior, not just feedback. This approach keeps us efficient and effective, focusing on solving one problem and adding REAL value. Have you already tried balancing user input and your vision? How did it go?

Re user/customer feedback: First, questionnaires don't seem to work very well. They typically ask the wrong questions, are too narrow in scope, and often have an implied bias. An actual conversation is better. Chatting while you watch a user/customer work is ideal, provided that you spend more time listening than talking, and you listen with an open mind instead of trying to manipulate your user to your way of thinking. That last bit is often subconscious and needs active attention. I often hear people try to turn whatever the user's saying into something that makes sense to a programmer but not to a user.