One of the fundamental principles behind usability testing is to let the participants actually use the software, app, or website and see what problems might emerge. By simulating use and not interrupting participants, you can detect and fix problems before users encounter them, get frustrated, and stop using and recommending your product. So while there’s
Did you do that task correctly? Unmoderated testing provides many benefits. The most notable of which is the ability to collect metrics from a large and geographically diverse sample of participants quickly. A common metric collected in usability tests is the task completion rate. It’s often called the fundamental usability metric because if users can’t complete
It’s often called web surfing or web browsing, but it probably should be called web doing. While there is still plenty of time to kill using the web, in large part, we’re all trying to get things done. Purchasing, reserving, comparing and communicating—Internet behavior is largely a goal directed activity. If a website doesn’t help
Completion rates are the fundamental usability metric: A binary measure of pass and fail (coded as 1 or 0) provides a simple metric of success. If users cannot complete a task, not much else matters with respect to usability or utility. Easy to understand: They are easy to collect and easy to understand for both
It depends (you saw that coming). Context matters in deciding what a good completion rate is for a task, however, knowing what other task completion rates are can be a good guide for setting goals. An analysis of almost 1200 usability tasks shows that the average task-completion rate is 78%. The Fundamental Usability Metric A
It would be nice if all users completed tasks in a usability test. If they did you wouldn’t have to worry about what to do with their task times if they are unable to complete the task. But then again, if all your users had no problems completing tasks, you wouldn’t worry about improving usability.
