TechWhirl Sponsors

About TechWhirl

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.

<snip>Will XML lead us in 20 to 25 years, or will we TWs lead XML?
Again, Steven's comment about focusing only on content just caught my eye.
Thoughts?<snip>

As a profession, I do not think that we are on the verge of extinction. Over
the years, I have seen a change in the profile of a Technical Writer. There
was a time when a Tech. Writer understood (in depth) one or more of the
fundemental disciplines: Electronics, Hydraulics/Mechanical, Digital
Circuits, or Chemistry. A writing tool was a tool, that's all. Today's arena
seems to focus on the tool.

When one hires a plumber, does one care that he/she is using Crescent wrench
version 5.0, or that he/she has the skills to perform/explain the task at
hand? Does one care that a doctor uses an EKG controller version 2.0, or
that he/she can diagnose and correct the heart condition. I think we care
that the professional adds value to the project.
For example, if I can obtain the instructions on how to use an automotive
GPS written on a handkerchief, the instructions are clear and concise, and I
arrive safely at my destination the Technical Writer that wrote the
procedure/description has met the objective.

The more that the documentation group's capital requirements involve
epicurean solutions and short lifecycle tools, the more venture capitalists
will look at other alternatives to reduce/eliminate documentation costs and
devalue documentation. When documentation groups are eliminated, ask
yourself if the documentation added any value to the product. Did the
document reduce the lifecycle cost of the product, which the customer is
willing to fund in order to mitigate operational expenses? Did the
documentation reduce manufacturing costs (Standards ... Compliance ... Bah,
Humbug!!)? Did the documentation give the product a competitive advantage?
If you answer NO to these questions, be prepared for a long wait at the soup
kitchen.

In the economy of present (an probably the same hold true for the future),
corporate goodwill has taken a backseat to quarterly ROI. When one takes a
Technical Writing job, it's not a free lunch - eventually the function will
be phased out if there is no business case for continued document
development. If you can squeeze lead your hands and turn it into gold, the
Technical Writer will always survive (in other words put on your Marcomm hat
and turn losses into profits). Without giving away all of my secrets ;-D ,
creating a documentation demand "pull" (customer demands documents (based on
THEIR needs), rather than company pushing documents to market), can be a
catalyst for survival. Personally, I have never been layed-off from an
organization (11 years in the industry). Maybe it's pure luck, or maybe it's
adopting NPV 'ology' to my documentation projects.

######################################################################
This e-mail message has been scanned and cleared by MailMarshal http://www.marshalsoftware.com
######################################################################

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Announcing new options for IPCC 01, October 24-27 in Santa Fe,
New Mexico: attend the entire event or select a single day.
For details and online registration, visit http://ieeepcs.org/2001