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:Alexia Prendergast <alexiap -at- SEAGATESOFTWARE -dot- COM> Date:Wed, 12 Nov 1997 09:58:57 -0500
Why should we expect users to sit down and read user manuals? I don't
think it means our docs are bad -- I think it means our users are busy,
impatient people who have jobs to do. If we remember that, and we
remember how we use documentation ourselves, we can write better docs
that suit the needs of those people.
I *use* manuals when I need to get something done. I *read* them out of
professional interest.
A.
--
Alexia Prendergast
Tech Pubs Manager
Seagate Software (Durham, NC, USA) mailto:alexiap -at- seagatesoftware -dot- com
> -----Original Message-----
> 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.
>