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.
> Before I get totally hysterical, maybe somebody has been in my situation...
> I have just finished writing a manual which is quite good. It's been through
> three reviews with the SMEs and all their corrections have been entered.
> It's also been edited by two technical writers (that's all we have). Now that
> I am all ready to go to press, the approval board (my boss) has come up with
> a creative idea: The entire R&D and QA staff has to read the entire book.
> I have never heard of this kind of procedure before and it sounds to me like
> the world's biggest nightmare, but my boss refuses to budge. Can anybody
> give me some good arguments why this shouldn't happen. When I noted
> that this is an expensive use of the programmers' time, he said, "You just let
> me worry about that."
> Help...
> Dear Anonymous,
I think its great that someone in authority actually TELLS AND DEMANDS
that others review the book. No problem for me.
My $.02.
Take control of the review project. Be proactive, not reactive. You have
an opportunity to make your light shine and show how you can manage the
review process.
