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.
FORWARDED ANONYMOUSLY ON REQUEST.
REPLY _ON_ THE LIST--I CANNOT FORWARD INDIVIDUAL
MESSAGES. ERIC
Job Opportunity Anxiety
I'm presented with an opportunity that looks very interesting,
but I'm a bit concerned about the direction it will take my
career. I'd love your insights.
Background: I have 7 years experience in "traditional"
tech writing for several software developement companies.
Mostly I've developed end-user manuals, online help, and
our interenet web site. I've also worked extensively on our
product development team doing audience and requirements
analysis (which is why I've been offered this new position.)
New Opportunity: A newly created role within the support
department of a software development company. This company
has a "knowledge base" consisting of documents created
by Support Specialists when resolving customer problems
with the software.
My job would be to improve the quality of these documents
(by providing templates, instruction, editing, and anything
else I can think of). But primarily I'd develop and oversee the
interenet/extranet environment that allows customers and
Support Specialists access to these documents. I'd be
expected to "maintain and expand the on-line documentation
systems" -- this does not refer to their online help system,
which is maintained by the tech writing department.
Eventually, they'd like to develop an Expert System or
Electronic Performance Support System (EPSS)
or software agent (like the little Einstein in Word for Win97)
and would look to me (and my department) to be an integral
part of that development. (They see EPSS as the natural
evolution of their "knowledge base".) I know this is a huge
job -- they have already stated that there will be a need to
change this role into a whole department -- which I would be
heading up.
Other Info: They currently have a Technical Writing department
that does all the end user documentation. I would not be part
of the department, but definately would work to establish
collaboration with them.
My Anxieties: This is not truly a Technical Writing position,
but is definately a Technical Communication position. I'm
excited by the opportunity, but leary of leaving the area with
which I am so comfortable.
I'm wondering if I take this job, whether I could readily
move back into traditional tech writing (manuals, online help,
etc.) if I wanted to down the road.
What do you seasoned professionals think of a move like
this? I'm trying to weigh the pros and cons, but fear my
judgement is a bit clouded due to my eagerness to leave
my present position.
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
