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.
RE: "Are technical writers the unsung heroes of document generation?"
Subject:RE: "Are technical writers the unsung heroes of document generation?" From:"Cardimon, Craig" <ccardimon -at- M-S-G -dot- com> To:'William Sherman' <bsherman77 -at- embarqmail -dot- com> Date:Tue, 23 Jun 2015 11:51:45 +0000
I don't mind being insurance. Most everyone needs insurance. Smile.
-----Original Message-----
From: techwr-l-bounces+ccardimon=m-s-g -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+ccardimon=m-s-g -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of William Sherman
Sent: Monday, June 22, 2015 9:08 PM
To: TECHWR-L Writing
Subject: Re: "Are technical writers the unsung heroes of document generation?"
Back on track, yes, they are the unsung heroes, but not in the way most think.
They are insurance.
When the proverbial brown stuff hits the proverbial rotating air mover, what is in those manuals can make or break a company in court. Look up American Airlines Flight 191. American Airlines used an engine removal procedure different than that documented by McDonnell Douglas, and as such, AA took the blame. Had that not existed, McDD would have had the blame. The overall design was not a very good one, so that added to the disaster, but deviating from the acceptable procedure is what caused the accident.
This is where some companies get in trouble. Instead of allowing tech writers to run all the procedures start to finish to ensure the documentation actually matches, short cuts are often taken by having others review it and (maybe) sign off on it. However, those most familiar with a task will frequently skip tasks and not follow word for word a procedure, defeating the review process.
> I'll need to let this one go. It's gone far afield of the situation I
> was discussing.
>
> Certainly an interesting thread, with some good learning. I'm grateful
> for that.
>
> Thanks,
>
> Steve
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
Information contained in this e-mail transmission is privileged and confidential. If you are not the intended recipient of this email, do not read, distribute or reproduce this transmission (including any attachments). If you have received this e-mail in error, please immediately notify the sender by telephone or email reply.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW