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.
Of course you cannot ensure people won't behave outrageously. That's not the
point really.
I think agreeing to the person's terms is not a good idea. The writer is
kept from productive work and babysitting someone who should be able to
perform his job without supervision.
Perhaps if his job performance requirements included, in writing, the
accuracy of the documentation, he would pay some attention. It is *his* job
that needs to performed right, and if I am the technical writer's manager, I
do *not* want her babysitting a grown man who needs to be financially
motivated to perform his job.
> -----Original Message-----
> From: Gene Kim-Eng [mailto:techwr -at- genek -dot- com]
> Sent: Monday, July 31, 2006 6:26 PM
> To: Bonnie Granat; 'Siliconwriter'; 'TECHWR-L List'
> Subject: Re: Reviewers who don't review
>
> There isn't a manager on the face of the Earth who can prevent people
> from making outrageous accusations or juvenile responses when some-
> thing goes wrong. If one of my writers was in this situation
> (not getting
> reviews or access to product) I would counsel him or her to do exactly
> what I suggest, if that didn't work *I* would show up at the
> reviewers'
> office or developers meetings with my laptop, thermos and protein bars
> and if *that* didn't work, I would officially remind everyone in the
> development process that somebody, if not my writer then somebody
> else, needed to actually fire up the product *following the document
> instructions* and verify that its contents were valid and that I was
> prepared to hold up release of the document until that happened.
>
> The only sure way to prevent the unacceptable responses to
> document failure is to prevent the failure in the first place.
>
> Gene Kim-Eng
>
>
> ----- Original Message -----
> From: "Bonnie Granat" <bgranat -at- granatedit -dot- com>
>
> > Tell your own manager exactly what you told us and ask your
> manager how he
> > or she would like you to proceed next time -- to "stand
> over" the person
> > or
> > to perform your job as you have been. If your manager says
> do the latter,
> > request that your manager get assurance that the next time
> will not bring
> > more outrageous accusations or juvenile responses.
>
>
>
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l