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.
"With that in mind, what do _you_ do to increase your
marketability and potential for a newer, better, more
satisfying position, either at your current employer or elsewhere?
Or, what should certain of your co-workers, ex-managers,
or current and former employees consider to make
themselves more valuable in the marketplace?"
Okay, some of these may seem obvious, even presumptuous, but you
asked:
First I know what I'm talking about (or I keep my mouth shut). When I
had my first interviews here, the department manager opened some
system schematics and (before he could explain them) we entered into a
deeper discussion about what the circuits did. As the only writer
interviewed who didn't need an explanation, and was able to freely
discuss the products, I was more valuable. Yes, we talk about other
things, but I am able to keep up to the SMEs on most stuff.
Second, I actually do the writing. Other writers (within the company)
are known to only edit what the SMEs write, or just guess and expect
the SME to edit them. I learn on the job, write about it, and
remember it. Within weeks here I was a respected member of the team
who understood what things did and why. By actually getting the
writing done, and not requiring anywhere as much from an SME, I reduce
their workload and I am more valuable.
Third, I meet deadlines with deadly accuracy. Or plant has gone from
a "best case" of 6-12 weeks late to "worst case" of 2-3 weeks early on
documentation delivery. This means all our products now ship with
finished manuals as opposed to the old habits of preliminary and rush
"quick copy" versions.
Fourth, I try to balance congenial and authoritative styles; I demand
respect and substance, but I also try not to tick people off. I learn
when their "slow times" are and don't waste time asking the same
questions 16 times... others in our office aren't so considerate.
-- I find that asking good questions at good times gets good answers.
-- I try to be productive credible: if I can help a project, I do;
if I can't, I stay out of the way.
-- If I say it can be done, it gets done!
Fifth, I have helped to ensure that what we ship >looks< like a
product from a reputable company. Because of company growth (and not
knowing better), the manuals we used to ship were often late and
looked like bad photocopies. Now, they are delivered on-time, kept
up-to-date, and are offset printed from Lino output with only a
minimal increase in cost.
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
