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.
I am so glad you said that, Gene. I've often heard an arbitrary figure
tossed around like it was gospel, and while my gut told me there was NO
POSSIBLE WAY a TechCom department could run with that, you do what you have
to to make things work.
Kind of like the pastor who heard at an aerobics instructor class that the
maximum volume for a public setting should be 80db. So he tried to push
that onto the sound techs at his church. The difference was the aerobics
class was in a 20ft x 20ft room with 16 ft ceilings. The church building
seated at least 5 times that, plus had a vaulted ceiling that dispersed
sound further than the 80db cap would allow.
Yeah. Metrics need to be accompanied by a disclaimer.
-Tony
On Mon, May 12, 2014 at 11:46 AM, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
> No, and in my opinion it's a worse than useless metric. When you're doing
> graphics-heavy instructions, a page is totally different from a page of
> text, and the last thing you should be doing is encouraging anyone to judge
> writers by the volume of pages they produce.
>
> Gene Kim-Eng
>
>
> On Mon, May 12, 2014 at 11:31 AM, Jim Witkin <jameswitkin -at- gmail -dot- com>
> wrote:
>
> > Is there any industry accepted method for calculating how many tech
> writers
> > are required to maintain a certain number of documentation pages?
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help 2014 v1 now available. SharePoint 2013 support, NetHelp enhancements, and more. Read all about it.
