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.
We send documents for review to the analyst who wrote the spec. Since it's a
huge app and there are seven analysts working on different pieces, we write
a "content" document about each piece, which we send for
review/revision/approval. We incorporate the approved content into the final
documentation.
We get a rate of 100%, because we make them sign their name to it, attesting
that it is accurate to the best of their ability. We didn't used to ask for
signatures, and had about a 50% response rate. Once we added the sig line,
responses shot up. Very rarely do we have to chase down the analyst to get
it back. It also helps that the review stage is during their bug-fix stage
rather than during the heavy development stage. It also gives them a chance
to see how "the other guys" see what they've conceived.
Elisabeth B. Zakes
Austin, TX
> Okay, folks, when you send out material for review, what percentage do
> you get back fully reviewed? We're assuming a scenario where you send
> material out to various SMEs? If you like, include comments about how
> you've achieved that rate.
>
> Thanks. DB.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
