Customer-Centric Design Principles For Innovators

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

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

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

Friday honesty: Customer-centricity is a lot harder to maintain than it seems. Even for those of us in Customer Success. The tendency is always to drift toward making our processes and focus company-centric rather than customer-centric. Don't believe me? Just look at one example of this: Customer Journeys. Many teams say that they have a defined Customer Journey. But rather than actually being oriented around the customer, for many the journey map is a list of activities from the company's perspective that are built around milestones the company cares about (contract signature, go-live, renewal, etc). I know about this, because I've been guilty of it in the past myself. I confuse my activity list with a customer journey and wonder why customers aren't as successful as they'd like. While important, that isn't a customer journey. It's an activity list. It's a rut none of us mean to fall into, but it's the natural drift because we live and breathe our own organization. So what do you do about it? How can you adopt a more customer-centric mindset in this area? TRY THIS APPROACH INSTEAD: 1. List out the stages your customers' business goes through at each phase of their experience with your product. Use these to categorize journey stage, rather than your contract lifecycle. 2. For each stage, list out what their experiences, expectations, and activities should be to get the results they want. Don't focus on listing what YOU do, but rather focus on listing what a customer does at each phase of their business with your product. List out the challenges they'd face, the business benefits they'd experience, the change management they'd have to go through, the usage they'd expect. Think bigger than your product here. 3. Then map what support a customer would need to actually accomplish these desired outcomes at each stage of the journey. Think education, change management enablement, training, etc. 4. Based on all of the above, you're finally ready to start identifying what your teams do to support the customer. ____________________________________________ Following a process like this helps build customer-centricity in 3 ways: 1. It causes customers to be the center of how you decide which activities are most important to focus on. 2. It empowers your team to become prescriptive about what customers should be doing for THEIR success. 3. It exposes what you don't know about your customers' business. And if you don't know something, just ask them. Don't make assumptions when you can instead talk to your customers directly. Avoid the company-centric drift, fight to maintain true customer-centricity however you can. This isn't just a nice to have in 2024. It's a business imperative that's important for any business to survive in this climate. But I want to hear from you! How do you guard your org from drifting to company-centricity? #SaaS #CustomerSuccess #Leadership #CustomerCentric

Outcome Driven Design is the essence of Amazon’s working backwards process. Outcome-driven design (ODD) is a user-centric approach that prioritizes the desired results and impact of a product or service over its features and specifications. By focusing on the outcomes that users aim to achieve, ODD ensures that design decisions are guided by real user needs and expectations. Ultimately, ODD aims to create solutions that deliver tangible business benefits, improve user satisfaction, and drive overall long term success by aligning the product’s objectives with the end user’s desired outcomes. To maintain our focus on customers problems and desired business outcomes, we ask ourselves different set of questions. What problems are we solving for customers? This question keeps us focused on understanding customer problems and working backwards from them to drive design decisions. We call them controllable inputs. By clearly defining the problems, designers can prioritize efforts on the most critical issues that impact user satisfaction and performance. This helps in aligning design goals with the actual pain points and challenges experienced by users, leading to solutions that are more relevant and valuable. Why these problems? This question clarifies how much we know about customers and their problems. It ensures that the problems being addressed are not only significant but also strategically important. It validates the relevance of the design focus and ensures that resources are allocated to issues that will have the most substantial impact on user outcomes. It also helps in uncovering the underlying causes of the problems, which can inform more effective and innovative solutions. What are our metrics? Metrics provide a way to quantify the benefits and improvements resulting from the design. They help in tracking progress, evaluating effectiveness, and making data-driven decisions. By setting specific, measurable goals, designers can ensure that their efforts lead to tangible results that enhance user satisfaction and achieve the intended outcomes. How high is the bar? This question encourages designers to strive for excellence and push the boundaries of what is possible. It ensures that the design not only meets basic user needs but also exceeds expectations, delivering exceptional value and experience. High standards drive innovation and continuous improvement, leading to solutions that stand out in the market and provide significant advantages to users. Setting the bar high establishes ambitious goals and standards for the design process. So next time when someone asks: “What are you working on?”, try using these questions to frame your response. Amazon Design Amazon Web Services (AWS) #design #usercentereddesign #workingbackwards PC: Adobe Stock