Understanding The Voice Of The Customer In Product Design

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 was a VP at Amazon from 2004 to 2014. In that time, every major new product innovation was built using the same exact process. 11 years later, they are still using that process for everything they build. Here’s how it works. The process is called Working Backwards. It flips the traditional invention approach by not starting with a company’s internal capabilities or current products. It starts instead with a clear definition of a customer problem. The goal is to write a press release describing a significant customer problem or need, how current solutions don’t solve the problem, and the new product user experience for a solution to the problem. This approach is “Backwards” because it starts with a press release (the last step in building a new product ). Most companies start building products by evaluating their existing technology or capabilities, or by looking at new trends, and then trying to build something customers will want. Amazon takes the opposite approach. Working Backwards starts with a deep understanding and concise definition of a customer problem before moving to potential solutions. After writing the Press Release, you add a list of frequently asked questions, or FAQs. The FAQs include the likely questions from customers and the press, as well as the typical questions the internal leaders ask about any new product idea, like "How big is the market?" and "How will we solve the technical challenges?" This document forces teams to clarify not only the customer problem they are solving, but also the ideal outcome from the customer’s perspective. This is all done before a single line of code is written or a prototype is built. To do this, teams frame the problem statement, the customer behaviors, and existing alternative solutions. Then, they describe the ideal customer experience, outlining how the product would solve the problem meaningfully. Finally, they anticipate key challenges (legal, technical, competitive, or operational) and document how they will address them. The key here is this: If the problem statement is weak, unclear, or does not represent a significant customer need (with a large TAM), then moving forward with development is a waste of time and money. While working backwards, teams iterate on the problem definition until it is strong and clear, or they move on to a different idea. Amazon has used this process to build many multi-billion dollar businesses, and it remains a core part of their innovation strategy. By working backwards, Amazon ensures that the products they build have a clear reason to exist before any resources are spent. Follow for more insights about building inside Amazon.

"Talk to customers" is classic startup advice. But not enough folks teach you how to talk to users in a way that gets you actual insights. Since launching Decagon and raising $100M over 3 rounds, we’ve learned a lot, especially about GTM. Here's how we've adapted our customer conversations to go beyond surface-level excitement and uncover real signals of value. We benchmark around dollars when discussing product features. Why? Because it’s easy to run a customer interview where the customer seems thrilled about a new idea we have. But excitement alone doesn’t tell you if a piece of feedback is truly valuable. The only way to find out is to ask the hard questions: → Is this something your team would invest in right now? → How much would you pay for it? → What’s the ROI you’d expect? Questions like these don’t allow for generic answers—they'll give you real clarity into a customer's willingness to pay. For example: say you float a product idea past a potential user. They're stoked by it. Then you ask how much they'd pay for said product—and the answer is $50 per person for a 3-person team. Is that worth building? It might be, depending on the outcome you're shooting for. But if your goal is to build an enterprise-grade product, that buying intent (or lack thereof) isn't going to cut it. If you'd stopped the interview at the surface-level excitement, you might have sent yourself on a journey building a product that isn't viable. By assessing true willingness to pay you can prioritize building what users find valuable versus what might sound good in theory. Get to the dollars as quickly as you can. It’s an approach that has helped us align our roadmap with what customers truly need and ensure we’re building a product that has a measurable impact.

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

We surveyed 1,244 product teams over the last 6 months and uncovered a reality that blew our minds: While all product teams are trying to create products that better satisfy customer needs, over 80% of product teams do not agree on what a customer "need" even is! Teams define "needs" as exciters and delight-ers, pains and gains, specifications and requirements, features, value drivers, wants and benefits, wishes, aspirations... ...and the list goes on, as if any of these inputs will correctly inform the innovation process. Here's the problem: THEY DON'T! Just like any process, only precise inputs lead to a great result. So what is the right input? We know that people buy products and services to get a "job" done. So, let's start by defining customer "needs" as the metrics customers use to measure success when getting a job done. If we know how customers measure success, we can create solutions that help them get their jobs done better--and win in the marketplace. These metrics, which we call the customer's desired outcomes, are tied to the customer's job-to-be-done and are unique in many ways. They are: - measurable and controllable, - actionable, - unambiguous, - solution independent and, - stable over time. When listening to music, for example, a music enthusiast may want to: “minimize the time it takes to get the songs in the desired order for listening.” This is one of many outcomes associated with the job of listening to music. Using these customer inputs as customer need statements, you're able to: 1. Understand how your customer measures success. 2. Measure how well your solutions get the job done. 3. Give your team clear instructions on how to improve your solutions. Watch your team transform when they're aligned with the metrics your customers use to measure success. #CustomerNeeds #InnovationProcess

