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.
Annie Wood wondered: <<We are currently reviewing our documentation
processes and are looking to get some feedback about how other teams/
companies handle reviewing their documentation.>>
There's a bunch of useful stuff on my Web site: http://www.geoff-
hart.com/resources/bibliography.html
<<Do you have a process for reviewing/testing/proofreading
documentation?>>
We've had one everywhere I worked. Lessons learned are discussed in
the various references on my site.
<<What do you review in the documentation? Content, grammar, layout,
style (both wording and/or applying templates), or functionality of
the Help (other documentation)?>>
All of the above, plus other useful things like clarity, accuracy,
and completeness.
<<Who reviews the documentation? Another technical writer, editor,
proofreader, SME?>>
Anyone with a stake in the outcomes or the ability to improve the
quality of the final product. For more details: http://www.geoff-
hart.com/resources/2005/reviews.htm
<<Do you use any sort of defecting tracking software?>>
Not generally. We did keep old file copies showing what changes were
necessary as a result of review, but the goal was more to help people
learn the kinds of things they were missing than to punish anyone.
With software, the developers did indeed keep track of bugs and other
problems in a database of some sort.
<<Do you provide the reviewer with anything explaining the changes in
the documentation?>>
This kind of discussion is an important part of any review process,
since it builds a sense of teamwork and cooperation--at least if done
right. <g>
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! http://www.webworks.com/techwr-l
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList