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.
I just had to jump in here, for what my $.02 is worth . . .
Nora Merhar writes
-We do try to field trial the documents, by which I mean that we
-send the docs
-out with the product for the field trial. We never get any input
-this way.
-Anybody have any ideas on a better way to field trial
-documentation?
We have a rather small user audience, so this will obviously not
work for lots of folks (probably *most* folks), but in our case, the
documentation is used for training the engineers. I get to sit in
on the training session, and hear comments like "We should include
xxx in the doc" or "I'm glad to see this in here; it's helpful." As
engineering training is usually done for a small group who will be
using the software and equipment in beta test, I get to
correct/update the documentation before it goes to press, which
results in a better doc.
Barbi Harrison
harrison -at- tulsa -dot- dowell -dot- slb -dot- com
(yes, that's in OKLAHOMA! :-) )
