Search Results

By Philip Burgess | UX Research Leader User experience (UX) research plays a crucial role in designing products that meet user needs and expectations. However, without clear metrics, it’s difficult to measure success or identify areas for improvement. Choosing the right UX metrics ensures your research plan delivers actionable insights that guide design decisions. This post highlights the essential UX metrics every research plan should include to provide a clear picture of user satisfaction, usability, and engagement. UX research dashboard showing key metrics Why UX Metrics Matter UX metrics quantify how users interact with a product. They help teams understand whether users find a product easy to use, enjoyable, and effective in meeting their goals. Without these measurements, teams rely on guesswork or anecdotal feedback, which can lead to misguided design choices. Good UX metrics provide: Objective data to support design decisions Clear indicators of user satisfaction and pain points Benchmarks to track improvements over time Evidence to justify investments in UX improvements Usability Metrics to Track Usability is the foundation of a good user experience. These metrics focus on how easily users can complete tasks. Task Success Rate This metric measures the percentage of users who complete a specific task successfully. For example, if 80 out of 100 users complete a checkout process without errors, the task success rate is 80%. Why it matters: It directly reflects how well users can achieve their goals. Low success rates indicate usability problems that need fixing. Time on Task This tracks how long users take to complete a task. Shorter times usually mean the task is straightforward, while longer times may signal confusion or complexity. Example: If users take an average of 3 minutes to find product information, but the goal is under 1 minute, the design needs simplification. Error Rate This counts the number of mistakes users make during a task, such as clicking the wrong button or entering invalid data. Use case: A high error rate during form submission suggests the form design or instructions are unclear. User Satisfaction Metrics Understanding how users feel about a product is just as important as measuring their behavior. System Usability Scale (SUS) SUS is a simple questionnaire that asks users to rate usability on a scale from 0 to 100. Scores above 68 are considered above average. Benefit: It provides a quick, standardized way to gauge overall usability. Net Promoter Score (NPS) NPS measures user loyalty by asking how likely users are to recommend the product to others on a scale from 0 to 10. Scores are categorized into promoters, passives, and detractors. Insight: A high NPS indicates strong user satisfaction and potential for organic growth. Customer Satisfaction Score (CSAT) CSAT asks users to rate their satisfaction with a specific interaction or feature, usually on a 1 to 5 scale. Example: After completing a purchase, users might rate their satisfaction with the checkout process. Engagement Metrics to Include Engagement metrics reveal how users interact with the product over time. User Retention Rate This measures the percentage of users who return to the product after their first visit. High retention suggests the product provides ongoing value. Example: A mobile app with a 30-day retention rate of 40% is performing well compared to industry averages. Session Length Session length tracks how much time users spend during each visit. Longer sessions can indicate deeper engagement, but very long sessions might also mean users struggle to find what they need. Feature Usage Tracking which features users interact with helps identify what parts of the product are most valuable or underused. Use case: If a new search feature has low usage, it might need better promotion or redesign. UX researcher reviewing heatmaps to understand user behavior How to Choose the Right Metrics Not every metric fits every project. Select metrics based on your research goals and product context. Define clear objectives: Are you testing usability, satisfaction, or engagement? Consider the product type: Metrics for a mobile app differ from those for a website or software tool. Balance quantitative and qualitative data: Combine metrics with user interviews or observations for richer insights. Set benchmarks: Use industry standards or past data to evaluate results. Putting Metrics to Work Collecting data is only useful if you act on it. Use UX metrics to: Identify usability issues and prioritize fixes Track improvements after design changes Communicate findings to stakeholders with clear evidence Guide future research questions and product development For example, if task success rate is low on a checkout page, redesign the flow and test again. If NPS drops after a new release, investigate what caused dissatisfaction.

