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.
I agree with your thinking. Personally, I prefer variety in a work
setting, and the opportunity to train as well as write appeals to me.
A couple of caveats: a) You'll have to make sure your tech writers have
demonstrated training skills (developed and delivered training, and /or
taught technical communication); and b) I think that the tech support
function could easily become full time. So then you'd have to plan for
the possibility of asking one of your tech writers to move into a
dedicated tech support role, which is something I know I wouldn't want.
As the business expands, I don't know how easy it will be to bounce
several tech writers around to three different roles.
A key advantage of having a tech writer involved in the training at the
start is that he or she can plan the training with an eye towards
training the users properly to reduce the number of tech support calls,
and to improve and modify the product documentation.
>From: John Bell[SMTP:jbell -at- PARAGREN -dot- COM]
>Sent: Monday, May 12, 1997 9:43 AM
>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>Subject: Radical Idea?
>So, hypothetically speaking, would you as a tech writer enjoy a job
>where you were doing technical writing, client training, and client
>technical support? If the company grows larger and the opportunity to
>split into separate disciplines arises, should we split and which
>discipline(s) would you want to work in?
>--- John Bell
> jbell -at- paragren -dot- com