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.
On Thu, Sep 13, 2012 at 3:52 PM, Steve Janoff (non-Celgene)
<sjanoff -at- celgene -dot- com> wrote
> Might be helpful to define what you mean by "document quality."
I'm rather fond of how IBM answers that question in their book
Developing Quality Technical Information. Their definition
incorporates a lot different things that I'd been told to focus on
over the course of a decade long career. They break quality down into
three characteristics:
Easy to Use (Task oriented, Accurate, Complete)
Easy to Understand (Clear, Concrete, Style)
Easy to Find (Organization, Retrievability, Visual effectiveness)
For more details, you can check out the "Look Inside" preview of the
Table of Contents over on Amazon.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
