Re: product documentation liability

Subject: Re: product documentation liability
From: "Peter Neilson" <neilson -at- windstream -dot- net>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Wed, 27 Feb 2013 05:45:25 -0500

On Wed, 27 Feb 2013 01:09:10 -0500, Debbie Hemstreet <D_Hemstreet -at- rambam -dot- health -dot- gov -dot- il> wrote:

Look in the pharmaceutical industry, devices, and quality issues - documentation is everything in these industries.

I don't know the link, I'm sure others do. The most well-known documentation flub had to do with a shuttle disaster. The error was traced to documentation!

Looked for the Shuttle "documentation" problem and did not find it.

In my experience blaming "documentation" for an error is not unlike blaming QC for bad production. "We had a problem with quality. Too much product was being rejected. So we fired the quality manager." I have seen "documentation" listed as the cause of a software error: "Product does not work as described in documentation."

"Documentation" errors can be caused by several factors:
1. Documentation not provided.
2. Obsolete documentation provided.
3. Deliberately false documentation provided.
4. No information available to documentation team.
5. False information provided to documentation team.
6. Written documents not reviewed for technical accuracy.

Now, which of these is the fault of the technical writer?
EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips for creating EPUB, the file format used for e-readers, tablets, smartphones, and more.

Learn more:


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

product documentation liability: From: Simon
RE: product documentation liability: From: Debbie Hemstreet

Previous by Author: Re: Telecommuting ( was: Do as I say, not as I do )
Next by Author: Re: The great note-taking divide is coming
Previous by Thread: RE: product documentation liability
Next by Thread: RE: product documentation liability

What this post helpful? Share it with friends and colleagues:

Sponsored Ads