Using Customer Insights To Reduce Product Failures

While it can be easily believed that customers are the ultimate experts about their own needs, there are ways to gain insights and knowledge that customers may not be aware of or able to articulate directly. While customers are the ultimate source of truth about their needs, product managers can complement this knowledge by employing a combination of research, data analysis, and empathetic understanding to gain a more comprehensive understanding of customer needs and expectations. The goal is not to know more than customers but to use various tools and methods to gain insights that can lead to building better products and delivering exceptional user experiences. ➡️ User Research: Conducting thorough user research, such as interviews, surveys, and observational studies, can reveal underlying needs and pain points that customers may not have fully recognized or articulated. By learning from many users, we gain holistic insights and deeper insights into their motivations and behaviors. ➡️ Data Analysis: Analyzing user data, including behavioral data and usage patterns, can provide valuable insights into customer preferences and pain points. By identifying trends and patterns in the data, product managers can make informed decisions about what features or improvements are most likely to address customer needs effectively. ➡️ Contextual Inquiry: Observing customers in their real-life environment while using the product can uncover valuable insights into their needs and challenges. Contextual inquiry helps product managers understand the context in which customers use the product and how it fits into their daily lives. ➡️ Competitor Analysis: By studying competitors and their products, product managers can identify gaps in the market and potential unmet needs that customers may not even be aware of. Understanding what competitors offer can inspire product improvements and innovation. ➡️ Surfacing Implicit Needs: Sometimes, customers may not be able to express their needs explicitly, but through careful analysis and empathetic understanding, product managers can infer these implicit needs. This requires the ability to interpret feedback, observe behaviors, and understand the context in which customers use the product. ➡️ Iterative Prototyping and Testing: Continuously iterating and testing product prototypes with users allows product managers to gather feedback and refine the product based on real-world usage. Through this iterative process, product managers can uncover deeper customer needs and iteratively improve the product to meet those needs effectively. ➡️ Expertise in the Domain: Product managers, industry thought leaders, academic researchers, and others with deep domain knowledge and expertise can anticipate customer needs based on industry trends, best practices, and a comprehensive understanding of the market. #productinnovation #discovery #productmanagement #productleadership

I’m not asking my CSMs to resolve support tickets. I’m asking them to leverage them. Support tickets aren’t just a backlog of problems; they’re customer truth bombs waiting to explode. If you’re not mining them for insights, you’re flying blind—and that’s exactly how churn sneaks up on you. Every Customer Success team I’ve ever led has been trained to use Support tickets strategically. Why? Because they’re packed with insights that make us better at our jobs. ✅ We learn more about the product. ✅ We spot trends before they become problems. ✅ We understand our customers’ use cases more deeply. If you’re not tapping into support data, here’s what you’re missing: 🔥 Emerging Pain Points Recurring issues expose friction in the customer journey. Ignore them, and those minor frustrations turn into churn-worthy headaches. 🔥 Product Gaps Customers vote with their tickets. If the same feature requests or usability complaints keep surfacing, your roadmap is practically writing itself. 🔥 Engagement Risks A spike in tickets isn’t just noise—it’s a flare. Users don’t submit tickets when they’re thriving; they do it when they’re stuck, frustrated, or in need of more enablement. Here are a few ways my team and I are using these insights: ✅ Spot & Engage Struggling Users A surge in ticket volume? Proactively reach out before frustration turns into a cancellation. ✅ Create Targeted Content If the same questions keep coming up, turn those insights into help docs, webinars, or office hours. ✅ Surface Expansion Opportunities Seeing frequent feature requests? Build them—or better yet, use them to tee up expansion conversations. ✅ Map Out User Behavior Support tickets tell you who’s onboarding, who’s adopting new features, and who’s stuck. Use that data to drive deeper engagement. ✅ Collaborate with Product Your product team needs this intel. Share support trends regularly to influence meaningful fixes and features. High ticket volume isn’t necessarily a bad thing—but you need to know how to use it to your advantage. Bottom line? CSMs don’t need to fix support tickets. But the best ones know how to use them to drive retention, expansion, and adoption. _____________________________ 📣 If you liked my post, you’ll love my newsletter. Every week I share learnings, advice and strategies from my experience going from CSM to CCO. Join 12k+ subscribers of The Journey and turn insights into action. Sign up on my profile.

