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.
It's often difficult to get people to actually read the document you are
asking them to review. You might have insisted on working with the product
and interviewing the source people. This is the kind of information that
comes out in conversations and exercising the product. There are all sorts
of reviewers, and after some experience with a particular group, you come
to find out who your best reviewers are.
Stand over him? I have done that. But my first choice is to find a better
A review method that sometimes works is to hold a meeting with all
reviewers and turn the pages one at a time. This often spurs communication
among the reviewers, with lots of info coming out in the conversation.
<siliconwriter -at- co
Sent by: "TECHWR-L List"
techwr-l-bounces+ <techwr-l -at- lists -dot- techwr-l -dot- com>
om -at- lists -dot- techwr-l
Reviewers who don't review
A couple of weeks ago I created a quick start guide for our users,
sent it around for review, got signatures, and sent it through our
Document Control process, which garnered more reviews and more
signatures. It got packed with the product and sent to a user. Next
thing I know, I'm getting feedback from the field reps that the
default user ID and password are incorrect. I had no access to this
software while writing the guide, and relied on our field reps to
give me the information, then later to review it. Nobody mentioned
that the user ID and password had been changed. When I mentioned (a
bit testily, I confess) in email that the reviewers should have
caught this, I was told by the head of tech support (my main
reviewer) that he never looks at the documents he's sent to review,
and that I should walk them over to him and stand over him to get
them actually reviewed.
What am I, his mother?
Any suggestions as to a response? I am holding onto my temper with
both hands, as the field reps are now blaming me for this screw-up.
Am I responsible? What can I do to ensure that this does not happen
in future? I should point out that Tech Support Guy is frequently off
site and when he is here, is virtually always on the phone. If I
stood over him to get a review, I'd have to move into his cubicle.
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
The information contained in this communication is confidential, private, proprietary, or otherwise privileged and is intended only for the use of the addressee. Unauthorized use, disclosure, distribution or copying is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately at (312)653-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in Oklahoma; or (972)766-6900 in Texas.