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.
My reaction to this story is that if someone signs off on something to say
that he or she has reviewed it, then that's exactly what it is supposed to
mean. If that one person signing off on it is supposed to mean 'well, he
signed off on it but for him it does not mean that he did a proper review'
then I'd say that it does not look like you did not coordinate the review
properly. Rather, it seems that the one person did not perform his review
I don't think that you should be in the position of having to accept
... 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....