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.
RE: What do you do when you don't have anyone with the time to reviewand edit your docs
Subject:RE: What do you do when you don't have anyone with the time to reviewand edit your docs From:"Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 19 Jan 2010 08:20:05 -0500
I use customized voting buttons on Outlook, outside the actual review
process: "I have reviewed it and passed it on; I have it now; I haven't
received it yet..." etc.
The shared e-mail update reinforces the team aspect of the review
process -- no easy task, since each person reviews the documents alone.
> -----Original Message-----
> From: Bill Swallow
> Sent: Monday, January 18, 2010 7:44 PM
> To: Wade Courtney
> Cc: TECHWR-L
> Subject: Re: What do you do when you don't have anyone with
> the time to review and edit your docs
>
> I always send my material for review in chunks, set a
> deadline, cc the appropriate managers, and set electronic
> reminders. I also follow up in person early on in the review
> cycle, mainly as an unspoken reminder that a real live person
> does in fact depend on them to review the info. If there's no
> traction, the managers are contacted for a nudge.
> If that doesn't work, I escalate.
>
> Generally I try to avoid any form of conflict by planning the
> reviews early on, identify the reviewers early on, and give
> everyone involved a heads-up and set the expectations with
> them. I treat them as part of the project, not part of the
> process, because... well, they are!
>
This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-