Re: Cases where bad documentation caused accidents or worse

["Michael West" <mike -dot- west -at- oz -dot- quest -dot- com>]

Bill Hall wrote:
> it would be helpful if people could list other cases
> where documentation failures had obvious consequences.


If you broaden your inquiry from "bad documentation"
to "faulty technical communication" you can find a
horrible amount of stuff. Many air disasters are
attributable to faulty or ambiguous ground-air
communications, for example. You'll find medical
disasters, military disasters, industrial disasters --
you name it -- all attributable to faulty technical communication.
Sub-categories might include ambiguous signals, non-
standard terminology, inappropriate message format,
and so on.

Start with Google and search on "airline disaster transcripts".
Not my idea of a pleasant way to spend an afternoon, though.

--
Michael West
Melbourne



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free copy of ARTS PDF Tools when you register for the PDF
Conference by April 30. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com

Are you using Doc-to-Help or ForeHelp? Switch to RoboHelp for Word for $249
or to RoboHelp Office for only $499. Get the PC Magazine five-star rated
Help authoring tool for less! Go to http://www.ehelp.com/techwr

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.