Selecting tasks. One of the essential requirements of every usability test is that the test participants attempt tasks that users of the product will perform. When a product of even modest complexity is tested, however, there are more tasks than there is time available to test them, so it is necessary to sample tasks. In a diagnostic test, testers select tasks for three primary reasons:
They include important tasks such as (a) tasks that are performed frequently or are basic to the job users will want to accomplish, and (b) tasks that are critical, if infrequent, because they affect other tasks, such as log in or configuration.
They include tasks that probe areas where usability problems are likely.
They include tasks that probe the components of a design, such as tasks that force the user to navigate to the lowest level of the menus or tasks that have toolbar shortcuts. The goal is to include tasks that increase thoroughness at uncovering problems.
Generating task scenarios. Almost without exception, testers present the tasks that participants do in the form of a task scenario. For example:
"You have just bought a new combination telephone and answering machine. The box is
on the table. Take the product out of the box and set it up so that you can make and
receive calls.
Selecting tasks. One of the essential requirements of every usability test is that the test participants attempt tasks that users of the product will perform. When a product of even modest complexity is tested, however, there are more tasks than there is time available to test them, so it is necessary to sample tasks. In a diagnostic test, testers select tasks for three primary reasons:
Generating task scenarios. Almost without exception, testers present the tasks that participants do in the form of a task scenario. For example:
"You have just bought a new combination telephone and answering machine. The box is on the table. Take the product out of the box and set it up so that you can make and receive calls.