Your Product Managers are talking to customers. So why isn’t your product getting better? A few years ago, I was on a team where our boss had a rule: 🗣️ “Everyone must talk to at least one customer each week.” So we did. Calls were scheduled. Conversations happened. Boxes were checked. But nothing changed. No real insights. No real impact. Because talking to customers isn’t the goal. Learning the right things is. When discovery lacks purpose, it leads to wasted effort, misaligned strategy, and poor business decisions: ❌ Features get built that no one actually needs. ❌ Roadmaps get shaped by the loudest voices, not the right customers. ❌ Teams collect insights… but fail to act on them. How Do You Fix It? ✅ Talk to the Right People Not every customer insight is useful. Prioritize: -> Decision-makers AND end-users – You need both perspectives. -> Customers who represent your core market – Not just the loudest complainers. -> Direct conversations – Avoid proxy insights that create blind spots. 👉 Actionable Step: Before each interview, ask: “Is this customer representative of the next 100 we want to win?” If not, rethink who you’re talking to. ✅ Ask the Right Questions A great question challenges assumptions. A bad one reinforces them. -> Stop asking: “Would you use this?” -> Start asking: “How do you solve this today?” -> Show AI prototypes and iterate in real-time – Faster than long discovery cycles. -> If shipping something is faster than researching it—just build it. 👉 Actionable Step: Replace one of your upcoming interview questions with: “What workarounds have you created to solve this problem?” This reveals real pain points. ✅ Don’t Let Insights Die in a Doc Discovery isn’t about collecting insights. It’s about acting on them. -> Validate across multiple customers before making decisions. -> Share findings with your team—don’t keep them locked in Notion. -> Close the loop—show customers how their feedback shaped the product. 👉 Actionable Step: Every two weeks, review customer insights with your team to decipher key patterns and identify what changes should be applied. If there’s no clear action, you’re just collecting data—not driving change. Final Thought Great discovery doesn’t just inform product decisions—it shapes business strategy. Done right, it helps teams build what matters, align with real customer needs, and drive meaningful outcomes. 👉 Be honest—are your customer conversations actually making a difference? If not, what’s missing? -- 👋 I'm Ron Yang, a product leader and advisor. Follow me for insights on product leadership + strategy.

Building a product isn’t just about solving a problem - it’s about ensuring you solve the right problem, in a way that resonates with your users. Yet, so many products miss the mark, often because the feedback from the people who matter most - users - isn’t prioritized. The key to a great product lies in its alignment with real user needs. Ignoring feedback can lead to building features that no one uses or overlooking pain points that drive users away. In fact, 42% of startups fail because their products don’t address a genuine market need ( source: CB Insights). Starting with a Minimal Desirable Product (MDP) can help. This isn’t about launching the simplest version of your idea, but about delivering something functional that still brings delight - encouraging users to engage and share their insights. How to Integrate Feedback Effectively - Observe User Behavior: Watch how users interact with your product. Are there steps where they hesitate or struggle? Their actions often tell you more than their words. - Ask the Right Questions: Use surveys and interviews to go beyond surface-level feedback. Open-ended questions can reveal frustrations or desires you hadn’t anticipated. - Iterate, Don’t Hesitate: Apply feedback to refine your product. Prioritize changes that align with user needs and eliminate features that don’t serve a purpose. - Keep Listening: The market evolves, and so do user preferences. Regularly revisiting feedback ensures your product stays relevant. The Hidden Cost of Ignoring Feedback A study from Harvard Business Review shows that 35% of product features are never used, and 19% are rarely used. That’s not just a waste of resources - it’s a missed opportunity to deliver real value. Let’s be honest: integrating feedback is hard work. It’s not a one-time task but an ongoing commitment. Negative feedback can be tough to hear, but it’s often where the biggest opportunities for improvement lie. Great products are never built in isolation. How do you incorporate user feedback into your product journey? #innovation #technology #future #management #startups