TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Training and documentation From:"Weissman, Jessica" <WeissmanJ -at- ABACUSTECH -dot- COM> Date:Tue, 3 Nov 1998 16:58:27 -0500
When I've done standup training on software, I make sure to show the users
the help system as part of the training. In the few cases where the client
is distributing printed documentation to all users, I make sure we look at
that, too.
But training materials aren't the same as documentation. They focus on
exercises rather than on the more complete presentation found in
documentation.
When I've based a class on a series of slides (rare for me but common for
other trainers), the slides form a kind of training outline. But the order
in which I train the skills or components varies a lot from the order in the
manual. Of course if the manual includes a tutorial component, that may
well be so similar to the training that there's no need for extra training
materials.
