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.
Has anybody addressed the issue of metrics in documentation; that is,
how do you effectively and accurately measure a writer's productivity?
This isn't sales, in which you can count the number of phone calls,
client calls, dollars brought in, etc. For writing, it's rather absurd
to count the number of keystokes, pages, documents, etc. <snip>
I work for a quickly-growing biotech company's manufacturing dept.
One measure of my success in at least the mechanicals of writing &
editing is how few times the document comes back to correct typos,
formatting problems, or unclear sentences or organization.
Many of the problems Rod mentions (SME delays, etc.) are mine too, but
if I can get what *I* do right, I feel better about the other
problems. And I suggest that metrics (in this case just counting the
trend of typos, etc., over a period of time) is a good way to improve
Doug Montalbano <> Technical Writer <> Chiron Corporation
Doug_Montalbano -at- cc -dot- chiron -dot- com <> (510) 601-2862 (voice/TDD)
How much it all matters, how little it all means.
-- Evelyn Waugh