User Experience Metrics That Support Data-Driven Decisions

UX metrics work best when aligned with the right questions. Below are ten common UX scenarios and the metrics that best fit each. 1. Completing a Transaction When the goal is to make processes like checkout, sign-up, or password reset more efficient, focus on task success rates, drop-off points, and error tracking. Self-reported metrics like expectations and likelihood to return can also reveal how users perceive the experience. 2. Comparing Products For benchmarking products or releases, task success and efficiency offer a baseline. Self-reported satisfaction and emotional reactions help capture perceived differences, while comparative metrics provide a broader view of strengths and weaknesses. 3. Frequent Use of the Same Product For tools people use regularly, like internal platforms or messaging apps, task time and learnability are essential. These metrics show how users improve over time and whether effort decreases with experience. Perceived usefulness is also valuable in highlighting which features matter most. 4. Navigation and Information Architecture When the focus is on helping users find what they need, use task success, lostness (extra steps taken), card sorting, and tree testing. These help evaluate whether your content structure is intuitive and discoverable. 5. Increasing Awareness Some studies aim to make features or content more noticeable. Metrics here include interaction rates, recall accuracy, self-reported awareness, and, if available, eye-tracking data. These provide clues about what’s seen, skipped, or remembered. 6. Problem Discovery For open-ended studies exploring usability issues, issue-based metrics are most useful. Cataloging the frequency and severity of problems allows you to identify pain points, even when tasks or contexts differ across participants. 7. Critical Product Usability Products used in high-stakes contexts (e.g., medical devices, emergency systems) require strict performance evaluation. Focus on binary task success, clear definitions of user error, and time-to-completion. Self-reported impressions are less relevant than observable performance. 8. Designing for Engagement For experiences intended to be emotionally resonant or enjoyable, subjective metrics matter. Expectation vs. outcome, satisfaction, likelihood to recommend, and even physiological data (e.g., skin conductance, facial expressions) can provide insight into how users truly feel. 9. Subtle Design Changes When assessing the impact of minor design tweaks (like layout, font, or copy changes), A/B testing and live-site metrics are often the most effective. With enough users, even small shifts in behavior can reveal meaningful trends. 10. Comparing Alternative Designs In early-stage prototype comparisons, issue severity and preference ratings tend to be more useful than performance metrics. When task-based testing isn’t feasible, forced-choice questions and perceived ease or appeal can guide design decisions.

Over the last year, I’ve seen many people fall into the same trap: They launch an AI-powered agent (chatbot, assistant, support tool, etc.)… But only track surface-level KPIs — like response time or number of users. That’s not enough. To create AI systems that actually deliver value, we need 𝗵𝗼𝗹𝗶𝘀𝘁𝗶𝗰, 𝗵𝘂𝗺𝗮𝗻-𝗰𝗲𝗻𝘁𝗿𝗶𝗰 𝗺𝗲𝘁𝗿𝗶𝗰𝘀 that reflect: • User trust • Task success • Business impact • Experience quality    This infographic highlights 15 𝘦𝘴𝘴𝘦𝘯𝘵𝘪𝘢𝘭 dimensions to consider: ↳ 𝗥𝗲𝘀𝗽𝗼𝗻𝘀𝗲 𝗔𝗰𝗰𝘂𝗿𝗮𝗰𝘆 — Are your AI answers actually useful and correct? ↳ 𝗧𝗮𝘀𝗸 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗶𝗼𝗻 𝗥𝗮𝘁𝗲 — Can the agent complete full workflows, not just answer trivia? ↳ 𝗟𝗮𝘁𝗲𝗻𝗰𝘆 — Response speed still matters, especially in production. ↳ 𝗨𝘀𝗲𝗿 𝗘𝗻𝗴𝗮𝗴𝗲𝗺𝗲𝗻𝘁 — How often are users returning or interacting meaningfully? ↳ 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗥𝗮𝘁𝗲 — Did the user achieve their goal? This is your north star. ↳ 𝗘𝗿𝗿𝗼𝗿 𝗥𝗮𝘁𝗲 — Irrelevant or wrong responses? That’s friction. ↳ 𝗦𝗲𝘀𝘀𝗶𝗼𝗻 𝗗𝘂𝗿𝗮𝘁𝗶𝗼𝗻 — Longer isn’t always better — it depends on the goal. ↳ 𝗨𝘀𝗲𝗿 𝗥𝗲𝘁𝗲𝗻𝘁𝗶𝗼𝗻 — Are users coming back 𝘢𝘧𝘵𝘦𝘳 the first experience? ↳ 𝗖𝗼𝘀𝘁 𝗽𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝗮𝗰𝘁𝗶𝗼𝗻 — Especially critical at scale. Budget-wise agents win. ↳ 𝗖𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝘁𝗵 — Can the agent handle follow-ups and multi-turn dialogue? ↳ 𝗨𝘀𝗲𝗿 𝗦𝗮𝘁𝗶𝘀𝗳𝗮𝗰𝘁𝗶𝗼𝗻 𝗦𝗰𝗼𝗿𝗲 — Feedback from actual users is gold. ↳ 𝗖𝗼𝗻𝘁𝗲𝘅𝘁𝘂𝗮𝗹 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 — Can your AI 𝘳𝘦𝘮𝘦𝘮𝘣𝘦𝘳 𝘢𝘯𝘥 𝘳𝘦𝘧𝘦𝘳 to earlier inputs? ↳ 𝗦𝗰𝗮𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆 — Can it handle volume 𝘸𝘪𝘵𝘩𝘰𝘶𝘵 degrading performance? ↳ 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗥𝗲𝘁𝗿𝗶𝗲𝘃𝗮𝗹 𝗘𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝗰𝘆 — This is key for RAG-based agents. ↳ 𝗔𝗱𝗮𝗽𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗦𝗰𝗼𝗿𝗲 — Is your AI learning and improving over time? If you're building or managing AI agents — bookmark this. Whether it's a support bot, GenAI assistant, or a multi-agent system — these are the metrics that will shape real-world success. 𝗗𝗶𝗱 𝗜 𝗺𝗶𝘀𝘀 𝗮𝗻𝘆 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗼𝗻𝗲𝘀 𝘆𝗼𝘂 𝘂𝘀𝗲 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀? Let’s make this list even stronger — drop your thoughts 👇

