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:TWs in Product Development From:"Hopkins, Sharon" <SharonH -at- CNRX -dot- COM> Date:Fri, 13 Nov 1998 09:44:39 -0500
The small (just post-startup) software company that I work for has asked me
to participate on a Product Management Committee "designed to funnel our
development efforts to the goal of making product changes that will
positively impact existing customer workflow as well as making our
installation/implementation more efficient." In other words, the decision
has been made to include Documentation (I am a department of one) in the
Product Development phase rather than having me do cleanup at the end.
Needless to say I am very happy about this.
I would really like to hear from anyone out there who has experience giving
input at this stage in the development of software. What type of
information were you able to provide? How was it received? Tips on
providing input so that it will be well received? Where is the TW
perspective most valuable?
I have some ideas of my own but I would like to hear what others have to say
as I have never done this before (other than informally) and I don't want to
blow it for myself or my department as the company grows.
Sharon Hopkins
sharonh -at- CNRx -dot- com
Sharon Hopkins
Documentation Manager
CLINICAL NETWORx
A Hollister Company
275 Wyman Street
Waltham, MA 02154
sharonh -at- CNRx -dot- com
(781) 890-0888 x 123
