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:Pages per hour From:Richard Mateosian <srm -at- C2 -dot- ORG> Date:Sat, 10 Jun 1995 10:12:15 -0700
>How many pages of a tech manual can you produce in one day (8 hours)?
Does anyone else find this a naive and silly question?
I don't mean to pick on the poster. Predicting how long a job is going to
take is crucial to bidding on it. Evaluating an employee's productivity is
an important management responsibility. It would be wonderful if there were
an easy rule of thumb for this. Unfortunately, it's not that simple.
Whenever a task gets so predictable that you can make this kind of estimate,
along comes a "productivity tool" to aid or automate that part of the
process. Everyone's output increases as a result, but the unpredictability
returns.
Twenty-five years ago, at the dawn of the word processing age, nobody would
have attempted half of the things that routinely appear on the pages of
technical manuals today. With today's technology it might take a year to
produce what will routinely appear on a "page"--whatever that comes to
mean--of a manual twenty-five years from now.
Whenever we look for productivity standards, we are looking at the routine
aspects of the job. These are probably not the main source of quality in
communication. ...RM