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: STC_MGT--> "Very" Technical Writer Titles From:Smokey Lynne L Bare <slbare -at- JUNO -dot- COM> Date:Thu, 6 Nov 1997 15:48:02 -0500
Pat stated:
....we use "Information Developer" for all positions. We differentiate
only by=
level (1 through 5). We selected this title because we think it's more=
inclusive than "writer" -- editors, illustrators, CD and Web
developers,=
etc. We've talked about changing the highest level to "Documentation=
Consultant" to mirror "Consulting Engineer" as the highest Engineering=
level. However, our 5th level encompasses more than the "very"
technical=
writer. Our 5th level includes people who are project leaders and
mentors=
as well as the highest in technical expertise. They are the most
"visible"=
outside the department, and have the most "upstream" influence. Here,=
someone could be a super technical whiz and not go beyond level 4.=20
At my last company, "Documentation Specialist" was the highest level.=20
Pat
********
I was glad to see the old terminology of 5th level resurface, as I
believe it began originally within the Swiss organization, which did our
Tech. Comm. Certification years ago (I became certified while in
college). Another term which you may wish to consider is 'Information
Architect', which is very comprehensive. Basically, it means one who
designs any possible concept of information, starting with 'analysis' to
'post-implementation' phases, or even worse - 'postmortems' (if you
should be so unfortunate). An architect usually heads or leads a group
of designers (each with their own specialty). Much like this job
structure, an info. arch. heads or leads a team, or complements a team of
writers, developers, BAs (Business Analysts), and PAs (Program Analysts).
The I.A. oversees this process, and various procedures relating to
communications in any form, as well as the mechanics involved in its
processes.
Several years ago HR needed to define job descripts for the newly created
positions for writers, as well as a fee structure. I designed a format,
which included a title, job definition, experience level requirement ,
and pay ranges. The final outcome was a new roster of job titles which
were:
Contact/Agreement Specialist - deals in print medium, bidder, buyer, etc.
Copywriter
Technical Writer
Technical Documentation Trainer
Educational Writer
Creative Services Writer
Technical Communication Specialist (usually certified)
Information Architect (usually certified)
As an I.A., my particular specialty is in web weaving and 5th level
editing (an editor's editor more or less). The above titles had hourly
wages assigned to their positions, which helped HR quite a bit.
Actually, it helped the writers as it boosted their fee structure more
with the norm (with the aid of STC's Salary Forecast booklet). For the
folks in Corporate Communications and Marketing Communications, we
selected the 'Creative' aspect to differentiate their job roles. They
did not have the tight specificity regs hanging over them as did the
other positions. The Educational and Technical roles were definitely
standardized, information oriented.
