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.
>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?
During department reshuffling at the last company I was at, Documentation
was "merged" with Training. I wasn't expected to train at all (thank
goodness - I suffer from paralyzing stage fright) but I was able to sit
in the back of some of our trainings and this proved invaluable
information. I one case I came back from a training and completely
rewrote the documentation to fit the user profile I'd just met.
When we hired a 3rd Tech writer, the position was specifically a tech
writer/trainer which I though would be appealing (well, at least to
someone who could stand up in front of a group of people without
imitating a deer caught in headlights :)
The Documentation & Training Department was also a sub-department of the
Customer Services Department. We attended all of the Cust Serv staff
meetings and learned some of the more common technical problems so we
could add more information about those areas to our docs & help files.
I say go with your idea.
Millstar Electronic Publishing Group
kpadova -at- millstar -dot- com