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:Development Procedures - where do you come in? From:Liz -dot- Goodwin -at- ametek -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 25 Jan 2002 08:05:40 -0500
Peggy Lee wrote:
Before completing my response to our V.P., I'd be interested in hearing
from
as many of you as care to respond.
1.) I'd like to know if you are involved in the early stages of product
development. If so, how early -- like preliminary design meetings?
2.) How useful is it to you to be involved in these early meetings?
3.) Do you provide a preliminary design of online help and manuals?
4.) Do you participate in peer reviews?
5.) Other opinions,issues, advice or ideas along these lines?
We have very formal engineering procedures set up (ISO 2000)and, as a tech
writer, I am included once the Product Development Proposal (PDP) has been
written. This document defines the product, the market and the milestones
for development. I am then involved in the weekly product meetings that
include all the engineers working on the project and finally, the monthly
business team meetings which include production, manufacturing and
marketing as well.
I think it is extremely useful to be in on all of the meetings because even
when they are discussing some esoteric point in mass spectrometry, I learn
something. The more I know about the product, the better I can document it.
I don't provide a "preliminary design," but I work closely with the
engineer who is designing the product to define the various modules for the
manual. Usually the software lags behind and we are always rushing to get
it finished. The online software usually does not appear until several
months after the product has been released. The user manual, however, does
include software instructions. So, we do the written manual first and then
work on the online help.
I am also a lone tech writer for this business unit and I do not
participate in peer reviews. I am, however, called upon to help select and
interview candidates when we are hiring for our other locations.
To mix metaphors - "It is better to be in on the ground floor, than to
stumble in the dark!"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.