RE: More title questions

Subject: RE: More title questions
From: "John Rosberg" <jrosberg -at- interwoven -dot- com>
To: "Janice Gelb" <Janice -dot- Gelb -at- Sun -dot- COM>, "Techwr-l" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 27 Nov 2007 08:50:57 -0600

I agree with Ms. Gelb -- editing are two related, but distinct jobs --
the skill sets appear identical from a distance, but all on this list
can see the difference (one would hope.

Further, in a smaller to mid-sized technical company, the term "Editor"
(here in the States, anyway), might be perceived as something akin to a
"language janitor" (which is entirely false and incorrect), and would
likely result in a lessening of respect for the position, rather than
the reverse.

While some standardization around job classifications and titles would
be nice, I do not see the need for it, as Mr. Machhan does -- our
colleagues generally do not share identical titles and classifications,
and it seems to hurt them little, if at all.

The conversation surrounding job titles, job classifications, and who
gets called to dinner first comes up recursively in the tech comm
community -- I view these things as of secondary interest and import,
well behind understanding how our profession can bring value to our
businesses in a real and measurable way.

Though, as always, your mileage may vary ;-}


-----Original Message-----
From: Janice Gelb [mailto:Janice -dot- Gelb -at- Sun -dot- COM]
Sent: Monday, November 26, 2007 3:27 PM
To: Techwr-l
Subject: Re: More title questions

Raj Machhan wrote:
> Editor as a designation has its moorings in the print media. It is
> used to describe the pecking order in newspaper and magazines. So we
> sub-editors, deputy editors, assistant editors, associate editors and
so on,
> with the editor-in-chief as the top boss. However, the job profile of
> editorial positions (excluding the overworked sub-editors, who lie at
> bottom of the pile) also involves a fair amount of writing.
> I do not see any reason why we cannot apply the same structure, in a
> way, to positions in a Technical Communications set up. So instead of
> having designations such as "technical writer editor", or "technical
> and editor" we could simply put it as "technical editor", "sr
> editor" and so on. The designations need to be standardized to avoid
> confusion.

My job is that of a technical editor and although
I have written some of our internal tools documentation
manuals, that is not my primary job function. I imagine
the writers on here will object as much as I do to a
job title that implies that their primary function is
to edit! Editing and writing are different jobs with
different responsibilities and although often people
must do both in their working environment, that doesn't
mean that the titles can or should be combined.

I don't think that writers who occasionally do peer
editing to catch overlooked obvious errors because their
company does not employ editors should append "editor"
to their titles. You only need to invent a hyphenated
or slashed title if your editing responsibilities are
equal to or on the same professional standing as your
writing responsibilities.

-- Janice

Janice Gelb | The only connection Sun has with
janice -dot- gelb -at- sun -dot- com | this message is the return address


Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more.

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Re: More title questions: From: Janice Gelb

Previous by Author: RE: STC Salary data collection
Next by Author: Re: 'Adobe PDF' problem with Word
Previous by Thread: RE: More title questions
Next by Thread: RE: More title questions

What this post helpful? Share it with friends and colleagues:

Sponsored Ads