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: Pencil Test for Technical Writers From:Brad Connatser <concom -at- USIT -dot- NET> Date:Sun, 11 Aug 1996 15:25:19 +0000
In article <4uiu3d$34a -at- nntp1 -dot- best -dot- com>, randy -dot- grandle -at- corp -dot- sun -dot- com (Randy
Grandle) wrote:
> Michael Wing <mjwing -at- ingr -dot- com> wrote:
> >
> >With all the discussion on certification, qualifications, correct
> >language usage, and technical aptitude, and so forth, I am wondering if
> >maybe a simple pencil test would help in choosing a candidate for a
> >Technical Writing position. Because contact time with development and
> >other resources is restricted and because the information for the
> >product/service for which they are writing is incomplete and transitory,
> >the position requires a writer who is an innovative thinker. By
> >innovative, I mean that they must fill in the information gaps by
> >extrapolating from the information at hand, see past the black-and-white
> >and describe variations in the product/service, visualize the
> >product/service in terms of its application(s) and not just its
> >step-by-step functioning, and so forth.
snip
> Moreover, the assumption that the only good candidates are those who are
quick
> on their feet and can innovative is questionable. The race is not always to
> the swift. Some of us like to spend time researching, thinking things though,
> and actually planning our work (and we also meet deadlines).
> Productive and effective writing is not done "by-the-seat-of the-pants" and
> "on-the-fly." Productive and effective writing involves a quality
process. You
> cannot bypass the information gathering and planning stage of a good
> writing process and expect good writers to deliver a quality product.
How about a take-home test?
Brad
--
Brad Connatser
Concurrent Communications
concom -at- usit -dot- net
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-
