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: Scenario: You're hired a new writer... From:Chris Hamilton <chamilton -at- GR -dot- COM> Date:Fri, 30 Jan 1998 09:28:01 -0600
What a new writer needs to have varies from job to job. I've done
writing at four places, and I'd look for a different set of skills in a
new writer in each place. Right now, I'd need someone who's not afraid
of some very technical, cutting edge technology. In previous jobs, that
hasn't been the case.
But by not telling the person anything about what's expected, you
haven't done much in terms of setting that person up for success. The
ultimate success or failure of someone's project is the responsibility
of that person, but if you put in place an environment where that person
has the structure and practices of the group as a framework for working
successfully, that person's going to do better than if you just say go
to it and walk away. Even the successes will be more successful if
there's a framework within which to build.
Chris
--
Chris Hamilton, Sr. Technical Writer chamilton -at- gr -dot- com
Greenbrier & Russel http://www.gr.com
-------------------------
These views are mine, not my employer's.
