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: QUESTION: Legal liability for incorrect documentation
Subject:Re: QUESTION: Legal liability for incorrect documentation From:John Posada <posada -at- FAXSAV -dot- COM> Date:Fri, 6 Feb 1998 11:29:05 -0500
Larry...
Here's what I would do.
Management is always hearing that the sky is falling, and in most cases, is rarely as severe as made out to be.
You need to present solid logical information to management.
Therefore, instead of just running to management and yelling OHMYGOD!!, ask your lead programmer to let you know what three of the most serious problems are, what the impact is to the customer, and what resources would be needed to fix those three problems. Then, if you can, extend it out something to the effect of "It is my understanding that the three problems outlined in this report is 20% of the total actual problems. A report can be submitted itemizing the problems, their impact to the customer and your bottom line, and the required resources to fix those problems.". You present it in a professional manner and it's then up to management to address it. You them go on about your other work.
John
-----Original Message-----
From: Larry Weber [SMTP:larry_weber -at- HOTMAIL -dot- COM]
Sent: Friday, February 06, 1998 11:15 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: QUESTION: Legal liability for incorrect documentation
Esteemed colleagues:
What are the legal liabilities for publishing incorrect documentation?
BACKGROUND: I work on an application that includes its own programming
language, source code, and compiler. Marketing hypes these features as
customization capabilities. However, according to the lead programmer,
the documentation we provide (which I have inherited) is severely
out-of-date and, in many cases, blatantly wrong. I'm not thrilled about
the idea of updating this material, but I want to make management aware
of the situation and associated consequences.
Thanks in advance,
Larry Weber
larry_weber -at- hotmail -dot- com
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
