user testing is important to detect problems

This article is about performing usability testing. This blog will test an in-depth look at the relevance of usability testing.

Usability testing focuses on people and their tasks, and seeks empirical evidence about how to improve the usability of an interface. Usability is an evaluative method that allows teams to observe a user’s experience with a digital application as he or she moves through the steps of a particular task. The research methodology was devised to help teams test the parts of an interface that most and most frustrate in the beginning so that they can be launched.

Tests are designed around tasks and scenarios that represent typical end-user goals. It is common practice that everyone on the interdisciplinary team works together to identify usability testing tasks and scenarios. In usability testing, tasks must be specific, concrete and reflect the real goals of the target group. Tasks and scenarios should neither influence the participant to solve a problem a certain way, nor seek to justify product requirements (which often reflect system or developer goals).

In most cases, usability testing uses the format of thinking aloud protocol technique. This makes it for observers and evaluators easier to detect the following:

1. understands the task but can’t complete it within a reasonable amount of time;

2. understands the goal, but has to try different approaches to complete the task;

3. gives up or resigns from the process;

4. completes a task, but not the task that was specified;

5. expresses surprise or delight;

6. expresses frustration, confusion, or blames themselves for not being able to complete

the task;

7. asserts that something is wrong or doesn’t make sense; or

8. makes a suggestion for the interface or the flow of events.

As usability tests reveal problems, the team will realize that how they evaluate and use the interface is different from how typical end users do. Also, just as the number of participants in the test directly impacts the number of problems that are detected, so does the number of evaluators, the more problems will be detected.

The key to successful usability testing is to require the attendance of developers and project stakeholders at research events. Many teams are making the usability test observation session the only opportunity to see and weigh in on proto types prior to launch. With this approach, you are guaranteed to have observers participate in the

What are your experiences? Let us know in a comment below.