By Philip Burgess | UX Research Leader Measuring success and customer satisfaction often involves looking at different types of data. Two common categories are behavioral and attitudinal metrics. While they both provide valuable insights, they focus on different aspects of customer experience and decision-making. Understanding the difference between these metrics helps businesses and researchers make better decisions, improve products, and tailor services more effectively. Person reviewing behavioral and attitudinal data charts What Are Behavioral Metrics? Behavioral metrics track what people actually do. These metrics are based on observable actions and measurable events. Examples include: Number of website visits Purchase frequency Time spent on a page Click-through rates Product usage patterns Behavioral data is objective because it records real actions without relying on what people say or think. For example, if a customer buys a product three times in a month, that purchase history is a behavioral metric. Why Behavioral Metrics Matter Behavioral metrics reveal how customers interact with a product or service in real life. They help identify patterns and trends that might not be obvious from surveys or interviews. For instance, a company might notice that users spend less time on a particular feature, indicating it may be confusing or less useful. These metrics are essential for: Tracking performance over time Identifying bottlenecks or drop-off points Measuring the effectiveness of marketing campaigns Improving user experience based on actual usage What Are Attitudinal Metrics? Attitudinal metrics focus on what people think, feel, or believe. These metrics come from surveys, interviews, feedback forms, and other methods that capture opinions and perceptions. Examples include: Customer satisfaction scores Net Promoter Score (NPS) Brand perception Product preference Emotional response to a service Attitudinal data is subjective because it reflects personal feelings and opinions rather than observable actions. Why Attitudinal Metrics Matter Attitudinal metrics provide insight into customer motivations and preferences. They help explain why people behave a certain way. For example, a customer might stop using a product not because it is faulty but because they feel it does not meet their needs or values. These metrics are useful for: Understanding customer loyalty and advocacy Gauging brand reputation Identifying unmet needs or desires Improving communication and messaging Key Differences Between Behavioral and Attitudinal Metrics | Aspect | Behavioral Metrics | Attitudinal Metrics | |----------------------|-------------------------------------|------------------------------------| | Data Type | Objective, based on actions | Subjective, based on opinions | | Collection Method | Tracking tools, analytics, logs | Surveys, interviews, feedback | | Focus | What customers do | What customers think or feel | | Examples | Purchase history, click rates | Satisfaction scores, brand loyalty | | Use Cases | Performance measurement, UX design | Customer insights, brand strategy | How to Use Both Metrics Together Relying on only one type of metric can give an incomplete picture. Combining behavioral and attitudinal data provides a fuller understanding of customer experience. For example, a company might see from behavioral data that users abandon their shopping carts frequently. Attitudinal data collected through surveys might reveal that customers find the checkout process confusing or too long. Together, these insights guide improvements that address both the action and the reason behind it. Practical Steps to Combine Metrics Collect behavioral data through analytics platforms and tracking software. Gather attitudinal data using surveys or interviews at key customer touchpoints. Compare trends in behavior with customer feedback to identify gaps. Use attitudinal insights to interpret behavioral patterns. Test changes and measure impact using both types of data. Notebook with notes on behavioral and attitudinal metrics comparison Examples of Behavioral and Attitudinal Metrics in Action E-commerce Website Behavioral: Track how many visitors add items to their cart but do not complete the purchase. Attitudinal: Survey customers about their satisfaction with the checkout process and reasons for abandoning carts. Mobile App Behavioral: Measure daily active users and feature usage frequency. Attitudinal: Collect user feedback on app design, ease of use, and overall satisfaction. Customer Support Behavioral: Count the number of support tickets resolved within a certain time. Attitudinal: Ask customers to rate their support experience and provide comments. Final Thoughts on Behavioral and Attitudinal Metrics Both behavioral and attitudinal metrics offer valuable insights but from different angles. Behavioral data shows what customers do, while attitudinal data reveals why they do it. Using both together helps create a clearer, more actionable understanding of customer needs and experiences.

By Philip Burgess | UX Research Leader Measuring user experience (UX) is essential to creating products that truly satisfy users. But with so many metrics available, choosing the right ones can feel overwhelming. Picking the wrong metrics wastes time and resources, while the right ones provide clear insights that guide design decisions and improve the product. This post explains how to select UX metrics that fit your product’s goals and user needs. Dashboard displaying UX metrics for a digital product Understand Your Product Goals and User Needs Start by clarifying what your product aims to achieve and who your users are. UX metrics should align with these goals. For example, if your product focuses on e-commerce, metrics related to purchase flow and checkout ease matter most. If it’s a content platform, engagement and content discovery metrics take priority. Ask yourself: What user problems does the product solve? What behaviors indicate success for users? What business outcomes depend on user experience? Knowing this helps you avoid generic metrics that don’t reveal meaningful insights. Instead, focus on metrics that reflect real user value and business impact. Different Types of UX Metrics to Consider UX metrics fall into several categories. Each type offers different insights, so combining a few can give a fuller picture. Behavioral Metrics These track what users do within your product. Examples include: Task success rate: Percentage of users who complete a task. Time on task: How long it takes users to finish a task. Error rate: Frequency of mistakes during tasks. Behavioral metrics show how easily users navigate your product and where they struggle. Attitudinal Metrics These capture user feelings and satisfaction. Common attitudinal metrics are: Net Promoter Score (NPS): Likelihood users recommend your product. Customer Satisfaction (CSAT): How happy users are with specific features. System Usability Scale (SUS): Standardized questionnaire measuring usability. Attitudinal data reveals how users perceive your product, which can differ from observed behavior. Engagement Metrics Engagement metrics measure how users interact over time, such as: Session length: Average time spent per visit. Frequency of use: How often users return. Feature adoption rate: Percentage using new features. These metrics help track user retention and product stickiness. Qualitative Feedback Though not numeric, qualitative feedback from interviews, surveys, or usability tests provides context to metrics. It explains why users behave a certain way or feel a certain emotion. Match Metrics to Your Product Stage Your product’s development phase influences which metrics matter most. Early stage : Focus on usability and task success to identify major pain points. Growth stage : Track engagement and retention to build a loyal user base. Mature stage : Measure satisfaction and NPS to maintain and improve user loyalty. For example, a startup launching a new app might prioritize task completion rates and error rates to fix usability issues. An established app might focus on NPS and feature adoption to refine the experience. Use Metrics That Are Actionable and Measurable Choose metrics that you can measure reliably and that lead to clear actions. Avoid vanity metrics that look good but don’t influence decisions. For instance, total page views might be high but don’t tell you if users complete key tasks. Instead, track task success rate or conversion rate, which directly relate to user goals. Combine Quantitative and Qualitative Data Numbers alone don’t tell the full story. Combine quantitative metrics with qualitative insights to understand user motivations and frustrations. For example, if task success rate drops, follow up with user interviews to find out why. This approach leads to targeted improvements rather than guesswork. UX researcher’s notebook with handwritten notes and wireframe sketches Regularly Review and Adjust Your Metrics UX is dynamic. As your product evolves, so should your metrics. Regularly review whether your current metrics still align with goals and user needs. Set a schedule to analyze data, discuss findings with your team, and adjust metrics if needed. This keeps your measurement relevant and focused on continuous improvement. Practical Example: Choosing Metrics for a Mobile Banking App Imagine you manage a mobile banking app. Your main goals are secure transactions and easy account management. Behavioral metrics: Track task success rate for money transfers and bill payments. Attitudinal metrics: Use CSAT surveys after transactions to measure satisfaction. Engagement metrics: Monitor frequency of app logins and feature use like budgeting tools. Qualitative feedback: Conduct interviews to understand pain points in security features. This mix helps you spot usability issues, measure satisfaction, and see if users adopt new features, guiding product improvements effectively.

