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:Re: Tech writer status <rant> From:"Megan E. Rock" <megan -dot- rock -at- FANUCROBOTICS -dot- COM> Date:Wed, 24 Feb 1999 11:35:13 -0500
Melonie Holliman said:
"As a technical writer, I have a unique view point and can significantly
improve a product or service."
Obviously most of us technical writers believe this or we would be in a
different line of work. But how many of you work for companies where
management outside of the technical writing department truly appreciates and
respects a technical writer's perspective and recognizes the value that
quality documentation adds to a product?
I know that it's common for a manager of a documentation group to champion
the cause, but it seems that in many cases the documentation group is
constantly fighting to be heard because documentation is viewed as a
necessary evil by the engineering groups.
How have you influenced the thinking of non-documentation management so they
also insist on clear, concise, and usable documentation?
Megan E. Rock
megan -dot- rock -at- fanucrobotics -dot- com