Bríef Summary of Test Outcome

Every major task passed the 70 percent successful completion criteria with the exception of two. The team felt that the problems associated with those tasks conld be corrected prior to release, and wanted to schedule a very quick test to confirm. Twenty recommendations from the test were identified for implementation prior to release, and at least fifteen recommendations were diverted to future releases.

Providing a "tour" of advanced features prior to the test proved to be a stroke of genius. Participants loved it, and some even insisted on taking itback to their current jobs. One user suggested the company market it or a onger virtual seminar as a separate product for customers, and that is alreadv _n the works.

The revamped organizatíon of the user guide was much more in ture with users' expectations than the previous set, although the index proved cificult to use. More task-oriented items must be added to the index to icprove accessibility.

As you can tell from this condensed series of tests, the product evolvei over time and reflected each test's findings. We strongly advócate such an mrative approach, but again, do not be discouraged if you can manage only on; :est to begin. Now let's talk about what it takes to be a good test moderator.