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: Peer edits From:Bob Jones <Bob -dot- Jones -at- PAREXEL -dot- COM> Date:Wed, 22 Oct 1997 15:25:01 -0400
I got another message similar to yours yesterday, so I
have a prepared response:
Your ideas about how these meetings can go is pretty
accurate. I led these review meetings for seven
manuals and sat on three other review meetings. They
can be deadly. Did I mention that you get a free
lunch for participating?
One of the things that keeps these meetings from
becoming a committee is that the project leader must
be dictatorial -- you listen to what others have to
offer and you make a decision. If the review meeting
becomes like a committee then nothing gets done. One
of the benefits of the meetings that I remember is
that we were finally able to get rid of a standard
section of front matter that had clung to our
documents for years -- no one writer working alone
would take responsibility for cutting it.
Becky, this process was the only way to finish a bunch of
books that wouldn't die. I wouldn't want to do it often,
but I needed to I would.
______________________________ Reply Separator
Subject: Peer edits
Author: Rebecca Carr <rebecca -at- WHITE -dot- SC -dot- TI -dot- COM> at
Date: 10/22/97 01:02 PM
Surely you jest! Read the book aloud...."perfect text"???
What planet are you from and who has this kind of time?