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: Cost Savings and Online Help From:"John H. Olds" <JOlds -at- AOL -dot- COM> Date:Tue, 25 Oct 1994 20:17:35 -0400
We technical writers should spend more time and effort selling management on
the project management and team building aspects of developing good technical
documentation. During the research phase of product development it is
generally the writer who sees the big picture and adds a system control
aspect to the products development.
Often the egineering team is made up of mechanical, electrical, software and
process engineers. These people have a narrow focus and often do not
communicate or get along with each other. The technical communcations
function therefore is the one place were the entire project comes together.
This is an oportunity to micro manage the products development by being an
honest broker and bringing the various functions together. This promotes
understanding and communcations among the product team members were it is
most lacking.
I do not have time here to go into more detail but would welcome the proper
form to do so.
I feel it is up to us to convince senior management because it is not in the
immediate best interest of others to admit their short comings.
