RE: A Question for Newbies and Intermediate Writers

["Giordano, Connie" <Connie -dot- Giordano -at- FMR -dot- COM>]

Sheldon,  these are my suggestions based on my experiences in getting up to
speed quickly:

Review any and all existing information regarding the system architecture,
process models, business requirements, specifications, and believe it or
not, contracts with the clients (it's nice to know in advance what's been
promised).

If there is an existing version of the product, spend as much time as
possible using it, breaking it, and questioning it.  Work with any QA staff
to reviewing reported defects and requested enhancements.

Work with business analysts, program/product managers, lead developers, and
other SMEs to develop functional and design specifications. 

Knowing what the current product does and doesn't do, what the new stuff
should do, and what's been promised has been invaluable in planning and
writing the doc in some semblance of a realistic schedule.

HTH

Connie Giordano 

-----Original Message-----
From: Sheldon Kohn [mailto:Sheldon -dot- Kohn -at- onlineinsight -dot- com]
Sent: Wednesday, April 19, 2000 9:57 AM
To: TECHWR-L
Subject: A Question for Newbies and Intermediate Writers


Hello All,

I am asking for advice and perspectives based on your experience when you
entered the tech comms field. 

[SNIP]

My question to those of you who are relatively new to the field is, what was
most helpful in the first weeks and months of your professional life? I do
not want (or need) to take a "sink or swim" approach, so I want to make sure
that we use our limited ramp-up time wisely.