RE: What to look for in a technical editor

Subject: RE: What to look for in a technical editor
From: "Giordano, Connie" <Connie -dot- Giordano -at- FMR -dot- COM>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 22 May 2003 11:48:03 -0400

The last time I checked, I WAS the editor, desktop publisher, help producer,
and designer... And the curriculum developer, and the assistant webmaster,
the company's MS Office guru, and a sometimes QA analyst and Business
analyst... And even the evil marcomm expert. I LIKE it that way. So the
ideal situation for you, wouldn't necessarily work for other people.

There are a lot of us with the title "technical writer" who do not believe
that writing should be isolated from the rest of the communication
process... Or product development strategy... Or industry expertise. And
that's one of the reasons "technical writer" has become such a misleading
job title. We even wrote that up in my last review!

Connie P. Giordano
Senior Technical Writer
Advisor Technology Services
A Fidelity Investments Company
704-330-2069 (w)
704-330-2350 (f)
704-957-8450 (c)

If surrounded myself people in all necessary supporting roles, they'd be
calling me "Sybil"

-----Original Message-----
From: Mark Baker [mailto:mbaker -at- ca -dot- stilo -dot- com]
Sent: Thursday, May 22, 2003 11:09 AM
Subject: RE: What to look for in a technical editor


3. Precisely because, for complex products, it is hard to find suitable
candidates for technical writer positions, it is appropriate to surround
those valuable resources with supporting players such as editors, designers,
and desktop publishers who can relieve the writers of various burdens and
allow them to focus their scarce talents where they are needed. While it
would be ideal if all these supporting players also had the technical
knowledge that the writers need, it is probably unrealistic to hope to find
suitably qualified people. Supporting technical writers with non-technical
editors is therefore an appropriate strategy to maximize scarce resources.
However, work needs to be structured to recognize the limits of each of the
people involved.

Mark Baker
Senior Technical Writer
Stilo Corporation
1900 City Park Drive, Suite 504 , Ottawa, Ontario, Canada, K1J 1A3
Phone: 613-745-4242, Fax: 613-745-5560
Email mbaker -at- ca -dot- stilo -dot- com


Robohelp X3, from eHelp, lets you quickly and easily create
professional Help systems for all your Windows and Web-based
applications, including Net.

Order RoboHelp X3 in May and receive a $100 mail-in rebate, PLUS
free RoboScreenCapture and WebHelp Merge Module.

Order RoboHelp today:

You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.

Previous by Author: RE: Somewhat OT: Tech Writers vs. other writers
Next by Author: RE: Word 2002 + Watermarks + strange page numbering
Previous by Thread: RE: What to look for in a technical editor
Next by Thread: RE: What to look for in a technical editor

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

Sponsored Ads