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 am curious about the review process for different tech writing
departments. Over my career, reviews have been handled many ways;
sometimes by other writers, sometimes by the test team, and sometimes by
programmers. On rare occasions I've worked in places where there are no
reviewers prior to customer release.
How are reviews handled in your office? Who conducts the reviews and
how much time do you typically give a reviewer? Do you have separate
reviews for content and grammar/layout? Also, is your documentation
reviewed/tested alongside other software or hardware artifacts?
Also, where is your tech writing department in the hierarchy of your
company? (I'm asking because I think this sometimes impacts reviews and
possibly the quality of reviews.) For example, is your department
separate from others, are you part of the programming department, or are
you grouped with the QA or marketing departments?
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
