Penny Orwick and I completed a series of posts for Steyer Associates on peer reviews for technical documentation.
A point we both made in our example peer reviews was that the original draft content wasn’t ready for review, much less for publication. To wrap up our series, Penny suggested a checklist.
Today’s Ready for Review? A Checklist provides the basics, plus some cautionary notes about what you risk losing if you send poor docs for tech review:
- Discrediting yourself with your technical experts
- Discrediting yourself with your peers
Typically I link to my tech-communications blog topic with a parallel for fiction writers. But it seems like there are a lot of models out there. So this time I’ll just link again to my Checklist for Writer/Editor Collaborations.
Other topics in our “peer review tips” collection:
- Lions and Tigers and Peer Review—Oh No! (Apr 2014)
- Peer Reviews in Technical Communications: An Example (Penny, June 2014)
- Peer Review Redux (June 2014)