By Philip Burgess | UX Research Leader Measuring success in user experience (UX) research depends heavily on choosing the right key performance indicators (KPIs). Without clear, meaningful KPIs, teams risk focusing on irrelevant data or missing critical insights that drive product improvements. But what exactly makes a KPI good for UX research? This post breaks down the essential qualities and offers a practical checklist to help UX researchers select KPIs that truly matter. A UX researcher reviewing user data on a laptop screen Understand What a KPI Should Do A KPI is a measurable value that shows how effectively a team is achieving key objectives. In UX research, KPIs help track user satisfaction, usability, engagement, and overall experience quality. Good KPIs guide decision-making and highlight areas needing improvement. To be effective, a KPI must: Reflect a clear goal or outcome Be measurable with available data Provide actionable insights Align with business and user needs Checklist for Choosing Good UX KPIs 1. Tie KPIs to Specific UX Goals Start by defining what success looks like for your project or product. Common UX goals include improving task completion rates, reducing errors, increasing user satisfaction, or speeding up onboarding. Example: If your goal is to improve onboarding, a KPI could be the percentage of users who complete the onboarding process within the first session. 2. Ensure KPIs Are Quantifiable KPIs must be based on data you can collect reliably. Avoid vague or subjective measures that are hard to track consistently. Example: Instead of “users feel happy,” measure the Net Promoter Score (NPS) or System Usability Scale (SUS) score, which provide numeric values. 3. Focus on Actionable Metrics Choose KPIs that lead to clear actions. If a KPI shows a problem, your team should know what to do next. Example: A high drop-off rate on a checkout page signals a need to simplify the process or fix bugs. 4. Keep KPIs User-Centered KPIs should reflect the user’s experience, not just business metrics. While revenue and conversion rates matter, UX KPIs focus on how users interact with and perceive the product. Example: Track average time to complete a key task rather than just sales numbers. 5. Limit the Number of KPIs Too many KPIs dilute focus. Select a handful of meaningful indicators that cover different aspects of UX without overwhelming the team. Example: Use three to five KPIs such as task success rate, error rate, user satisfaction, and time on task. Close-up of a UX dashboard showing task success rate and user satisfaction metrics Examples of Effective UX KPIs Task Success Rate Measures the percentage of users who complete a task successfully. High success rates indicate good usability. Error Rate Tracks how often users make mistakes during tasks. A rising error rate signals usability issues. Time on Task Measures how long users take to complete a task. Shorter times usually mean the interface is intuitive. User Satisfaction Score Collected through surveys, this score reflects how users feel about their experience. Retention Rate Shows how many users return to the product over time, indicating ongoing value. Avoid Common Pitfalls Choosing vanity metrics that look good but don’t inform decisions, like total page views without context. Ignoring qualitative feedback that explains why KPIs change. Setting unrealistic targets that demotivate teams. Using KPIs that don’t align with user needs or product goals. How to Implement Your KPI Checklist Define your UX goals clearly. Write down what success means for your project. Identify available data sources. Check analytics tools, surveys, and usability tests. Select KPIs that fit your goals and data. Use the checklist above to evaluate each candidate. Set realistic benchmarks. Use past data or industry standards to set targets. Review KPIs regularly. Adjust as your product and user needs evolve.

