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 docs vs. user documentation? From:"Beth Kane" <bethkane -at- tcisolutions -dot- com> To:<TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM> Date:Fri, 28 Jan 2000 12:15:18 -0700
I would never define user docs that way ("user docs...are what you use once
you already know the basics").
I've always written user docs as if they're the only training the users are
going to get. They're aimed at the beginner as well as the intermediate to
advanced user. You never know whether the users will get any training. You
have to allow for the possibility they won't, or else you're likely to get a
whole lot of calls to tech support. My user docs contain all the how-tos,
with the possible exception of highly technical how-tos.
What you're calling user docs is what I'd call a reference manual,
containing deeper details (more on the why, not just the how), more
technical background, troubleshooting info, etc.
If I were to write training docs I'd add more training-like things -- things
a user's guide doesn't have -- such as objectives, summaries and practice
lessons. I'd also format them even more openly (more white space), and add
boxes and the like.
Beth Kane
Senior Technical Writer
Total Control Information Inc.
bethkane -at- tcisolutions -dot- com <mailto:bethkane -at- tcisolutions -dot- com>
-----Original Message-----
Geoff says:
..Training docs are intended
to get the reader comfortable enough to use the software with a basic degree
of efficiency and (ideally) give the reader the confidence to learn more
things by consulting the user documentation. The user docs, on the other
hand, are what you use once you already know the basics of a product and
want to learn how to do more.