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.
What I or anyone else here means by "addressing" something is totally irrelevant. The only thing that matters is what the customer and your lawyer(s) agree it means.
This is not your problem. You are just the guy who wrote the words. Their meaning and how the company applies them and deals with this customer are decisions that must be made at higher levels.
ISD and training maven,
Technical document wizard,
Process/decision flow chart Rembrandt,
Organizer, planner, and all around useful person.
--- On Fri, 3/12/10, McLauchlan, Kevin <Kevin -dot- McLauchlan -at- safenet-inc -dot- com> wrote:
> From: McLauchlan, Kevin <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
> Subject: Address this. . .
> To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
> Date: Friday, March 12, 2010, 9:55 AM
> I'm getting push-back on some standard language in our
> Release Notes.
> In the list of issues/bugs that are not being fixed for the
> release, we say "To be addressed in a future release".
> We carefully don't even say "next" release.
> But the problem is the word "addressed".
> Some customer has decided that "To be addressed in a future
> means "...an explicit prmise that the issue is to be fixed
> exactly how I want it".
> I have labored under the illusion that to "address"
> is to turn your attention to it. To pick it up and make a
> decision, and _possibly_ act on it.
> So, as far as _I_ am concerned, we "address" issues by
> deferring them,
> by delaying them, by deciding that they are not worth
> doing, and even
> by deciding to FIX something... and fixing it. But,
> as far as I'm
> concerned, as a native English speaker, all of those other
> are ALSO, just as validly, "addressing" the issues.
> It's like prayer (if one is religious):
> God always answers prayers.
> Sometimes the answer is no.
> Please tell me what you believe is meant by "to address
> - Kevin
> PS: "The customer is always right" is not a helpful
> The information contained in this electronic mail
> may be privileged and confidential, and therefore,
> 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
> produce desktop, Web, or print deliverables. Just write (or
> and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
> Explore CAREER options and paths related to Technical
> learn to create SOFTWARE REQUIREMENTS documents, and
> get tips on FUNCTIONAL SPECIFICATION best practices. Free
> You are currently subscribed to TECHWR-L as klhra -at- yahoo -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit http://lists.techwr-l.com/mailman/options/techwr-l/klhra%40yahoo.com
> 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-
>http://www.techwr-l.com/ for more resources and info.
> Please move off-topic discussions to the Chat list, at:
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: http://www.doctohelp.com
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: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-