By Philip Burgess | UX Research Leader User experience (UX) shapes how people interact with products and services. Measuring UX helps teams understand what works, what doesn’t, and where to improve. Without clear metrics, decisions rely on guesswork instead of data. This guide explains key UX metrics, why they matter, and how to use them to create better experiences. User interacting with touchscreen showing UX data charts Why UX Metrics Matter UX metrics provide measurable evidence of how users feel and behave when using a product. They help teams: Identify pain points and areas needing improvement Track progress over time after changes or updates Align design decisions with user needs and business goals Justify investments in UX improvements with data Without metrics, teams risk focusing on features that don’t improve satisfaction or usability. Metrics guide efforts toward what truly impacts user experience. Types of UX Metrics to Track UX metrics fall into three main categories: behavioral, attitudinal, and qualitative. Each offers unique insights. Behavioral Metrics These measure what users do, revealing how they interact with a product. Task Success Rate Percentage of users who complete a task successfully. For example, if 85 out of 100 users complete checkout without errors, the success rate is 85%. This metric shows usability and effectiveness. Time on Task How long users take to complete a task. Shorter times usually indicate easier, more efficient experiences. If users spend 5 minutes on a form that should take 2, it signals friction. Error Rate Frequency of mistakes users make during tasks. High error rates suggest confusing interfaces or unclear instructions. Click or Tap Counts Number of clicks or taps to complete a task. Fewer clicks often mean simpler navigation. Attitudinal Metrics These capture users’ feelings and opinions about the experience. System Usability Scale (SUS) A standardized questionnaire that scores usability on a scale from 0 to 100. Scores above 68 are considered above average. Net Promoter Score (NPS) Measures user loyalty by asking how likely they are to recommend the product on a scale from 0 to 10. Scores above 50 are excellent. Customer Satisfaction (CSAT) Direct rating of satisfaction, often on a 1 to 5 scale. It reflects immediate feelings after using a product or feature. Qualitative Metrics These provide deeper understanding through open-ended feedback. User Interviews Conversations that reveal motivations, frustrations, and suggestions. Usability Testing Observations Watching users interact with a product to identify issues not captured by numbers. Open-Ended Survey Responses Users describe their experience in their own words, offering rich insights. How to Choose the Right Metrics Not every metric fits every project. Choose based on goals and context. For improving task flow, focus on task success rate , time on task , and error rate . To measure overall satisfaction, use SUS , NPS , or CSAT . When exploring new features, combine quantitative metrics with qualitative feedback to understand why users behave a certain way. Set clear objectives before measuring. For example, if the goal is to reduce checkout abandonment, track task success and time on task specifically for the checkout process. Practical Examples of UX Metrics in Action An e-commerce site noticed a high cart abandonment rate. They measured task success and time on task during checkout. Results showed users struggled with a confusing payment form. After redesigning the form, task success rose from 70% to 90%, and average time dropped by 30 seconds. A mobile app used SUS surveys after each update. When scores dropped below 60, the team investigated and found a new feature caused confusion. They fixed the issue, and SUS scores returned to 75. A SaaS platform tracked NPS quarterly. When scores dipped, they conducted user interviews to uncover dissatisfaction with customer support. This led to training improvements and a 15-point NPS increase over six months. Laptop screen displaying UX metric dashboards with graphs and charts Best Practices for Using UX Metrics Combine Metrics Use both behavioral and attitudinal data for a full picture. Numbers show what happens, feedback explains why. Track Over Time Measure before and after changes to see real impact. Segment Users Analyze metrics by user groups, such as new vs. returning users, to uncover specific needs. Avoid Vanity Metrics Focus on metrics that influence decisions, not just numbers that look good. Communicate Clearly Share findings with teams using simple visuals and stories to drive action. Final Thoughts on UX Metrics Measuring UX is essential for building products that users enjoy and trust. The right metrics reveal where users struggle and what delights them. By tracking task success, satisfaction, and qualitative feedback, teams make informed decisions that improve experiences and business outcomes.

By Philip Burgess | UX Research Leader Emotions shape how people experience the world, make decisions, and interact with others. Measuring emotions like confidence, anxiety, and delight can reveal valuable insights for personal growth, mental health, and even product design. But emotions are complex and often invisible. How can we capture and quantify these feelings in a meaningful way? This post explores practical methods to measure emotional states, focusing on confidence, anxiety, and delight. You will learn about behavioral cues, physiological signals, and self-report tools that help track these emotions. Understanding emotional metrics can improve communication, boost well-being, and guide better choices. Understanding Emotional Metrics Emotional metrics refer to ways of quantifying feelings to better understand their intensity and impact. Unlike physical measurements, emotions are subjective and fluctuate quickly. Still, researchers and practitioners use various indicators to assess emotions reliably. Confidence reflects a person’s belief in their abilities or decisions. Anxiety involves feelings of worry, nervousness, or unease. Delight is a positive emotion marked by joy, pleasure, or satisfaction. Each emotion has unique signs that can be observed or measured. Combining different methods gives a fuller picture. Behavioral Signs to Watch One of the simplest ways to measure emotions is by observing behavior. People often express confidence, anxiety, and delight through body language, speech, and actions. Confidence Steady eye contact Upright posture Clear and calm speech Willingness to take risks or lead Anxiety Fidgeting or restless movements Avoiding eye contact Hesitant or shaky voice Repetitive behaviors like nail-biting Delight Smiling or laughter Relaxed body language Energetic gestures Positive verbal expressions For example, a speaker who maintains eye contact and speaks clearly likely feels confident. Someone pacing or avoiding interaction may be anxious. Watching these cues helps estimate emotional states without needing complex tools. Person showing confident body language while speaking Physiological Measurements Emotions trigger physical responses that can be measured with technology. These signals provide objective data about emotional intensity. Heart rate increases with anxiety and excitement. Skin conductance (sweat gland activity) rises during stress or delight. Breathing patterns change with calmness or nervousness. Facial muscle activity can indicate smiles or tension. Wearable devices like smartwatches and fitness trackers often include heart rate monitors. More advanced tools use sensors to detect skin conductance or facial expressions. For example, a study measuring heart rate variability found that people with higher confidence showed more stable heart rhythms during challenges. Anxiety caused spikes in skin conductance, while delight correlated with specific facial muscle movements. Self-Report and Questionnaires Asking people to describe their feelings remains one of the most direct ways to measure emotions. Self-report tools use scales and prompts to capture emotional states. Likert scales ask participants to rate their confidence or anxiety from low to high. Emotion diaries encourage daily logging of feelings and triggers. Standardized questionnaires like the State-Trait Anxiety Inventory (STAI) assess anxiety levels. These tools rely on honesty and self-awareness but provide valuable insights when combined with behavioral and physiological data. For example, a person might rate their confidence as 7 out of 10 before a presentation and 4 after, matching observed body language and heart rate changes. Person completing an emotional self-report questionnaire Practical Applications of Emotional Metrics Measuring emotions has many uses across different fields: Mental health professionals track anxiety levels to tailor therapy. Educators assess student confidence to improve learning. Product designers evaluate delight to enhance user experience. Leaders monitor team emotions to boost morale and performance. For example, a teacher noticing low confidence in students can introduce supportive activities. A mobile app might use sensors to detect user delight and adjust content accordingly. Tips for Measuring Emotions Effectively Use multiple methods for a complete view. Observe changes over time, not just single moments. Respect privacy and obtain consent when collecting data. Interpret results in context; emotions are influenced by many factors. Combine quantitative data with qualitative insights for depth. Tracking confidence, anxiety, and delight helps reveal hidden emotional patterns. By combining behavioral observation, physiological signals, and self-reports, you can measure these feelings with greater accuracy. This understanding supports better communication, personal growth, and improved experiences.

