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.
Subject:Re: acceptable error rates From:Rebecca Phillips <Rebecca -at- QRONUS -dot- CO -dot- IL> Date:Thu, 24 Oct 1996 17:31:57 +0200
>A well-written, understandable document with the occasional typo is
>infinitely preferable to an incomplete, confusing or impenetrable
That doesn't mean you can't measure documentation errors. It might be
difficult to measure, but it is measurable.
Here we consider documentation errors the same way we consider software
bugs. If someone finds a problem with a document, whether it is a typo
or a customer complaint that the function was explained incorrectly, it
is entered into the Quality Assurance "bug" database. When it is fixed,
we report it to the QA department, and it is removed from the bug list.
In the same way that software has critical, major, and minor bugs, so
does software. I have been in situations where the documentation was
rated as buggy as the software. That sent the company a screaming sign
that they needed to budget more documentation staff.