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.
A problem with raises is that you are always butting up against the culture
and protocols of that specific company. If documentation is considered an
"expense" within a company it's going to be hard to gather impressive data
to show how you deserve a grand raise. All you'll be doing is showing the
HR department how you want to increase expenses.
If your company has a policy of a limit of X% raise per year, then you're
gonna have to change the policy to get a better raise. Fat chance. Many
people also hit their heads on the rather arbitrary salary ceilings for
various categories of employment that some companies establish. Frequently,
the only raises that you'll get when you max out your salary are COL
increases.
In many cases the way of getting the largest salary increase is to jump
ship -- find another company willing to pay you better. Of course, you'll
inherit whatever salary protocols used by that new company.
Paul Strasser
Louisville, CO
>Not sure what Eric's take is on this, but IMHO, the occasional pulse-check
>on raises/earnings seems a valid topic. I would guess that every tech
writer
>is interested in compensation.
>