By Philip Burgess | UX Research Leader Trust shapes every digital interaction. Whether users feel confident sharing personal data, making purchases, or engaging with content depends largely on how much they trust the platform. But trust is intangible. How can businesses measure it effectively? Understanding the right metrics helps companies build stronger relationships with users and improve their digital experiences. Dashboard showing key trust metrics in a digital platform Why Measuring Trust Matters Trust influences user behavior and loyalty. When users trust a website or app, they are more likely to: Complete transactions Share personal information Return frequently Recommend the platform to others Without trust, users hesitate or abandon the experience. Measuring trust reveals how well a digital experience meets user expectations and highlights areas needing improvement. Key Metrics to Track Trust Several metrics provide insight into trust levels. These metrics combine quantitative data with user feedback to paint a clear picture. 1. User Satisfaction Scores User satisfaction surveys, such as Net Promoter Score (NPS) or Customer Satisfaction Score (CSAT), ask users directly about their experience. High satisfaction often correlates with trust. NPS measures the likelihood of users recommending the platform. CSAT captures immediate satisfaction after an interaction. For example, an e-commerce site with an NPS of 70 indicates strong user trust and loyalty. 2. Conversion Rates Conversion rates show how many users complete desired actions, such as signing up or purchasing. Low conversion despite high traffic may signal trust issues. For instance, if many users add items to a cart but abandon checkout, trust in payment security might be low. 3. Bounce Rate and Session Duration Bounce rate measures how many users leave after viewing one page. A high bounce rate can suggest users do not trust the site enough to explore further. Session duration indicates how long users stay engaged. Longer sessions often reflect comfort and trust in the content or service. 4. Security Incident Reports Tracking security incidents like data breaches or phishing attempts helps assess trust risks. Frequent incidents damage user confidence. Monitoring how quickly and transparently a company responds to security issues also affects trust. 5. User Feedback and Reviews Qualitative feedback from reviews, comments, and support tickets reveals trust-related concerns. Users often mention trust explicitly when reporting problems or praising features. Analyzing common themes helps prioritize improvements. Practical Examples of Measuring Trust Example 1: Financial Services App A financial app tracks NPS, conversion rates for loan applications, and security incident reports. After noticing a drop in loan completions, the team surveys users and finds concerns about data privacy. They improve encryption and update privacy policies, leading to a 15% increase in conversions and higher NPS. Example 2: Online Retailer An online retailer monitors bounce rates and session duration on product pages. High bounce rates on new product launches prompt usability testing. They discover confusing return policies reduce trust. Simplifying the policy and highlighting guarantees lowers bounce rates by 20%. Building Trust Through Metrics Measuring trust is not a one-time task. It requires continuous monitoring and action. Use these tips to build trust effectively: Set clear goals for trust metrics aligned with business objectives. Combine quantitative and qualitative data for a full picture. Respond quickly to security issues and user concerns. Communicate transparently about policies and changes. Test changes and track their impact on trust metrics. User entering credentials on a secure login interface Final Thoughts on Measuring Trust Trust drives user engagement and business success in digital experiences. By focusing on clear, actionable metrics like satisfaction scores, conversion rates, and security reports, companies can understand where trust stands and how to improve it. Regular measurement combined with user-centered improvements builds stronger, lasting connections.

