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.
It varies. In the Software Documentation classes I taught, it ranged
anywhere from 1 page/day for the traditional study/analyze to pick-up-
the-books-at-the-printers process to 2 pages/day documenting working
GUI applications with screen shots and producing final output on laser
printers and copiers.
BTW, for editing figure 50 pages/day for heavy technical info. with
picky highlighting requirements to 75 pages/day for easier
screenshot-laden info.
Don't be surprised if management thinks these times are too
slow...reality irritates them!
I've heard the industry standard for estimating the number of hours per
page is 2.5 to 4 hours. What does this include? Writing alone?
Interviewing, writing, editing, inserting graphics (making and editing
the screen shots?)
I've tried searching the archives but haven't had any luck so I must be
using the wrong key words. If this topic has been explored ad nauseum
previously, give me a clue where to look or reply offline. Thanks.
Judy Kistler-Robinson
jkistler -at- trane -dot- com
The Trane Company
Product Communications
