Time-on-Task Analysis

Ever launched a product or feature, only to see users drop off without knowing why? You check the analytics - traffic looks fine, but engagement is slipping. Where are users struggling? Why do some breeze through while others get stuck? Traditional metrics like bounce rates and session counts barely scratch the surface. This is where session analysis becomes a game-changer. It moves beyond surface-level metrics to uncover hidden behavioral patterns - why users hesitate, get frustrated, or abandon tasks entirely. One of the biggest challenges in UX research is understanding friction points in real time. Hesitation detection reveals where users pause too long, signaling uncertainty or cognitive overload. Rage click detection catches moments of frustration - those rapid, repeated clicks that scream, "Why is this not working?" But frustration does not always look the same. Some users walk away silently. Task abandonment analysis helps us detect disengagement before it is too late, using behavioral trends rather than arbitrary cutoffs. Dwell time analysis adds another layer, showing how long users actively engage before losing interest. Of course, not all users behave the same way. Clustering techniques help group them based on interaction styles, making personalization and targeted interventions possible. And we can take it further - predictive modeling, like logistic regression, helps forecast dropout risk, allowing us to act proactively rather than reactively.

💎 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

When we run usability tests, we often focus on the qualitative stuff — what people say, where they struggle, why they behave a certain way. But we forget there’s a quantitative side to usability testing too. Each task in your test can be measured for: 1. Effectiveness — can people complete the task? → Success rate: What % of users completed the task? (80% is solid. 100% might mean your task was too easy.) → Error rate: How often do users make mistakes — and how severe are they? 2. Efficiency — how quickly do they complete the task? → Time on task: Average time spent per task. → Relative efficiency: How much of that time is spent by people who succeed at the task? 3. Satisfaction — how do they feel about it? → Post-task satisfaction: A quick rating (1–5) after each task. → Overall system usability: SUS scores or other validated scales after the full session. These metrics help you go beyond opinions and actually track improvements over time. They're especially helpful for benchmarking, stakeholder alignment, and testing design changes. We want our products to feel good, but they also need to perform well. And if you need some help, i've got a nice template for this! (see the comments) Do you use these kinds of metrics in your usability testing? UXR Study

✅ How To Run Task Analysis In UX (https://lnkd.in/e_s_TG3a), a practical step-by-step guide on how to study user goals, map user’s workflows, understand top tasks and then use them to inform and shape design decisions. Neatly put together by Thomas Stokes. 🚫 Good UX isn’t just high completion rates for top tasks. 🤔 Better: high accuracy, low task on time, high completion rates. ✅ Task analysis breaks down user tasks to understand user goals. ✅ Tasks are goal-oriented user actions (start → end point → success). ✅ Usually presented as a tree (hierarchical task-analysis diagram, HTA). ✅ First, collect data: users, what they try to do and how they do it. ✅ Refine your task list with stakeholders, then get users to vote. ✅ Translate each top task into goals, starting point and end point. ✅ Break down: user’s goal → sub-goals; sub-goal → single steps. ✅ For non-linear/circular steps: mark alternate paths as branches. ✅ Scrutinize every single step for errors, efficiency, opportunities. ✅ Attach design improvements as sticky notes to each step. 🚫 Don’t lose track in small tasks: come back to the big picture. Personally, I've been relying on top task analysis for years now, kindly introduced by Gerry McGovern. Of all the techniques to capture the essence of user experience, it’s a reliable way to do so. Bring it together with task completion rates and task completion times, and you have a reliable metric to track your UX performance over time. Once you identify 10–12 representative tasks and get them approved by stakeholders, we can track how well a product is performing over time. Refine the task wording and recruit the right participants. Then give these tasks to 15–18 actual users and track success rates, time on task and accuracy of input. That gives you an objective measure of success for your design efforts. And you can repeat it every 4–8 months, depending on velocity of the team. It’s remarkably easy to establish and run, but also has high visibility and impact — especially if it tracks the heart of what the product is about. Useful resources: Task Analysis: Support Users in Achieving Their Goals (attached image), by Maria Rosala https://lnkd.in/ePmARap3 What Really Matters: Focusing on Top Tasks, by Gerry McGovern https://lnkd.in/eWBXpCQp How To Make Sense Of Any Mess (free book), by Abby Covert https://lnkd.in/enxMMhMe How We Did It: Task Analysis (Case Study), by Jacob Filipp https://lnkd.in/edKYU6xE How To Optimize UX and Improve Task Efficiency, by Ella Webber https://lnkd.in/eKdKNtsR How to Conduct a Top Task Analysis, by Jeff Sauro https://lnkd.in/eqWp_RNG [continues in the comments below ↓]

How do you include metrics in your case study? Especially if it’s not a real-world case study. Here are some ideas. 👇 1. Task Success Rate How often did the user complete a specific task (that you indicated) using your prototype? This gauges the usability of your design. For example, if you had 5 users try this task and 3 of them completed the task, you had a 60% Task Success Rate. (You really want it to be higher!). But maybe you go back and re-iterate your design based on user feedback and now you find you get a 90% task success rate. That’s worth noting in your case study, including the results of both tests so hiring managers know you improved the task rate because you observed user feedback and you re-iterated your design. 2. Time on Task How long does it take to complete a given task? This indicates the efficiency of your design. It’s best if you can compare the first time someone tries to complete the task (using one of your first iterations) to how long it takes after your final design. This shows improvement as you re-iterated your design based on user feedback. Another idea is to compare your time against industry standards or to how long it takes to complete the same task on a competitor’s site. 3. User Error Rate How many mistakes does a user make when completing a certain task? This determines how user-friendly your design is and helps define pain points. To use this rate, you must first define the total number of possible errors when completing the task. It may be just one (ie. enter your username) or several (enter username and password). (This is a very simplified example.) To find the user error rate: total number of errors occurred / total number of possible errors So, if 2 errors are possible in the task, and 5 people attempted the task and there were a total of 3 errors made. The user error rate is: 30% (3 / (2 x 5). The lower the number the better. 😊 4. Customer(User) Satisfaction Score This measures how happy your customer or user is about a specific product or feature and their user experience. The typical question is, “Did you find our app [or specific feature/task] do what you needed it to today?" And, offer a Yes/No response. PS. It’s best to plan for these ‘tests’ as you start the project. However, hindsight is always better than foresight. If you realize after the fact (which happens a lot with beginning UX/UI’ers), you won’t be able to show how these rates improved throughout your design process, but you can share the end results. And, you can potentially compare that against competitor results or industry standards. PSS. Share these metrics on your resume, too. Recruiters and hiring managers like to see impact. 😊 What other metrics do you suggest for showing impact in your case studies? #uxdesign #metrics #results #casestudies #designportfolios