When we think about improving an online shopping experience, we often jump to new features or a better design. But behind the scenes, web performance—how fast and smoothly a site loads and responds—is one of the biggest drivers of user satisfaction and business impact. In a recent blog post, Walmart Global Tech’s Engineering team shared their journey to improve their site’s performance systematically, and the lessons are highly relevant for anyone building digital products today. Their journey began with choosing the right metrics. Instead of relying solely on backend or infrastructure-level indicators, they shifted toward Core Web Vitals, a set of user-centric metrics that reflect the real customer experience. These include how quickly content loads (Largest Contentful Paint), when the page becomes interactive (Interaction to Next Paint), and how stable the layout is during loading (Cumulative Layout Shift). By anchoring their efforts in these three metrics, the team ensured that any optimization directly improved what customers actually felt. From there, they focused on how to move these metrics across a massive user base meaningfully. The team set goals based on the 75th percentile, ensuring that improvements benefited most users and weren’t overly influenced by outliers. They also embedded web performance into company-wide decision-making: Core Web Vitals are integrated into Walmart’s experimentation platform, incorporated into the release review process, and included in leadership discussions. In other words, performance isn’t just an engineering KPI—Walmart turned it into a shared organizational priority. This work is a great reminder that improving performance isn’t just an engineering task; it’s about building a culture where user experience is measurable, visible, and owned by everyone. Their approach shows that when a company aligns around the right metrics and integrates them into everyday workflows, even small performance gains can compound into meaningful business results. #DataScience #Analytics #Metrics #CoreWebVitals #Optimization #WebPerformance #SnacksWeeklyonDataScience – – –  Check out the "Snacks Weekly on Data Science" podcast and subscribe, where I explain in more detail the concepts discussed in this and future posts:    -- Spotify: https://lnkd.in/gKgaMvbh   -- Apple Podcast: https://lnkd.in/gFYvfB8V    -- Youtube: https://lnkd.in/gcwPeBmR https://lnkd.in/gqsfix-p

NPS Is Overrated. Here’s What Actually Matters. NPS is like checking your weight once a year—it gives you a number but tells you nothing about why it changed or what to do next. 🚨 The problem with NPS: • It’s a lagging indicator; when you see a drop, the damage is done. • It ignores why people feel the way they do; often, people don't know. That's why we have therapists... • It’s easy to manipulate; asking “Would you recommend us?” after a support call gets biased answers. • It gives one number to represent an entire human experience, like summarizing a movie with “meh.” ❌ Never rely on a single metric. Why? Because one KPI is a blindfold. It creates tunnel vision. You’ll make the wrong decisions because you’re optimizing one thing while everything else burns in the background. Real experience management needs a basket of KPIs that tell different sides of the story — just like you triangulate qualitative research data to actually understand what’s going on. ✅ A better approach: Balanced scorecards To manage journeys, track a mix of KPIs: ✔ Customer Effort Score (CES) – because easy beats delightful. ✔ Support tickets & complaints – pain points show up here first. ✔ Operational KPIs – cost per journey, revenue per journey, retention rates. ✔ Emotional journeys – yes, feelings are data too. 📌 Pro tip: Use leading indicators (e.g., CES, wait times) alongside lagging ones (e.g., churn, NPS). It’s not just about seeing the wreck — you want to steer before you hit the iceberg. #servicedesign #journeymap #journeymanagement #CX #NPS 🔥 What KPIs do you track beyond NPS? Drop your favorites. Or your horror stories. Both welcome.

