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.
Subject:Re: A Sticky Situation From:Chris Hamilton <chamilton -at- GR -dot- COM> Date:Tue, 21 Jan 1997 07:31:46 -0600
You might also look at what that writer is bringing to the table that
Jean is not. For instance, in my environment and to my management, a
writer who is raw, but understands object-oriented concepts well and can
write well, would be considered worth more than someone with lots of
experience, but little understanding. If that's the case, the manager
might have gone that way exactly because your neighbor has lots of
She shouldn't go in without being willing to ask what she has to do to
improve, as well. I don't know your neighbor, but there might be a
problem of some sort with her background and her ability to pick a
certain thing up. I go back to my O-O experience. Ideally, when we get
another writer, I'd like to get one experienced with both O-O and
producing documentation. But because of our schedule, I'd be more
willing to take someone inexperienced who could write over an
experienced person with little background.
Also, I hate to bring this up, but are sex and race involved?
Stephen Arrants wrote:
> A neighbor, Jean, who is also a technical writer, came to me with a
> problem. She one of two writers at a very small hardware company. Her
> manager was the only writer until Jean was hired in October 1996.
> Recently, the company hired another writer, at a salary Jean says is 15%
> above hers. The new writer has six months experience (compared to Jean's
> five years) and has never worked on a complete project (from start to
> Jeannie is angry about the siuation and asked me for advice. i'd advised
> her to take the following approach:
> * List out her strengths, successes, and improvements since she started
> in October.
> * List the responsibilities of *her* job.
> * Gather feedback she's already received from folks she's worked with.
> * Tray and gather salary figures from comparable companies in the area
> (there are only one or two of them, though).
> * Present this to her manager and talk about a rise in salary or
> additional benefits (extra time off, telecommuting, etc.).
> I've warned her not to be confrontational, but to be honest with her
> manager as to how she is feeling about this, and what she sees as a
> Can you give any other advice?
> steve arrants
> 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
Chris Hamilton, Technical Writer
Greenbrier & Russel