𝗧𝗵𝗲 𝘁𝗿𝘂𝘁𝗵 𝗮𝗯𝗼𝘂𝘁 𝗩𝗼𝗶𝗰𝗲 𝗼𝗳 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿? It’s broken. Not because customers stopped speaking, but because brands stopped listening like it mattered. Surveys. Scores. Dashboards. 𝗧𝗵𝗮𝘁’𝘀 𝗻𝗼𝘁 𝗹𝗶𝘀𝘁𝗲𝗻𝗶𝗻𝗴. That’s forced interaction. The modern customer isn’t waiting to be surveyed. They’re 𝘭𝘦𝘢𝘷𝘪𝘯𝘨 𝘴𝘪𝘨𝘯𝘢𝘭𝘴 𝘦𝘷𝘦𝘳𝘺𝘸𝘩𝘦𝘳𝘦 - in chats, returns, reviews, support tickets, SMS threads, order cancellations, product reconfigurations, social media, dark social (Reddit, Discord, etc) But most “VoC programs” are still stuck chasing NPS trends while the business burns. Modern Voice of Customer = 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝗦𝗶𝗴𝗻𝗮𝗹 𝗜𝗻𝘁𝗲𝗹𝗹𝗶𝗴𝗲𝗻𝗰𝗲 It’s not about asking questions. It’s about 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝗶𝗻𝗴 𝗮 𝘀𝘆𝘀𝘁𝗲𝗺 that 𝘢𝘣𝘴𝘰𝘳𝘣𝘴 𝘴𝘪𝘨𝘯𝘢𝘭, connects it to business outcomes, and triggers action. What You Should Be Measuring Instead: ✅ % 𝗔𝗰𝘁𝗶𝗼𝗻𝗮𝗯𝗹𝗲 𝗦𝗶𝗴𝗻𝗮𝗹𝘀 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝗶𝗲𝗱 - How much of your incoming feedback actually maps to a real friction point, journey stage, or operational failure? ✅ % 𝗦𝗶𝗴𝗻𝗮𝗹𝘀 𝗧𝗶𝗲𝗱 𝘁𝗼 𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗜𝗺𝗽𝗮𝗰𝘁 - How many of those signals correlate with churn, CLV drop, conversion loss, or increased cost-to-serve? ✅ 𝗖𝗼𝗻𝘁𝗲𝘅𝘁𝘂𝗮𝗹 𝗦𝗲𝗻𝘁𝗶𝗺𝗲𝗻𝘁 (𝗡𝗼𝘁 𝗝𝘂𝘀𝘁 𝗮 𝗦𝗰𝗼𝗿𝗲) - Not “61% negative.” But: “61% 𝘯𝘦𝘨𝘢𝘵𝘪𝘷𝘦 𝘴𝘦𝘯𝘵𝘪𝘮𝘦𝘯𝘵 𝘢𝘳𝘰𝘶𝘯𝘥 𝘥𝘦𝘭𝘪𝘷𝘦𝘳𝘺 𝘴𝘱𝘦𝘦𝘥 𝘵𝘳𝘢𝘯𝘴𝘱𝘢𝘳𝘦𝘯𝘤𝘺.” “78% 𝘱𝘰𝘴𝘪𝘵𝘪𝘷𝘦 𝘴𝘦𝘯𝘵𝘪𝘮𝘦𝘯𝘵 𝘰𝘯 𝘱𝘰𝘴𝘵-𝘱𝘶𝘳𝘤𝘩𝘢𝘴𝘦 𝘴𝘶𝘱𝘱𝘰𝘳𝘵.” That tells a story. That’s signal intelligence. ✅ 𝗦𝗶𝗴𝗻𝗮𝗹 𝗩𝗲𝗹𝗼𝗰𝗶𝘁𝘆 - What’s emerging fast? What’s fading out? Velocity = your 𝘦𝘢𝘳𝘭𝘺 𝘸𝘢𝘳𝘯𝘪𝘯𝘨 𝘳𝘢𝘥𝘢𝘳. ✅ 𝗙𝗿𝗶𝗰𝘁𝗶𝗼𝗻 𝗙𝗮𝘁𝗶𝗴𝘂𝗲 𝗦𝗰𝗼𝗿𝗲 How often is the same friction mentioned with no resolution? High friction fatigue = 𝗹𝗼𝘀𝘁 𝘁𝗿𝘂𝘀𝘁. Your brand becomes a broken record and customers stop playing. CX isn't a function of feedback. It’s a function of 𝘀𝗶𝗴𝗻𝗮𝗹 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲. You don’t need another dashboard. You need a listening architecture that fuels performance. That’s Experience Signal Intelligence. #UnfckYourCX #ExperiencePerformanceSystem  #ExperienceDesign #SignalIntelligence #CLV #VoC #NPS #surveys

