RE: Address this. . .

Subject: RE: Address this. . .
From: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
To: "Boudreaux, Madelyn (GE Healthcare, consultant)" <MadelynBoudreaux -at- ge -dot- com>, TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 12 Mar 2010 17:12:52 -0500

Boudreaux, Madelyn subjected us to:
> I write this partly tongue-in-cheek, in the vein (or maybe the key) of
> Friday...
> It seems to me that "address" being taken to mean "fix" is a
> case of the
> jargon chickens coming home to roost.
> People used to call problems, bugs, etc, "problems," and
> "bugs," and we
> "fixed" or "solved" them. But somewhere along the line, it was decided
> that we can't admit to having "problems" or "bugs," so we started
> calling them "issues." Or "opportunities," my *favorite*.
> (Ooh, where's
> my sarcasm tag?) But you can't "fix" an issue, so we have to "address"
> it instead.
> So while we used to "fix bugs" and "solve problems," now we "address
> issues."
> A customer who, presented with a list of "issues to be addressed," may
> be doing the wordmath in his or her head and thinking, "That must mean
> they're going to fix this bug."

Do you think ANYbody but a techwriter -- or those weird
folk over on CE-L actually thinks that way?


Anyway, we use "issues" because it covers more than bugs,
including feature requests, updates due to agency farts (*),
EOL-related ... concerns, some others I can't recall just now.

But then, look at the new post from Jeff S, two posts above
yours, wherein he's having ... um... "some issues" with
FrameMaker. Not problems, though.


- Kevin

(* You know, when they roll over ponderously and expell some gas...)

The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.


Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial:

Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at:

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.

Please move off-topic discussions to the Chat list, at:


Address this. . .: From: McLauchlan, Kevin
Re: Address this. . .: From: John Posada
Re: Address this. . .: From: Kerstin Peterson
Re: Address this. . .: From: Tony Chung
RE: Address this. . .: From: Boudreaux, Madelyn (GE Healthcare, consultant)

Previous by Author: RE: After all, it is Friday...
Next by Author: RE: Address this. . .
Previous by Thread: RE: Address this. . .
Next by Thread: Re: Address this. . .

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

Sponsored Ads