Overview of the Methodology

The validation test is conducted in similar fashion to the assessment test with three major exceptions.

- Prior to the test, benchmarks or standards for the tasks of the test are either developed or identified. This can be speciíic error or time measures, or as simple as eliminating the problems identified in earlier explora tory tests.

- Participants are given tasks to perform with either very little or no interaction with a test moderator. (And they are probably not asked to "think aloud.")

- The collection of quantitative data is the central focus, although reasons for substandard performance are identified.

Because you are measuring user performance against a standard, you also need to determine beforehand how adherence to the standard wilí be measured, a-nd what actions will be taken if the product does not meet its standards. For example, if the standard for a task addresses "time to complete," must 70 percent of participants meet the standard, or will you simply compare the standard to the average score of all participants? Under what conditions will the product's schedule be postponed? Will there be time to retest those tasks that did not meet the standard? These are all questions that should be addressed and resolved prior to the test.

Compared to an assessment test, a validation test requires more emphasis on experimental rigor and consistency, because you are makirtg important quantitative judgments about the product. Make sure that members of the design team have input and buy-in into developing the standards used during the test. That way they will not feel as if the standards were overly difficult or unattainable.