re: Documentation Procedures

Subject: re: Documentation Procedures
From: "Christensen, Kent" <lkchris -at- sandia -dot- gov>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 30 Oct 2001 10:02:46 -0700

re: This book touches on all the main things you'll need to consider (e.g.,
choosing tools, creating style guides, scheduling and planning projects, and
building a doc group), then provides a nice resource section at the back for
more detailed information.

This is cool, but it would be kind of sad if this is all there is. And if
it's considered most important, i.e., the "main thing."

I'd offer as answer to the original question--help in setting up a
documentation department--that the first priority is establishing people
relationships ... with customers. Both customers; the SMEs and the ultimate
customers, i.e. users. How will SMEs and writers communicate? Will there
be user testing of draft documentation? Will the group publish FAQs based
on customer response? Stuff like that.

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

Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.

You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.

Previous by Author: RE: QUERY: Meaning of "Real-Time editing funct
Next by Author: Re[2]: Don't you love farce?
Previous by Thread: RE: Documentation Procedures
Next by Thread: RE: Documentation Procedures

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

Sponsored Ads