RE: Tech Writer Lawsuit - follow up?

Subject: RE: Tech Writer Lawsuit - follow up?
From: "Donald H. White" <dwhite -at- jrtcllc -dot- com>
To: "'techwr-l List'" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 22 May 2008 13:28:45 -0400

"Telling Our Powerful Story"

This has been broadcast as a major element of Society programming since the
realignment/reconstruction/reorganization project, dating to 2003, I think.
However, there has never been anything of substance behind the title slug.

Now, we learn that STC is "still developing" the "messages" in support of
the theme, "Telling Our Powerful Story?" <ahem>

I thought we are communicators--"technical communicators," to be precise.
Can our Society not come up with the substance of a public relations
campaign? In, what, five years?

The Society petitioned the Bureau of Labor Statistics to upgrade the
classification and description of technical communicators. Yet, the Society
cannot develop a rationale for "our powerful story?" Rhetorical questions,
certainly. I don't think them sarcastic; I'm more frustrated than sarcastic.

I expect leaders to lead. If our Society establishes and publishes a program
to serve as a compass for the profession, all elements of that program
should be in place. Certainly, any element can, and will, be modified with
time and through experience. When leaders cannot develop a mission statement
for the organization that supports a profession, something is awfully wrong.
Perhaps something like: "Further the profession and professionalism of the
technical communication arts" would suffice. The statement could go further,
of course. And it can include all aspects of technical communication without
specifying each.

A good example of a mission statement for an organization that supports a
wide variety of fields is that of the Project Management Institute:


Still, it's not quite clear to me why the Society is reluctant to issue a
press release concerning the issues involved with California law and
compliance with it as regards technical writers because it doesn't have its
story ready to support "Telling Our Powerful Story."

Donald H. White
James River Technical Communications LLC


Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more.

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity!

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.

Tech Writer Lawsuit - follow up?: From: Geoff Hart

Previous by Author: RE: Tech Writer Lawsuit; STC position? (take II)
Next by Author: Question re: font issues from MS Word to Adobe FrameMaker
Previous by Thread: Re: Tech Writer Lawsuit - follow up?
Next by Thread: Tech Writer Lawsuit

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

Sponsored Ads