Re: Training a new writer

Subject: Re: Training a new writer
From: "Damien Braniff" <DBraniff -at- amphion -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 11 Dec 2001 15:02:25 -0000

When I first started tools weren't really anything to worry about
(pencil and paper and then to typists!) and I still don't think they
are. Tools are fairly easy to pick up, especially if someone familiar
with using other packages. As to the writing, the best method is
show/write/edit/rewrite. Basically it seems you're almost there:

show the process - what information goes in the document, where
to get it, who to ask etc
write the document - show examples of what's expected, explain
styles etc and let them get on with it (make the first one fairly small)
edit - go through the document with them, point out what needs
changing, content to be added/removed, style etc
rewrite - get them to make the changes and edit it again. Repeat
as often as required until right

This was the process I went through, very much on the job and it worked
well for all the trainees. I started work in Sept my first document went
to the customer in January after several rewrites. Intensive for the
mentor (need to be very patient) but the next doc was

Damien Braniff
Technical Writer
Amphion Semiconductor Ltd.
50/51 Malone Road
BT9 5BS Belfast, Antrim
Northern Ireland

Tel: 028 9050 4000
Fax: 028 9050 4001
E-mail: dbraniff -at- amphion -dot- com

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?

Have you looked at the new content on TECHWR-L lately?
See and check it out.

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 for more resources and info.

Previous by Author: ADMIN: RE: Network Security Article Clarification
Next by Author: RE: Consequences of not really understanding
Previous by Thread: Re: Training a new writer
Next by Thread: Quality of source material from Development

What this post helpful? Share it with friends and colleagues:

Sponsored Ads