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.
Anthony Markatos wrote:
>
> Kathi, these are all what Hackos calls documentation "manufacturing" issues.
> As such, they are all relatively easy to correct. It is failures in
> planning, analysis, and overall organization that cause the big
> (next-to-impossible to correct) problems.
>
Tony,
"Manufacturing" issues can cause bridges to crumble and airliners to
fall from the sky. Sometimes they result from poor execution at the
point of manufacture, not in the engineering department.
You can have the best-planned, best-organized documentation in the
world, but if the user cannot make head nor tail of it because it is
poorly written, poorly edited, poorly translated, poorly composed, or
poorly printed, then it is ineffective.
