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: the document development process From:Mercedes Abels <maa5906 -at- GRIFFON -dot- MWSC -dot- EDU> Date:Fri, 22 Dec 1995 20:24:42 -0600
Our process includes writers in the development team which, for me, has
meant lots of rewriting. We are revising and rewriting text right up to
the day it goes out with the unit most of the time.
The last development team I sat in on included an engineer, a trainer, a
parts person, a marketing rep, and an electrical engineer. (and me, a
publications intern) The documentation went out a week after the first
unit shipped and we will make changes to it to reflect engineering
changes that were made after the trade show. It is truly a living process.
On Thu, 21 Dec 1995, Tammy Hale wrote:
> Methods for improving the document/product/system development process.
> I work for a small software engineering company. At my company, the
> engineers develop the system according to customer requirements, then I
> write the user's manual for the system, and my boss (a writer/editor) edits
> my work. I know that many companies include writers in the development
> process. What other ways do your development practices differ from mine?
> What works? What doesn't? What's helpful? What gets in your way?
