The other common approach is to create a case – study example that include all frequently encountered situations that the system is able to handle and that the users should be able to handle. Then the users must use the system to handle the actual situations that is enter data as required,
process the data, and prepare reports. If the system is inquiry – oriented, the case study should require the user to pose and receive responses to inquiries. If the results produced do not match those provided in the training guide, the users will know that mistakes were made.
During training, systems personnel should be alert to comments made by users or to problems that users may encounter. Although human factors testing, performed earlier, is intended
to detect difficulties, some problems may not occur until inexperienced users are directly interacting with the system. Despite testing, awkward keying requirements to enter data,
unexpected transactions, or unusual ways of preparing transactions may still arise during training. The trainer must be certain to involve systems personnel when problems in the design are found, while assisting users who are reluctant to change from their old ways to the new methods required to use the system. Of course, the trainer must first be certain that the new methods are necessary and do represent an improvement over current methods.