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: Techwriter Aptitude Test (A Daydream) From:Megan McMacken <mcmackme -at- FRC -dot- COM> Date:Wed, 12 Nov 1997 09:24:01 -0500
>OK. Serious. Reading the docs is usually the first thing I do, and I
>think it has always helped me understand things faster than by just
>playing around. Even if the documentation is lousy, it usually provides
>at least some kind of useful information that would be very hard or even
>impossible to find out otherwise. Dear me, here I am justifying the
>value of reading documentation on the bloody techwriter list! Well,
>anyway folks, why not give it a try sometime, you might be surprised.
Mike brings up an interesting phenomenon. We as technical writers complain
when the users won't read the documentation we spend time and money putting
together, but how often do any of us read through or even skim the manuals
for the gadgets we buy? I usually wait until I'm thoroughly stuck before I
pull out the manual. Perhaps that's because so few manuals I have run
across are well-written, and it's easier for me to just figure it out myself
and learn in the process.
And if the users aren't reading OUR manuals, why aren't they? Bad past
experience with documentation? Too lazy to look for information in the
documentation? Waited until they were completely frustrated before looking
at the manual, couldn't find the help they needed, and gave up? Calling
tech support is faster and easier? Or maybe our documentation isn't as good
as we think.
If users, including us, dislike having to "RTFM," what can we do to remedy
the situation?
Young and still idealistic about my chosen career,
Megan E. McMacken
--------------------------------------------------------------------------
Megan E. McMacken
Product Development and Documentation
FANUC Robotics North America, Inc.
Rochester Hills, Michigan
mcmackme -at- frc -dot- com