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: Philosophy: the Aim of Technical Comms? From:Nancy Hayes <nancyh -at- PMAFIRE -dot- INEL -dot- GOV> Date:Thu, 2 May 1996 13:39:11 GMT
>> "Give them what they need, when they need it."
> And to that I would add "and where they need it".
And I would add, "whether or not they really =want= it".
I work with
technical procedures, and if we gave the users what they need, when they
need it, and where they need it, we'd end up with hundred-page procedures
(or 2-page procedures if we're talking about a senior operator).
I'll agree that user-oriented technical writing is the best idea, but in
many cases what the user needs isn't necessarily what the user wants.
Nancy Lynn Hayes nancyh -at- pmafire -dot- inel -dot- gov OR NHAYES -at- inel -dot- mail
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net