Track customer UX metrics during design to improve business results. Relying only on analytics to guide your design decisions is a missed opportunity to truly understand your customers. Analytics only show what customers did, not why they did it. Tracking customer interactions throughout the product lifecycle helps businesses measure and understand how customers engage with their products before and after launch. The goal is to ensure the design meets customer needs and achieves desired outcomes before building. By dividing the process into three key stages—customer understanding (attitudinal metrics), customer behavior (behavioral metrics), and customer activity (performance metrics)—you get a clearer picture of customer needs and how your design addresses them. → Customer Understanding In the pre-market phase, gathering insights about how well customers get your product’s value guides your design decisions. Attitudinal metrics collected through surveys or interviews help gauge preferences, needs, and expectations. The goal is to understand how potential customers feel about the product concept. → Customer Behavior Tracking how customers interact with prototype screens or products shows whether the design is effective. Behavioral metrics like click-through rates and session times provide insights into how users engage with the design. This phase bridges the pre-market and post-market stages and helps identify any friction points in the design. →  Customer Activity After launch, post-market performance metrics like task completion and error rates measure how customers use the product in real-world scenarios. These insights help determine if the product meets its goals and how well it supports user needs. Designers should take a data-informed approach by collecting and analyzing data at each stage to make sure the product continues evolving to meet customer needs and business goals. #productdesign #productdiscovery #userresearch #uxresearch

Are you generating enough value for users net of the value to your company? Business value can only be created when you create so much value for users, that you can “tax” that value and take some for yourself as a business. If you don’t create any value for your users, then you can’t create value for your business. Ed Biden explains how to solve this in this week's guest post: Whilst there are many ways to understand what your users will value, two techniques in particular are incredibly valuable, especially if you’re working on a tight timeframe: 1. Jobs To Be Done 2. Customer Journey Mapping 𝟭. 𝗝𝗼𝗯𝘀 𝗧𝗼 𝗕𝗲 𝗗𝗼𝗻𝗲 (𝗝𝗧𝗕𝗗) “People don’t simply buy products or services, they ‘hire’ them to make progress in specific circumstances.”  – Clayton Christensen The core JTBD concept is that rather than buying a product for its features, customers “hire” a product to get a job done for them … and will ”fire” it for a better solution just as quickly. In practice, JTBD provides a series of lenses for understanding what your customers want, what progress looks like, and what they’ll pay for. This is a powerful way of understanding your users, because their needs are stable and it forces you to think from a user-centric point of view. This allows you to think about more radical solutions, and really focus on where you’re creating value. To use Jobs To Be Done to understand your customers, think through five key steps: 1. Use case – what is the outcome that people want? 2. Alternatives – what solutions are people using now? 3. Progress – where are people blocked? What does a better solution look like? 4. Value Proposition – why would they use your product over the alternatives? 5. Price – what would a customer pay for progress against this problem? 𝟮. 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗝𝗼𝘂𝗿𝗻𝗲𝘆 𝗠𝗮𝗽𝗽𝗶𝗻𝗴 Customer journey mapping is an effective way to visualize your customer’s experience as they try to reach one of their goals. In basic terms, a customer journey map breaks the user journey down into steps, and then for each step describes what touchpoints the customer has with your product, and how this makes them feel. The touch points are any interaction that the customer has with your company as they go through this flow: • Website and app screens • Notifications and emails • Customer service calls • Account management / sales touch points • Physically interacting with goods (e.g. Amazon), services (e.g. Airbnb) or hardware (e.g. Lime) Users’ feelings can be visualized by noting down: • What they like or feel good about at this step • What they dislike, find frustrating or confusing at this step • How they feel overall By mapping the customer’s subjective experience to the nuts and bolts of what’s going on, and then laying this out in a visual way, you can easily see where you can have the most impact, and align stakeholders on the critical problems to solve.