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.
Subject:Re: FW: Everybody's a Reviewer From:"Virginia L. Krenn" <asdxvlk -at- OKWAY -dot- OKSTATE -dot- EDU> Date:Tue, 15 Oct 1996 11:38:59 -0700
Brent, I agree with what you have said here and had wondered why the
original author was upset. But then it occured to me that she may have
been feeling threatened at the thought that perhaps her boss didn't have
enough confidence in her abilities.
______________________________ Reply Separator _________________________________
Subject: Re: FW: Everybody's a Reviewer
Author: Brent Jones <bjones -at- igs -dot- com> at SMTP
Date: 10/15/96 10:27 AM
Why *shouldn't it happen? I'm not sure why so many folks are proposing
methods for avoiding or sabotaging this review. I've seen other threads from
folks bemoaning the fact that they can never get input from developers and
SMEs on their docs. Well, which is it? It seems to me that:
1) If it's a good, solid document the input will probably be minimal.
Remember that the reviewers are probably busy too, and don't want to waste
either their time or yours with unimportant edits.
2) The QA and R&D folks are perfect reviewers, and are in a position to
offer really solid input. If your boss was suggesting that Marketing or HR
review it, that would be different.
3) All of this passive/aggressive stuff along the lines of "pretend to do it
but make it such a hassle that it will never happen again" is the true waste
of time. And will probably backfire, making everyone wonder why the
technical writer can't orchestrate a simple review more effectively.
Yes, I said a simple review. I've worked at places where 30+ people had to
sign off on every draft. It's often part of the gig, and even though it
sometimes revolves more around a CYA mindset than an interest in quality
docs, occasionally you have to live with it. So either do what you can to
make it a useful, positive experience that improves the document, or
convince your boss that it's not a good thing to do. To be honest, I can't
imagine many good arguments for the latter, other than that delivery date
slip will occur to allow the review and the incorporation of edits.
I think the real problem here is that your boss sprung it on you at the
last minute. He should understand that it will impact the dates.
Hopefully not because you make it a labyrinthine process designed to
frustrate everyone involved and ensure that it won't happen again, as
some have suggested you do, but because a new task inserted into an
established timeline obviously increases the timeline. And he should
understand that you'd like to know about major process changes earlier
in the cycle next time.