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 think your main concern should be why the previous tech
> writers couldn't catch on. Were they given a chance to
> familiarize themselves with the subjects and communicate
> effectively with the other personnel?
> This is not a knee-jerk defense of tech writers in general.
> If you recall, there was a discussion on this list recently
> about being required to document software without being given
> the chance to actually use the software.
To speak to Keith's point about "catching on": mainly, I rely on my
ability to *learn* and my native inclination and interest in
engineering, science, and computer technology. Test results in high
school indicated a very strong aptitude for engineering, but my gender
was an obstacle in the schools I went to, so I chose technical writing
instead. In addition to technical writing, I have also had other
IT-related jobs: system and network administrator, customer support, and
system and business analyst, all of which broadened my technical
experience considerably. People are sometimes surprised at how technical
I am "for a tech writer." (Surprise!)
There are tech writers who are extremely technical, and there are others
who approach our discipline from a more creative angle. And, some
positions just don't require a lot of technical ability; for example,
writing corporate policies.
In my experience, it's not always the technical writer who failed:
sometimes the hiring manager does not know the "right" questions to ask
a prospective tech writer. Sometimes it can just be a bad fit.
It sounds like they got it right this time, since you have the technical
ability they are looking for. Hopefully, living down your predecessors
won't take too long.
Good luck with the new position!
Technical Writer/Reporting Analyst
This message and any attachments may contain confidential or privileged
information and are only for the intended recipient of this message. If
you are not the intended recipient, please notify the sender by return
email or phone, and delete or destroy this and all copies of this
message and all attachments. Any unauthorized disclosure, use,
distribution, or reproduction of this message or any attachments is
prohibited and may be unlawful.