By Philip Burgess | UX Research Leader When customers interact with a product or service, their experience often hinges on how easy it is to complete important tasks. The Customer Effort Score (CES) is a simple yet powerful metric designed to measure this ease. Unlike other customer satisfaction tools that focus on feelings or loyalty, CES zeroes in on the effort customers must put in to achieve their goals. Understanding and improving CES can lead to smoother experiences, higher retention, and stronger customer relationships. Customer navigating an online checkout process What Is Customer Effort Score? CES asks customers a straightforward question after a key interaction: How much effort did you personally have to put forth to handle your request? Customers respond on a scale, often from "Very low effort" to "Very high effort." The goal is to identify friction points where customers struggle. This metric focuses on key flows —the critical steps customers take to complete tasks such as making a purchase, resolving an issue, or signing up for a service. By measuring effort in these flows, companies can pinpoint where customers face obstacles and take action to simplify those steps. Why CES Matters More Than Other Metrics Traditional metrics like Net Promoter Score (NPS) or Customer Satisfaction (CSAT) measure overall feelings or likelihood to recommend. While useful, they don’t always reveal the root causes of frustration or ease. CES directly targets the customer's experience of effort, which research shows strongly correlates with loyalty. A study by the Corporate Executive Board found that 94% of customers who had low-effort experiences were likely to repurchase , compared to only 4% of customers who had high-effort experiences. This makes CES a predictive tool for customer retention and growth. How to Measure CES in Key Flows To get meaningful CES data, focus on these steps: Identify key flows : Map out the most important customer journeys, such as account creation, product purchase, or support resolution. Ask the CES question immediately after the flow : Timing is critical. Ask customers right after they complete or abandon a task. Use a simple scale : Typically a 5- or 7-point scale works best, with clear labels from low to high effort. Collect qualitative feedback : Alongside the score, ask customers to explain their rating in their own words. This reveals specific pain points. For example, an e-commerce site might ask after checkout: How much effort did you have to put into completing your purchase today? Customers who struggled with payment options or slow loading times will give higher effort scores. Examples of Improving CES in Practice Many companies have successfully used CES to improve customer experience: A telecom company noticed customers reported high effort when trying to change plans online. By simplifying the interface and reducing form fields, they lowered CES by 30%, leading to fewer calls to support. An online bank tracked CES during loan applications. They found customers struggled with document uploads. Introducing a mobile app feature to scan documents reduced effort and increased loan completions. A software provider used CES after onboarding new users. They identified confusing setup steps and created tutorial videos, which cut effort scores in half and boosted user retention. These examples show how CES highlights specific issues and guides targeted improvements. Dashboard displaying customer effort scores and comments Best Practices for Using CES Effectively To get the most from CES, keep these tips in mind: Focus on key flows, not every interaction : Measuring effort everywhere can overwhelm teams. Prioritize the most impactful journeys. Combine CES with other metrics : Use CES alongside NPS and CSAT to get a full picture of customer experience. Act on feedback quickly : Use qualitative comments to identify quick wins and long-term fixes. Communicate results across teams : Share CES insights with product, support, and design teams to align efforts. Track changes over time : Monitor CES trends to see if improvements reduce effort consistently.

By Philip Burgess | UX Research Leader Customer Satisfaction Score (CSAT) is one of the most straightforward ways to measure how users feel about a product or service. For UX teams, CSAT offers a direct line to user sentiment, helping to identify what works and what needs improvement. But using CSAT effectively requires more than just collecting scores. It demands understanding its strengths, limitations, and how to integrate it into the design process. This post explores how UX teams can use CSAT to improve user experience, backed by practical examples and clear steps. What Is CSAT and Why It Matters for UX CSAT measures how satisfied users are with a specific interaction or overall experience. Typically, users answer a simple question like, “How satisfied are you with your experience today?” on a scale from 1 to 5 or 1 to 10. The score is then averaged or converted into a percentage. Why CSAT is valuable for UX teams: Direct feedback: It captures immediate user feelings after an interaction. Easy to collect: Simple surveys can be embedded in apps, websites, or emails. Actionable: Low scores highlight areas needing attention. Benchmarking: Teams can track satisfaction over time or compare different features. CSAT is not a perfect metric. It reflects subjective feelings and can be influenced by factors outside UX, such as customer support or pricing. Still, when combined with other data, it offers a clear window into user happiness. User completing a satisfaction survey on a touchscreen device User completing a satisfaction survey on a touchscreen device How UX Teams Should Collect CSAT Data Collecting CSAT data requires thoughtful timing and placement to get honest and useful responses. After key interactions: Ask users to rate their satisfaction immediately after completing a task, such as finishing a purchase or submitting a form. Keep it short: Use a single question with a clear scale to avoid survey fatigue. Use multiple channels: Embed surveys in apps, websites, or follow-up emails to reach different user segments. Segment responses: Collect metadata like device type, user location, or session length to analyze trends. For example, an e-commerce site might ask for CSAT right after checkout, while a SaaS product could prompt users after they complete a tutorial or use a new feature. Interpreting CSAT Scores for UX Improvements CSAT scores alone don’t tell the full story. UX teams should dig deeper to understand why users feel satisfied or dissatisfied. Look for patterns: Identify which features or pages have consistently low scores. Combine with qualitative feedback: Pair CSAT with open-ended questions asking users to explain their rating. Track over time: Monitor how scores change after design updates or new releases. Compare segments: See if certain user groups report lower satisfaction and investigate why. For instance, if a mobile app’s checkout process has a low CSAT, qualitative comments might reveal users find the payment options confusing or the interface slow. Using CSAT to Prioritize UX Work UX teams often face many improvement opportunities. CSAT helps prioritize by highlighting what matters most to users. Focus on pain points: Features or flows with low CSAT should get immediate attention. Balance quick wins and big projects: Some issues may be easy to fix and boost satisfaction quickly, while others require more effort but impact many users. Validate changes: After implementing fixes, measure CSAT again to confirm improvements. A practical example: A streaming service noticed low CSAT scores on its search feature. The team redesigned the search interface and added filters. Follow-up CSAT surveys showed a 20% increase in satisfaction, confirming the change’s success. UX designer reviewing customer satisfaction data on laptop UX designer reviewing customer satisfaction data on laptop Best Practices for Integrating CSAT into UX Processes To get the most from CSAT, UX teams should embed it into their workflows: Make CSAT part of regular user research: Use it alongside usability tests, interviews, and analytics. Share results across teams: Communicate CSAT insights with product managers, developers, and customer support. Set clear goals: Define target satisfaction levels for key features or user journeys. Use CSAT to guide design sprints: Prioritize user stories based on satisfaction data. Avoid over-reliance: Combine CSAT with other metrics like Net Promoter Score (NPS) or task success rates for a fuller picture. Common Pitfalls to Avoid When Using CSAT CSAT is useful but can mislead if not handled carefully: Ignoring context: A low score might reflect external issues, not UX problems. Survey fatigue: Asking too often can reduce response quality. Small sample sizes: Limited responses may not represent the whole user base. Focusing only on averages: Look at score distribution to catch extreme dissatisfaction. UX teams should treat CSAT as one tool among many, not the sole measure of success.