When reporting on your impact as a UX Researcher, here are the best → worst metrics to tie your work to: 𝟭. 𝗥𝗲𝘃𝗲𝗻𝘂𝗲 Every company is chasing revenue growth. This is especially true in tech. Tying your work to new (or retained) revenue is the strongest way to show the value that you’re bringing to the organization and make the case for leaders to invest more in research. Examples: - Research insights → new pricing tier(s) → $X - Research insights → X changes to CSM playbook → Y% reduction in churn → $Z 𝟮. 𝗞𝗲𝘆 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻𝘀 This might not be possible for many UXRs, but if you can, showing how your work contributed to key decisions (especially if those decisions affect dozens or hundreds of employees) is another way to stand out. Examples: - Research insights → new ideal customer profile → X changes across Sales / Marketing / Product affecting Y employees' work - Research insights → refined product vision → X changes to the roadmap affecting Y employees' work 𝟯. 𝗡𝗼𝗿𝘁𝗵 𝘀𝘁𝗮𝗿 𝗲𝗻𝗴𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝗺𝗲𝘁𝗿𝗶𝗰𝘀 If you can’t directly attribute your work to revenue, that’s ok! The majority of research is too far removed from revenue to measure the value in dollars. The next best thing is to tie your work to core user engagement metrics (e.g. “watch time” for Netflix, “time spent listening” for Spotify). These metrics are north star metrics because they’re strong predictors of future revenue. Examples: - Research insights → X changes to onboarding flow → Y% increase in successfully activated users - Research insights → X new product features → Y% increase in time spent in app 𝟰. 𝗖𝗼𝘀𝘁 𝘀𝗮𝘃𝗶𝗻𝗴𝘀 For tech companies, a dollar saved is usually less exciting than a dollar of new (or retained) revenue. This is because tech companies’ valuations are primarily driven by future revenue growth, not profitability. That being said, cost savings prove that your research is having a real / tangible impact. 𝟱. 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝗺𝗲𝘁𝗿𝗶𝗰𝘀 𝘁𝗵𝗮𝘁 𝗰𝗮𝗻’𝘁 𝗯𝗲 𝘁𝗿𝗮𝗰𝗲𝗱 𝘁𝗼 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗮𝗯𝗼𝘃𝗲 Hot take: The biggest trap for researchers (and product folks generally) is focusing on user experience improvements that do not clearly lead to more engagement or more revenue. At most companies, it is nearly impossible to justify investments (including research!) solely on the basis of improving the user experience. Reporting on user experience improvements without tying them to any of the metrics above will make your research look like an expendable cost center instead of a critical revenue driver. — TL;DR: Businesses are driven by their top line (revenue) and bottom line (profit). If you want executives to appreciate the impact of (your) research, start aligning your reporting to metrics 1-4 above.

AI changes how we measure UX. We’ve been thinking and iterating on how we track user experiences with AI. In our open Glare framework, we use a mix of attitudinal, behavioral, and performance metrics. AI tools open the door to customizing metrics based on how people use each experience. I’d love to hear who else is exploring this. To measure UX in AI tools, it helps to follow the user journey and match the right metrics to each step. Here's a simple way to break it down: 1. Before using the tool Start by understanding what users expect and how confident they feel. This gives you a sense of their goals and trust levels. 2. While prompting  Track how easily users explain what they want. Look at how much effort it takes and whether the first result is useful. 3. While refining the output Measure how smoothly users improve or adjust the results. Count retries, check how well they understand the output, and watch for moments when the tool really surprises or delights them. 4. After seeing the results Check if the result is actually helpful. Time-to-value and satisfaction ratings show whether the tool delivered on its promise. 5. After the session ends See what users do next. Do they leave, return, or keep using it? This helps you understand the lasting value of the experience. We need sharper ways to measure how people use AI. Clicks can’t tell the whole story. But getting this data is not easy. What matters is whether the experience builds trust, sparks creativity, and delivers something users feel good about. These are the signals that show us if the tool is working, not just technically, but emotionally and practically. How are you thinking about this? #productdesign #uxmetrics #productdiscovery #uxresearch

