Usability Testing Techniques

A design can pass a usability test and still feel exhausting. That is why 𝗡𝗔𝗦𝗔-𝗧𝗟𝗫 is useful in UX research. NASA-TLX, the Task Load Index, is a post-task rating method for measuring perceived workload. Instead of asking only whether users succeeded, it asks what success cost them. The scale looks at six dimensions: 🧠 𝗠𝗲𝗻𝘁𝗮𝗹 demand: How much thinking, remembering, deciding, or searching was required? 💪 𝗣𝗵𝘆𝘀𝗶𝗰𝗮𝗹 demand: How much physical action was required? ⏱️ 𝗧𝗲𝗺𝗽𝗼𝗿𝗮𝗹 demand: How rushed or time-pressured did the task feel? 🎯 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲: How successful did the user feel? 🔥 𝗘𝗳𝗳𝗼𝗿𝘁: How hard did the user have to work to reach that result? 😤 𝗙𝗿𝘂𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻: How insecure, annoyed, discouraged, or stressed did the user feel? In a UX study, the usual pattern is simple. Users complete a task, then rate these dimensions. Researchers compare ratings across tasks, prototypes, user groups, or design alternatives. The result is not just a score. The real value is often in the workload profile: where the burden appears and what kind of burden it is. This matters because ease of use is not the same as low workload. A product can be learnable but draining. A checkout can be fast but stressful. A dashboard can be powerful but mentally expensive. A workflow can produce few errors while forcing users to hold too much in memory. NASA-TLX helps teams see these hidden costs. It turns subjective strain into a structured design signal. For UX designers, that signal is practical: 🔍 Reveal cognitive friction that observation alone may miss. 📊 Compare competing designs beyond task time and completion rate. ⚠️ Explain why users make errors, hesitate, or abandon a flow. ✅ Encourage interfaces that are not only efficient, but sustainable to use. Good UX reduces the work the interface adds to the work users already came to do.

You run a usability test. The results seem straightforward - most users complete the task in about 10 seconds. But when you look closer, something feels off. Some users fly through in five seconds, while others take over 20. Same interface, same task, wildly different experiences. Traditional UX analysis might smooth this out by reporting the average time or success rate. But that average hides a crucial insight: not all users are the same. Maybe experienced users follow intuitive shortcuts while beginners hesitate at every step. Maybe some users perform better in certain conditions than others. If you only look at the averages, you’ll never see the full picture. This is where mixed-effects models come in. Instead of treating all users as if they behave the same way, these models recognize that individual differences matter. They help uncover patterns that traditional methods - like t-tests and ANOVA - tend to overlook. Mixed-effects models help UX researchers move beyond broad generalizations and get to what really matters: understanding why users behave the way they do. So next time you're analyzing UX data, ask yourself - are you just looking at averages, or are you really seeing your users?

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

“I don’t like it.” “Ok, so what would you like instead?” “…I don’t know.” Real conversation from one of my recent sessions. My first instinct was frustration. My second was: wait, this is actually the whole point! Because here’s the truth we sometimes forget: users are excellent at recognizing what doesn’t work, and genuinely bad at articulating what would. That’s not a flaw in your participants. That’s just how humans work. So how do you find “the version that works” when users can’t tell you? The research is actually pretty clear on this: 🔹 Pairwise comparisons over open questions. Studies show people perform significantly better when comparing two options side by side than when asked to define their preferences from scratch, especially when they’re unsure what their criteria even are. Show A vs. B, not a blank canvas. 🔹 Think-aloud protocols. Don’t ask what they want. Watch what they struggle with. Research on usability methods found think-aloud testing was significantly associated with products actually getting iterated and improved afterward. Behavior beats opinion. 🔹 Triangulate your methods. studies found user testing, interviews, and surveys each caught usability problems the others missed. User testing alone found just over half. No single method gives you the full picture. 🔹 Iterate, don’t interrogate. Usability testing isn’t about extracting the answer from users in one session. It’s about creating enough versions and enough contrast that the right direction reveals itself. “I don’t like it” isn’t a dead end, It’s data.