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: Who Decides? From:Carma C Allen <ccallen -at- BECKMAN -dot- COM> Date:Fri, 16 Apr 1999 11:33:03 -0800
In our company (in our division of the company, that is) the writer, who is
a member of the development team, prepares a Publications Plan during the
assessment phase of the project. This Plan, which (loosely) follows one
that Joanne Hackos has as a model in her book about managing the
publication process, details what documents will be prepared and when. This
is based on the writer's (and the rest of the Pubs Group's) prior
experience, the preliminary marketing product specs (product complexity,
user level, etc), the proposed schedule, available resources, and various
other factors. It includes expected review cycles and final publication
dates, and outlines the affect (effect? impact?) that product schedule
slippage, etc., will have on publication schedules. The Publications Plan
is signed off by all members of the development team
—all have input,
Marketing not really any more than Research & Applications or Field Service
(Engineering and Manufacturing are usually not very concerned—whatever we
say is okay with them, since they seldom deal directly with customers).
Team members usually sign off without any hassle because they know that
we've been doing this for a long time and mostly know what works.