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: Motivating/awarding co-workers for edits... From:Laurie Rubin <lmr -at- SYL -dot- NJ -dot- NEC -dot- COM> Date:Wed, 28 Jun 1995 15:27:34 -0400
I recently tried before and after incentives that I gathered from this list:
I attached a lollipop (I used blow pops and tootsie roll pops) to each
doc for each reviewer. To get the reviews back (at all, as well as quickly)
I made available donuts to everyone who gave me the review by a specific date.
Food is a great incentive to almost anyone!
Laurie
> PCarman <HARRIS -dot- PCARMAN -at- IC1D -dot- HARRIS -dot- COM> asks-->
> I was curious if any of you have any sort of motivational/award system
> for rewarding your co-workers for the edits they provide.
> For example, finding the most errors, returning edits on time, and
> providing the most information from the get-go.
> My co-workers and I would like to set up some sort of positive reward
> system, and we would like to know if you have ever worked with
> anything like this.
> =========================
> Just some comments:
> 1. Finding the most errors. Not good because what if John is the
> best writer you've got and Jane could use some improvement.
> Whoever is *lucky* enough to be assigned Jane's work to edit will
> most likely amass the most errors found.
> 2. Returning edits on time. This could work as long as there is
> some kind of consistent gauge used to assign suspenses.
> Otherwise, referring to the previous example, the person
> *unlucky* enough to edit Jane's work may more often miss
> suspenses.
> =*= Beverly Parks =*= bparks -at- huachuca-emh1 -dot- army -dot- mil =*=
> =*= "Unless otherwise stated, all comments are my own. =*=
> =*= I am not representing my employer in any way." =*=