🔮 UX Metrics and KPIs Cheatsheet (Figma) (https://lnkd.in/en9MK4MD), a helpful reference sheet for UX metrics, with formulas and examples — for brand score, desirability, loyalty, satisfaction, sentiment, success, usefulness and many others. Neatly put together in one single place by fine folks at Helio Glare. To me personally, measuring UX success is focused around just a few key attributes — how successful users are in completing their key tasks, how many errors users experience along the way and how quickly users get through onboarding to first meaningful success. The context of the project will of course request specific, custom metrics — e.g. search quality score, or brand score, or engagement score or loyalty — but UX metrics are all around delivering value to users through their successes. Here are some examples: 1. Top tasks success > 80% (for critical tasks) 2. Time to complete top tasks < Xs (for critical tasks) 3. Time to first success < 90s (for onboarding) 4. Time to candidates < 120s (nav + filtering in eCommerce) 5. Time to top candidate < 120s (for feature comparison) 6. Time to hit the limit of a free tier < 7d (for upgrades) 7. Presets/templates usage > 80% per user (to boost efficiency) 8. Filters used per session > 5 per user (quality of filtering) 9. Feature adoption rate > 30% (usage of a new feature per user) 10. Feature retention rate > 40% (after 90 days) 11. Time to pricing quote < 2 weeks (for B2B systems) 12. Application processing time < 2 weeks (online banking) 13. Default settings correction < 10% (quality of defaults) 14. Relevance of top 100 search queries > 80% (for top 5 results) 15. Service desk inquiries < 35/week (poor design → more inquiries) 16. Form input accuracy ≈ 100% (user input in forms) 17. Frequency of errors < 3/visit (mistaps, double-clicks) 18. Password recovery frequency < 5% per user (for auth) 19. Fake email addresses < 5% (newsletters) 20. Helpdesk follow-up rate < 4% (quality of service desk replies) 21. “Turn-around” score < 1 week (frustrated users -> happy users) 22. Environmental impact < 0.3g/page request (sustainability) 23. Frustration score < 10% (AUS + SUS/SUPR-Q) 24. System Usability Scale > 75 (usability) 25. Accessible Usability Scale (AUS) > 75 (accessibility) Each team works with 3–4 design KPIs that reflect the impact of their work. Search team works with search quality score, onboarding team works with time to success, authentication team works with password recovery rate. What gets measured, gets better. And it gives you the data you need to monitor and visualize the impact of your design work. Once it becomes a second nature of your process, not only will you have an easier time for getting buy-in, but also build enough trust to boost UX in a company with low UX maturity. [continues in comments ↓] #ux #design

🔎 UX Metrics: How to Measure and Optimize User Experience? When we talk about UX, we know that good decisions must be data-driven. But how can we measure something as subjective as user experience? 🤔 Here are some of the key UX metrics that help turn perceptions into actionable insights: 📌 Experience Metrics: Evaluate user satisfaction and perception. Examples: ✅ NPS (Net Promoter Score) – Measures user loyalty to the brand. ✅ CSAT (Customer Satisfaction Score) – Captures user satisfaction at key moments. ✅ CES (Customer Effort Score) – Assesses the effort needed to complete an action. 📌 Behavioral Metrics: Analyze how users interact with the product. Examples: 📊 Conversion Rate – How many users complete the desired action? 📊 Drop-off Rate – At what stage do users give up? 📊 Average Task Time – How long does it take to complete an action? 📌 Adoption and Retention Metrics: Show engagement over time. Examples: 📈 Active Users – How many people use the product regularly? 📈 Churn Rate – How many users stop using the service? 📈 Cohort Retention – What percentage of users remain engaged after a certain period? UX metrics are more than just numbers – they tell the story of how users experience a product. With them, we can identify problems, test hypotheses, and create better experiences! 💡🚀 📢 What UX metrics do you use in your daily work? Let’s exchange ideas in the comments! 👇 #UX #UserExperience #UXMetrics #Design #Research #Product

💎 Overview of 70+ UX Metrics Struggling to choose the right metric for your UX task at hand? MeasuringU maps out 70+ UX metrics across task and study levels — from time-on-task and SUS to eye tracking and NPS (https://lnkd.in/dhw6Sh8u) 1️⃣ Task-Level Metrics Focus: Directly measure how users perform tasks (actions + perceptions during task execution). Use Case: Usability testing, feature validation, UX benchmarking. 🟢 Objective Task-Based Action Metrics These measure user performance outcomes. Effectiveness: Completion, Findability, Errors Efficiency: Time on Task, Clicks / Interactions 🟢 Behavioral & Physiological Metrics These reflect user attention, emotion, and mental load, often measured via sensors or tracking tools. Visual Attention: Eye Tracking Dwell Time, Fixation Count, Time to First Fixation Emotional Reaction: Facial Coding, HR (heart rate), EEG (brainwave activity) Mental Effort: Tapping (as proxy for cognitive load) 2️⃣ Task-Level Attitudinal Metrics Focus: How users feel during or after a task. Use Case: Post-task questionnaires, usability labs, perception analysis. 🟢 Ease / Perception: Single Ease Question (SEQ), After Scenario Questionnaire (ASQ), Ease scale 🟢 Confidence: Self-reported Confidence score 🟢 Workload / Mental Effort: NASA Task Load Index (TLX), Subjective Mental Effort Questionnaire (SMEQ) 3️⃣ Combined Task-Level Metrics Focus: Composite metrics that combine efficiency, effectiveness, and ease. Use Case: Comparative usability studies, dashboards, standardized testing. Efficiency × Effectiveness → Efficiency Ratio Efficiency × Effectiveness × Ease → Single Usability Metric (SUM) Confidence × Effectiveness → Disaster Metric 4️⃣ Study-Level Attitudinal Metrics Focus: User attitudes about a product after use or across time. Use Case: Surveys, product-market fit tests, satisfaction tracking. 🟢 Satisfaction Metrics: Overall Satisfaction, Customer Experience Index (CXi) 🟢 Loyalty Metrics: Net Promoter Score (NPS), Likelihood to Recommend, Product-Market Fit (PMF) 🟢 Awareness / Brand Perception: Brand Awareness, Favorability, Brand Trust 🟢 Usability / Usefulness: System Usability Scale (SUS) 5️⃣ Delight & Trust Metrics Focus: Measure positive emotions and confidence in the interface. Use Case: Branding, premium experiences, trust validation. Top-Two Box (e.g. “Very Satisfied” or “Very Likely to Recommend”) SUPR-Q Trust Modified System Trust Scale (MST) 6️⃣ Visual Branding Metrics Focus: How users perceive visual design and layout. Use Case: UI testing, branding studies. SUPR-Q Appearance Perceived Website Clutter 7️⃣ Special-Purpose Study-Level Metrics Focus: Custom metrics tailored to specific domains or platforms. Use Case: Gaming, mobile apps, customer support. 🟢 Customer Service: Customer Effort Score (CES), SERVQUAL (Service Quality) 🟢 Gaming: GUESS (Game User Experience Satisfaction Scale) #UX #design #productdesign #measure

Most companies see business, customer, and UX metrics as separate stories. I had Bruno M. (JP Morgan Chase, HealthEquity), who led the journey-centric transformation to make these separate layers work together. I love the simplicity of the approach, when every job to be done or journey get structured with 3 layers of metrics. That way, every level of the journey framework is consistent: 1️⃣ Business Layer (Top Layer) This layer focuses on traditional KPIs that matter most to executives — the metrics that indicate how the journey contributes to overall business performance. Examples include: - Revenue - Conversion rates - Cost savings (e.g., shorter average handle time) - Retention / Churn rates These help executives and general managers see how customer experience links directly to financial and operational performance. 2️⃣ Customer Experience Layer (Middle Layer) Here, Bruno connects business KPIs to customer sentiment using metrics like: - NPS (Net Promoter Score) - CSAT (Customer Satisfaction) While he’s critical of NPS (“hard to know what’s really broken just from NPS”), he acknowledges it remains a key business-facing metric that helps secure buy-in from leadership. However, he stresses that NPS alone is meaningless — its value emerges only when overlaid with other measures like completion rates or drop-off data. 3️⃣ UX / Behavioral Layer (Bottom Layer) The third layer goes deeper into the user experience where the actual friction or success of the journey can be observed. Examples include: - Task completion rates - Time on task - Error rates - Drop-offs or conversion funnels These granular metrics help teams act quickly and connect customer behaviors directly to business outcomes. 🤝 How It All Connects Bruno envisions a single dashboard where you can: - Click into a “job to be done” or journey. - See the KPI layer, CX layer, and UX layer all linked together. This way: - Executives can see how journeys drive business. - CX teams can track satisfaction and loyalty. - Product and design teams can pinpoint usability and behavioral issues. He calls this layered approach the core of accountability in journey management. Making sure everyone from the CEO to the UX designer looks at the same truth through their own lens. Check out the Episode for a deep dive, this one is 🔥🔥🔥