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.
Re: Techwriters in the product development cycle (was Help2)
Subject:Re: Techwriters in the product development cycle (was Help2) From:"Lori A. Moreland" <Lori -dot- Moreland -at- CLE -dot- AB -dot- COM> Date:Wed, 9 Aug 1995 08:46:21 -0400
Wm. MacLeod asks about where in the product development cycle manuals should be
developed.
My suggestion:
<Soapbox on>
Right at the start. Sit in on the design review meetings. Actively discuss
publication needs with the engineering or product manager. From that meeting,
develop a publication strategy. The strategy should include as much information
as posssible about the document(s) you will produce. As you begin to develop
the documents, revise your strategy based on the product's development.
Remain flexible throughout this process. Don't panic when a sudden change to the
product means you have to change your strategy or your document. If you calmly
accomodate the million or so changes that can (and probably will) happen,
engineers/product managers will feel that you are responsive to their needs.
This will definitely enhance your credibility with them.
</Soapbox off>
Lori Moreland
Sr. Technical Communicator
Allen-Bradley Co.
Lori -dot- Moreland -at- cle -dot- ab -dot- com
