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.
Subject:Re: Reviewers who don't review From:beverly_robinson -at- datacard -dot- com To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Tue, 1 Aug 2006 09:04:04 -0500
Coming in late to this discussion because I'm on digest but . . .
I've used the hidden message technique (usually only the first time I work
with a development team) and it works. For the second and subsequent
reviews with that team, I start my review memos with "Win fabulous prizes!"
Every reviewer to sends at least one substantive comment gets his/her name
put into a hat. At the release celebration I pick a name from the hat and
that person gets the grand prize. In the early days, when I was funding the
prizes myself and all reviewers were local, the prize was a bottle of wine,
a plant, or a box of candy. I also gave an "early bird gets the (gummy)
worm" award--a package of gummy worms candy for the first review to hit my
in-basket. Everyone else got a candy bar as a consolation prize--and my
thanks as I came to their desks to have them choose from among the three
kinds I offered. After a few releases, when the team had gotten into the
habit of reviewing the user information, I was able to eliminate the game.
More recently my reviewers have been spread throughout the world so my
manager funds the grand prize from the department budget--a $50 (or
equivalent local currency) "on the spot" award. Sending candy bars all over
the world doesn't work well, so I've cut out the consolation prizes.
To be sure, there are some developers who still don't review the manuals.
Maybe they're offended by the silliness; maybe they're just too busy. But I
know that others were really impressed by the fact that I was serious
enough about the quality of my work to reward their efforts out of my own
funds. Your mileage may vary.
NOTICE ? This message and any attachment(s) are for authorized use by the intended recipient(s) only and may contain privileged or confidential information. Unless you are an intended recipient, you may not use, copy, retain, or disclose to anyone any information contained in this message and any attachment(s). If you are not an intended recipient of this message, please immediately contact the sender and delete this message and any attachment(s).