This is what most people think of when they imagine a ‘usability test’. This technique focuses on how effectively users are able to accomplish their tasks using the interface. It is the most in-depth technique for detecting and correcting critical design flaws.

This evaluation can be done before a redesign of a site to find out areas that work and don’t work. It can also be done early in the product life cycle using a paper prototype. This is a good iterative technique and can be done multiple times as the product design changes and improves.

Process outline:

• Determine the specific areas or functionality of the product to be evaluated and the particular characteristics of the typical user for recruiting purposes.
• Recruit and schedule users.
• Write the task scenarios. Make each task as close to real user tasks as possible.
• Practice the scenarios to see that the tasks work and that the user will see the sections of the site under evaluation.
• Conduct the evaluation.
  • Users perform the tasks with little or no help from the moderator.
  • Users think aloud, explaining what they are doing and why and what they expect of the interface as they perform their tasks.
• Watch users and if possible record the session for later viewing by the project team.
• Write a report of observation findings and recommendations. Work with the team to reach consensus on recommended actions and priorities.
• The team makes the recommended changes.
• Repeat.