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: Can strong process create writers? From:"Eric J. Ray" <ejray -at- RAYCOMM -dot- COM> Date:Tue, 10 Nov 1998 10:14:50 -0700
At 10:32 AM 11/10/98 -0600, Laurel Nelson wrote:
>Whether or not a strong documentation process can create a technical writer
>is secondary to this question: Who is going to train this potential writer?
>The topic of on-the-job tech writing training has been discussed at length
>on this list, and everytime it is, I think the same question: Who is going
>to train this person?
And that's a very good question. The points you made (that
I snipped) were all right on target.
In my experience, management must understand that a
senior-level writer can either effectively train a novice
writer, or do the regularly-scheduled job, but not do both
well (assuming a mere mortal with the normal number of hours
in a week).
Depending on the writer and the organization, a
lack of training can be a temporary inconvenience for
all concerned, or fatal for the project, the writer, or
even for the tech pubs group.
Eric J. Ray RayComm, Inc. http://www.raycomm.com/ ejray -at- raycomm -dot- com
*Award-winning author of several popular computer books
*Syndicated columnist: Rays on Computing
*Technology Department Editor, _Technical Communication_