Peer Review Process/Best Practices

Subject: Peer Review Process/Best Practices
From: "Jill Mohan" <jillemo -at- gmail -dot- com>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Tue, 26 Feb 2008 15:56:13 -0500

This question may provoke only laughter - BUT, here goes...

Is there anybody out there using a slightly formalized process for getting
documents reviewed prior to delivery? If you are, can you share some best

Here is what we do currently - perhaps you could find remedies for glaring

Current state is -

1. I send out a doc to a mixed team of talent and suits.
2. Get silence for weeks.
3. I work the charm offensive going desk-to-desk asking for feedback
on areas that match expertise of desk's occupant.
4. Trickle of feedback comes in from the charmed.
5. I incorporate that feedback and recirculate the doc.
6. Another few days of silence.
7. Deadline gets moved up on system's delivery.
8. Team asks for another copy of the doc.
9. Various members demand changes to the system's interface or
functionality due to things they hadn't noticed until they read said
10. Engineers get the changes made.
11. Suit suddenly appears and makes changes to "formalize" the crap
out of a user's guide.
12. I try to aggregate five to six different reviewer's notes -
deciding on importance and relevance.

Thanks much,
Jill Mohan

Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more.

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.


Previous by Author: Michael Bremer's "UnTechnical Writing" book
Next by Author: Change Management dilemma (Install Guide v. Software Updates)
Previous by Thread: RE: Word to Frame Tool?
Next by Thread: RE: Peer Review Process/Best Practices

What this post helpful? Share it with friends and colleagues:

Sponsored Ads