By Philip Burgess | UX Research Leader Measuring user experience (UX) is crucial for creating products that satisfy and retain customers. One popular tool for this is the Net Promoter Score (NPS), a simple metric that asks users how likely they are to recommend a product or service. While NPS can offer valuable insights, it also has limitations that can mislead UX teams if not used carefully. This post explores when NPS works well for UX and when it falls short, helping you decide how to use it effectively. User providing feedback on a mobile app What NPS Measures in UX NPS asks users to rate their likelihood of recommending a product on a scale from 0 to 10. Respondents are grouped into: Promoters (9-10): Loyal users who are enthusiastic about the product. Passives (7-8): Satisfied but unenthusiastic users. Detractors (0-6): Unhappy users who might discourage others. The score is calculated by subtracting the percentage of detractors from promoters. This gives a single number that reflects overall user sentiment. For UX teams, NPS can serve as a quick health check. A high NPS often correlates with positive experiences, while a low score signals issues that need attention. It’s especially useful for tracking changes over time, such as after a redesign or new feature launch. When NPS Works Well for UX Tracking Overall Satisfaction NPS provides a straightforward way to gauge general user satisfaction. For example, a software company might see NPS rise after improving onboarding, confirming the change helped users feel more confident. Identifying Trends Over Time Because NPS is easy to collect regularly, it helps teams spot trends. If the score drops after a release, it signals a need to investigate. This ongoing feedback loop supports continuous improvement. Benchmarking Against Competitors Some industries publish average NPS scores, allowing companies to compare their user experience against peers. This can motivate teams to improve and help prioritize UX investments. Combining NPS with Qualitative Feedback When paired with open-ended questions, NPS helps uncover why users feel a certain way. For example, a low score accompanied by comments about slow load times points directly to a UX problem. When NPS Fails for UX Oversimplifying Complex Experiences User experience is multi-dimensional, involving usability, design, performance, and emotional response. NPS reduces all this to a single number, which can hide important details. Two products with the same NPS might offer very different experiences. Ignoring Context and User Segments NPS averages feedback from all users, but different segments may have very different views. For example, new users might struggle with a product while experienced users love it. Without segmenting data, teams might miss these nuances. Vulnerability to Bias NPS responses can be biased by timing, question phrasing, or user mood. For instance, asking for feedback immediately after a frustrating task may produce unfairly low scores. Also, some users are more likely to respond than others, skewing results. Limited Actionability Without Follow-Up A low NPS signals dissatisfaction but doesn’t explain why. Without qualitative data or further research, teams may struggle to identify specific UX issues to fix. UX analytics dashboard displaying NPS trends over time Best Practices for Using NPS in UX Use NPS as one of several metrics. Combine it with usability tests, task success rates, and qualitative feedback for a fuller picture. Segment your users. Analyze NPS by user type, experience level, or geography to uncover hidden patterns. Ask follow-up questions. Always include open-ended questions to understand the reasons behind scores. Time your surveys carefully. Avoid interrupting users during frustrating moments or immediately after errors. Track changes over time. Use NPS to monitor the impact of UX improvements or new features. Communicate results clearly. Share NPS trends with your team and stakeholders to align on priorities. Examples of NPS in UX Use A popular streaming service used NPS to track user satisfaction after redesigning its interface. The score rose from 35 to 50 over six months, confirming the redesign improved user experience. However, by segmenting data, the team found that older users still struggled with navigation. This insight led to targeted improvements for that group. In contrast, a mobile app company relied solely on NPS and saw a sudden drop after a major update. Without qualitative feedback, they initially blamed the update itself. Later research revealed the issue was a bug affecting only a small user segment. This example shows why NPS alone can mislead. Final Thoughts on NPS for UX NPS offers a simple, quick way to measure user sentiment and track UX changes. It works best when combined with other methods and when teams dig deeper into the reasons behind the scores. Relying on NPS alone risks missing important details and user segments.

