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:Safety & Tech Manuals From:Richard Lippincott <rlippinc -at- BEV -dot- ETN -dot- COM> Date:Mon, 30 Jan 1995 15:58:24 EST
It's me again, on this subject again.
If you recall, I got a thread going a couple of weeks ago, dealing with the
problem of placing safety warnings in tech manuals, and the impact on the
manual's readability.
The issue has not gone away for us. In fact, it's getting worse.
Just to recap, the problem is that we're being asked to insert so -many-
warnings, and repeating the warnings, that we're afraid the manual will
be ignored. This is ironic: our intent is to alert the user to these hazards,
but we fear that if the manual is ignored, then the user won't ever see the
warnings.
Our legal and safety people feel that, in order to cover our assets, we've
got to provide a "no loophole" approach.
We folks in the tech writing department figure there's a compromise level,
where the manual will be used and read, and still provide adequate warnings.
In order to support our case, we're interested in specific studies done on
usability & readability. We want to be able to document our position, and
indicate how studies show the usability deteriorates.
Or, we'd like to know if, in fact, there is -no- impact, so that we don't look
too foolish in front of management.
If anybody on the list can send info on studies in this area, I would be most
thankful. You can post directly to me, or to the list if you feel it's of
general interest.
Rick Lippincott
Eaton Semiconductor
Beverly, MA
rlippinc -at- bev -dot- etn -dot- com