RE: Technical writing in the development process

Subject: RE: Technical writing in the development process
From: Diane Haugen <WhiskeyCreek -at- wcdd -dot- com>
To: "Joe Malin" <jmalin -at- tuvox -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Sun, 25 Jun 2006 19:27:02 -0500

At 4:15 PM -0700 6/25/06, Joe Malin wrote:

I think, though, that to be part of the collaboration, we have to
establish our credibility. We have to show that our opinions about the
process and the result are based on solid facts and experience. In other
words, we have to be either "engineers" or "marketeers" or both.

You are absolutely right that you have to be a good marketer. The only way to convince those in charge of the development process that the technical writer does make a product more valuable is to tie it to the profit stream.

Mitsubishi only hired document designers to write their manuals when they finally realized that they could not reach their non-techie market without better manuals.

I keep dreaming about the day when what technical writers do could begin to be recognized for its inherent value. Be recognized as a valuable contribution to the development process without having to show a dollar-and-cents reason for it. This is the old art versus craft argument.

As physicists find that there is more and more reality out there that can't be measured in terms we are familiar with, it seems to me that the knee-jerk reaction for checklists should be diminishing. Is there anyone in this field of technical writing who has observed some signs that there might be such a shift is in the future?


Diane Haugen
Whiskey Creek Document Design

WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content delivery. Try it today!.
Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -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 lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

RE: Technical writing in the development process: From: Joe Malin

Previous by Author: Re: Technical writing in the development process
Next by Author: Re: Converting embedded Word Images
Previous by Thread: RE: Technical writing in the development process
Next by Thread: Michal Zarif/AME/APPLIED MATERIALS is out of the office.

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

Sponsored Ads