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.
: What you're talking about here is butt coverage. And I ain't talking
: about capri pants. When I send out a document to development for review
: (and I endeavour to ensure there's time in the development schedule for
: reviewing docs), I include a disclaimer, which reads something like
: this:
:
: Please review the following document for technical accuracy and send
: your comments to us by <date x>. If you cannot review this document by
: <date x>, please notify us as soon as possible. If we don't hear from
: you by <date x>, the document will be assumed to be 100% accurate as is.
:
: This tends to emphasize to reviewers whose court the responsibility ball
: sits in. Cheers. DB.
:
This is nearly exactly what we did at Artisoft. It worked well, up to a point.
Many reviewers didn't really check the docs for accuracy, though. But once
again, that's a management problem, not a writer's problem, and I'm glad to
see that other organizations recognize this. Bad managers keep bad employees,
and bad managers are the root of poor documentation.
---
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.
