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: handbook vs training manual From:"Sarah Bouchier" <Sarah -dot- Bouchier -at- exony -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 11 Oct 2006 13:48:50 +0100
I think your best bet is to start off by thinking about how your
audience are going to use this manual. Are most of them going to read
it through thoroughly, digest it and understand it before starting? If
so, write a training manual. Or are most of them going to flip straight
through to the bit they want (which is what I'm betting will happen in
practice)? If so, write a handbook.
>I have only dabbled in technical writing, but this seems more like a
>training manual than a handbook. It also has multiple audiences in mind
>nonprofit executive staff, nonprofit workers, government staff- and
>include procedural, conceptual, reference and instructional types of
>Am I correct in thinking this is more of a training manual? And will I
>better off approaching this from the instructional design angle, with
>learning objectives etc?