By Philip Burgess | UX Research Leader When users struggle with a product or service, the signs often show up in their mistakes. One of the clearest ways to spot these issues is by measuring the error rate . This simple metric can uncover major usability problems that might otherwise go unnoticed. Understanding and tracking error rate helps designers and developers create smoother, more intuitive experiences. What Is Error Rate and Why It Matters Error rate measures how often users make mistakes while interacting with a system. These mistakes can be anything from clicking the wrong button, entering invalid data, or failing to complete a task. By calculating the percentage of errors compared to total attempts, teams get a clear picture of where users struggle. Why focus on error rate? Because it directly reflects the user’s experience. A high error rate signals confusion, frustration, or poor design. It points to parts of the interface that need improvement. Unlike subjective feedback, error rate provides objective data that teams can act on. How to Measure Error Rate Effectively Measuring error rate requires careful planning and clear definitions. Here are key steps to follow: Define what counts as an error Not every mistake is equal. Decide which actions qualify as errors based on your goals. For example, entering a wrong password might be an error, but hesitating before clicking a button might not. Choose the right tasks to test Select tasks that represent common or critical user goals. This ensures the error rate reflects real-world challenges. Collect data systematically Use usability testing sessions, analytics tools, or user recordings to gather error data. Make sure to capture enough samples for reliable results. Calculate error rate clearly Divide the number of errors by the total number of attempts, then multiply by 100 to get a percentage. For example, if 15 errors occur in 100 attempts, the error rate is 15%. Tracking error rate over time also helps monitor improvements after design changes. Error messages displayed on a form submission screen Common Usability Problems Revealed by High Error Rates High error rates often highlight specific usability issues. Some common problems include: Confusing navigation Users click wrong links or buttons because menus are unclear or inconsistent. Poor form design Forms with unclear labels, missing instructions, or strict validation cause frequent input errors. Unclear feedback When the system does not clearly explain errors or next steps, users repeat mistakes. Complex workflows Tasks that require many steps or decisions increase the chance of errors. For example, an e-commerce checkout page with unclear field labels and no inline validation might show a 20% error rate in address entry. This signals a need to simplify the form and provide better guidance. Using Error Rate to Improve Design Once you identify areas with high error rates, use the data to guide improvements: Simplify interfaces Remove unnecessary options and clarify labels to reduce confusion. Add helpful feedback Provide clear error messages and suggestions to help users correct mistakes quickly. Test alternative designs Run A/B tests to compare versions and see which reduces errors. Train users when needed For complex systems, offer tutorials or tooltips to guide users. By focusing on reducing error rate, teams improve usability and user satisfaction. Lower error rates often lead to faster task completion and fewer support requests. Participant performing tasks during a usability testing session Practical Examples of Error Rate Impact Consider a mobile banking app that tracks login errors. If 30% of users fail to log in on the first try, this high error rate suggests problems with password entry or authentication flow. The team might respond by simplifying password requirements or adding biometric options. In another case, a software company noticed a 25% error rate in a file upload feature. Users often selected wrong file types or missed required fields. After redesigning the upload form with clearer instructions and file type filters, the error rate dropped to 8%. These examples show how error rate highlights real pain points and guides targeted fixes. Final Thoughts on Using Error Rate Error rate is a straightforward but powerful metric for uncovering usability problems. It provides clear evidence of where users struggle and helps prioritize design improvements. By defining errors carefully, measuring consistently, and acting on the data, teams can create more user-friendly products.

By Philip Burgess | UX Research Leader Understanding how much time someone spends on a task often seems like a straightforward way to measure productivity or engagement. But time on task can be misleading if taken at face value. It reveals some truths but hides others. This post explores what time on task really tells you, where it falls short, and how to use it wisely. Tracking time spent on a task with a timer and notes What Time on Task Measures Time on task simply records the duration someone spends actively working on a specific activity. This can be tracked manually with a stopwatch or automatically through software tools. It provides a clear, objective number: minutes or hours dedicated to a task. This measurement can help in several ways: Identifying effort : Longer time often means more effort or complexity. Estimating workload : Helps managers understand how long tasks take. Tracking progress : Useful for comparing planned versus actual time spent. Spotting distractions : If time on task is low, it may indicate interruptions or lack of focus. For example, a student studying for an exam might log 3 hours on a particular subject. This shows dedication and can help plan future study sessions. What Time on Task Does Not Show Despite its usefulness, time on task does not tell the whole story. It misses important factors that affect quality and effectiveness. Quality of Work Spending more time does not guarantee better results. Someone might spend hours on a task but produce low-quality work due to lack of skill, poor focus, or inefficient methods. Conversely, an expert might complete the same task quickly with excellent results. Engagement and Motivation Time on task does not reveal how engaged or motivated a person is. Someone might be physically present but mentally checked out, or they might be multitasking and not fully focused. These nuances affect outcomes but remain invisible in time data. Task Difficulty and Complexity Two tasks with the same time on task can differ greatly in difficulty. For example, writing a complex report and answering simple emails might both take 30 minutes, but the cognitive load and skill required are very different. Interruptions and Breaks Time on task often counts total time spent but may not account for interruptions or breaks. A person might spend 2 hours on a task but with frequent distractions, reducing actual productive time. How to Use Time on Task Effectively To get the most value from time on task data, combine it with other information and context. Pair Time with Output Quality Measure the quality or results of the work alongside time spent. For example, track the number of errors, customer satisfaction, or grades. This helps identify if more time leads to better outcomes or if efficiency can improve. Consider Individual Differences People work at different speeds and have varying skills. Use time on task as a guide, not a strict benchmark. Encourage individuals to focus on quality and learning rather than just clocking hours. Use Time Data to Identify Bottlenecks If a task consistently takes longer than expected, investigate why. It might reveal process inefficiencies, unclear instructions, or lack of resources. Addressing these issues can improve overall productivity. Track Time in Context Combine time on task with notes about interruptions, task complexity, or emotional state. This richer data helps explain why time varies and guides better decisions. Digital timer showing elapsed time next to a checklist Practical Examples Software development : Developers track time spent coding, debugging, and testing. But success depends on code quality and user feedback, not just hours logged. Customer service : Agents’ time on calls is measured, but customer satisfaction scores reveal true effectiveness. Learning : Students’ study time is recorded, but test scores and comprehension tests show actual learning.