The technical review can be a source of annoyance and contention, or it can hone your technical communications into precise targeted documents that help customers solve a problem, help products pass quickly through a regulatory review, or help the sales force quickly understand the product. Here are some guidelines for a smooth technical review process.
Have a process and a schedule. Do you scramble to write documentation just before a product is ready to ship, or just before an important regulatory review? If so, you are asking for technical reviews at crunch time — exactly the time when subject matter experts (SMEs) are least able to provide thoughtful input. Design a process that allows writers to attend early meetings and write early drafts. Build in reasonable time for reviewers reasonable timeframes to review the documents. Give writers reasonable timeframes to revise the documents.
Get “Buy-in.” The main reason that subject matter experts do not want to participate in technical reviews is lack of time. If they don’t understand why they are asked to review a document, they will not want to use valuable time to do it. Announce the process, make sure that people are aware that they will be asked to review documents. Emphasize the reasons why you are asking for a review. For example, technical reviews are important because:
- The technical writer sees the product from the end user perspective. Reviewing the document may identify missing, incomplete, or ambiguous information. A technical review can help find problems before customers do!
- A good technical document will bring regulatory approval more quickly than products with missing or vague documentation.
- Good technical communications will help sales by making products easy to understand and use for the sales force, and for customers.
- A good technical document will reduce the time, effort and money your company spends troubleshooting or supporting your product.
Provide clear instructions for the review. Provide a detailed summary about what you expect from the review. For example, “Please review this document for accuracy — the document will undergo a complete copy edit prior to publication.” This way, you will get substantive comments, rather than quibbles about punctuation or layout. Clear instructions can point out problem areas so reviewers can focus on new, or complex material. I like to provide a checklist to help guide reviewers to the kind of review I need. This saves time for everyone.
Establish Accountability. Indicate when the review comments are due, and why. Also, it helps to be flexible where it is impossible to review the document within the requested timeframe. Depending on the situation, the writer and SME can agree on a new date. If an SME is not able to review the document within your timeframe, ask them to designate a reviewer who can review the content in the same capacity (e.g., Marketing, Regulatory, etc.). SMEs who don’t notify the writer or designate another reviewer should understand that their comments will not be incorporated.
A smooth technical review process is an essential part of the product life cycle. With an understanding of your engineering process and good planning, good reviews will become routine.




