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: Advice Sought: supervising an extreme novice From:Bob Gembey <bob -at- SUPERNOVA -dot- NL> Date:Wed, 26 May 1999 10:22:48 +0200
Michele,
Rowena's advice was right on-target. If I may add from my experience
supervising new writers,
1. It does help to sit down with them every now and again and talk about
the approach they are taking, and the approach you would take. It is
important that you make clear, in your discussions, when you are making a
suggestion that they may choose to ignore, and when you are making a
correction that you want them to implement.
2. If this person is not a writer at all, you first have to find out
whether they have writing talent. If not, oh boy, I don't know what to
tell you. If they do, then you should also give a short run-down on the
"housestyle" used for the help files. Also, you should prep them on what
kinds of reactions they are going to get from the developers, and, how to
"translate" the type of jargon they are going to get from them into
something the intended audience will understand. In particular, whether
certain types of jargon are acceptable for the audience.
Lastly, the 3 weeks may be a bit long for a training period for someone
only working the summer. I'm not sure where you could cut corners, because
the actions all seem necessary, and its not unreasonable, but maybe it's
not practical.