RE: Technical Communication and GTD? (take II)

Subject: RE: Technical Communication and GTD? (take II)
From: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
To: "Gene Kim-Eng" <techwr -at- genek -dot- com>, "Technical Writing" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 13 Jan 2009 13:30:33 -0500

Don't "tell" them. Say it in e-mail. Send the same e-mail to all at the
same time.
All the e-mails should be identical, except the identity of the
person/project who has higher priority than the one being addressed by
the current copy.
And make the references circular, of course. If you can arrange a
moebius topology of prioritization, all the better. I've never been

(Joe gets a message saying that currently his project is higher in
priority than Victoria's, but lower than Cynthia's. Cynthia's message
says she's ahead of Joe, but behind Chuck. Chuck's says he's ahead of
Cynthia, but behind Victoria, and of course Victoria learns that she's
got higher priority than Chuck, but is behind Joe...)

If you have more than two competing projects, chances are small that
their leaders will all get together in one room to discuss what you said
to each of them separately. So they'll never know that the references
all go in a circle (or that moebious...)

Then stand back and watch the battle. When anyone approaches you to
make a decision, tell them that you would be happy to decide in that
person's favor, but you don't make policy, you just implement policy.
The principals must sort out priority among themselves and then present
you with the result of their deliberations (use that word; makes it
sound like something more elevated than the cat-fight that it will
actually be), so that you can know officially what The Company considers
its order of priorities.

If somebody gets demanding or nasty, say "Could you repeat that slower,
please? I need to the others know why their projects have dropped in
priority." Or, just smile and nod and after the bully has left, write
the e-mail and send to him/her, prefaced with "Is this what you wanted
me to understand from your visit to my office/cublcle this morning?"
You get to decide whether to CC everybody else right away, or to wait
until you have a reply that you can then pass on to all the other
project leads, accompanying your apology for their "demotion". Either
they'll acquiesce - in which case your bully friend was correct in
her/his estimation of her/his importance (or of the project's), or
they'll step up the battle, but at least others will come to you with
more than bluster when they finally do.

Oh, did I mention, have a sense of humor and a thick skin.

- Kevin

> -----Original Message-----
> From:
> techwr-l-bounces+kevin -dot- mclauchlan=safenet-inc -dot- com -at- lists -dot- techwr [mailto:techwr-l-bounces+kevin.mclauchlan=safenet->
inc -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Gene Kim-Eng
> Sent: Tuesday, January 13, 2009 12:21 PM
> To: Technical Writing
> Subject: Re: Technical Communication and GTD? (take II)
> If you *really* want priorities from above, tell the
> owners of every project you have that someone
> else is higher on your list than they are.
> Gene Kim-Eng
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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.


ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals.

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control!

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:


RE: Technical Communication and GTD?: From: Cardimon, Craig
Re: Technical Communication and GTD?: From: Milan Davidovic
Technical Communication and GTD? (take II): From: Geoff Hart
RE: Technical Communication and GTD? (take II): From: Cardimon, Craig
RE: Technical Communication and GTD? (take II): From: Sarah Blake
Re: Technical Communication and GTD? (take II): From: Gene Kim-Eng

Previous by Author: RE: Technical Communication and GTD? (take II)
Next by Author: RE: Technical Communication and GTD? (take II)
Previous by Thread: Re: Technical Communication and GTD? (take II)
Next by Thread: Re: Technical Communication and GTD? (take II)

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

Sponsored Ads