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: What to do? From:"Anameier, Christine A - Eagan, MN" <christine -dot- a -dot- anameier -at- usps -dot- gov> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 28 Oct 2003 10:10:21 -0600
Geoff wrote:
> If their English is really bad, it makes little sense for them to
waste
> lots of time fixing their own grammar etc. They're hired to be
> engineers, not writers, and even some native English engineers
> never master the art of writing clearly.
This is a very good point. I always cringe when someone suggests
teaching an in-house writing class for engineers/developers. Are they
going to teach you engineering next? We're the writers; they're not.
They need to be able to communicate the information *to you* (whether in
person, on the phone, in email, whatever) but they don't need to form
spotless sentences for public consumption.
Personally, I tend to find it a lot easier to work with SMEs who don't
think they're good writers. They get a lot less bent out of shape when I
take what they gave me and rewrite every word of it. Make these folks
sit through writing classes, and they become more invested in their
writing; you still have to edit the heck out of it, but now they resent
you for messing with their new-and-improved prose (or else they wonder
why they had to sit through writing classes when you're still just going
to rewrite everything).
> . . . it may be far more efficient for you to do all the writing based
on
> facts gathered during interviews with the engineers. . . .
> If your editing burden is high, adopt a different approach than you
> might be less familiar with: Use their writing as source material
("just
> the facts"), and rewrite it from scratch rather than trying to edit
the
> text into submission. For really heavy editing, this is generally far
> more efficient (a better use of everyone's time) than more traditional
> forms of editing.
I think either of these approaches would be vastly superior to trying to
edit what they give you. The end result would probably be more coherent;
and you wouldn't be constrained by the discomfort of covering somebody's
prose in red ink (can you tell I've been dealing with a similar issue
lately?).
RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for
competitive pricing or download a trial at: http://www.ehelp.com/techwr-l4
---
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 http://www.raycomm.com/techwhirl/ for more resources and info.