Friday, September 05, 2008

Finding ways to motivate productive behavior

My wife and I have always wanted to reward our employees well for good (i.e., productive, profitable) behavior. But coming up with a bonus plan that might actually achieve that end is hard! With these thoughts in mind, then, you can imagine how excited I was to find this article about "Farmer Smith" and the economists he hired to help him optimize his pay plan.

Smith had been paying a piece rate—a rate per kilogram of fruit picked—to his fruit pickers, but he had come to the conclusion that his pay plan wasn't working the way he wanted . . . or, perhaps, the way the workers themselves might have preferred (???).
Farmer Smith tried to adjust the piece rate each day so that it was always adequate but never generous: The more the work force picked, the lower the piece rate. But his workers were outwitting him by keeping an eye on each other, making sure nobody picked too quickly, and thus collectively slowing down and cranking up the piece rate.

In the first year, the economists' proposed pay scheme "increased productivity (kilograms of fruit per worker per hour) by about 50 percent."
The next summer, the researchers turned their attention to incentives for low-level managers, who would also be temporary immigrant workers but who would be responsible for on-the-spot decisions such as which workers were assigned to which row. The researchers found that managers tended to do their friends favors by assigning them the easiest rows. This made life comfortable for insiders but was unproductive since the most efficient assignment for fruit picking is for the best workers to get the best rows. The researchers responded by linking managers' pay to the daily harvest. The result was that managers started favoring the best workers rather than their own friends, and productivity rose by another 20 percent.

Small wonder that the economists were invited back for another summer. They proposed a "tournament" scheme in which workers were allowed to sort themselves into teams. Initially, friends tended to group themselves together, but as the economists began to publish league tables and then hand out prizes to the most productive teams, that changed. Again, workers prioritized money over social ties, abandoning groups of friends to ally themselves with the most productive co-workers who would accept them. In practice, that meant that the fastest workers clustered together, and again, productivity soared—by yet another 20 percent.

How far can this kind of improved efficiency go? We don't know. After three seasons, the economists figured they had run out all the improvements they were going to get. Farmer Smith, on the other hand, has now hired a consultant to try to continue to improve his workers' efficiency.

If this research is of interest to you, I would recommend you not only read the original article, but the more scholarly University College London papers referred to within it as well: The Evolution of Cooperative Norms: Evidence from a Natural Field Experiment and Incentives for Managers and Inequality Among Workers.

1 comment:

  1. Hi John!

    This blog entry from last Friday reminded me of a couple of articles I read recently... some time in the last few weeks. Thought you would be interested. (I don't recall how I ended up getting to them... maybe from one of your earlier posts???)

    Assuming you haven't seen them already, here are the links:

    The first, and most relevant one, is an article about appropriately rewarding team-effort. It's titled "UnJust Deserts." (It's not entirely clear to me whether they really meant Deserts or possibly misspelled Desserts, although I really do prefer the title as it's actually written.)
    http://www.poppendieck.com/pdfs/Compensation.pdf

    The second article is what lead to the article above. It's about the need for properly and clearly identifying the true scope of a project prior to giving estimates of how complete it is. It's titled "Coding Horror: On Our Projects We're Always 90% Done"
    http://www.codinghorror.com/blog/archives/001161.html

    ...

    One other recommendation that comes to mind when discussing employee/management relations is the book, "Management: A Biblical Approach" by Myron Rush. Available at:
    http://www.amazon.com/Management-Biblical-Approach-Myron-Rush/dp/0781437458?ie=UTF8&s=books&qid=1220911994&sr=8-1
    The part that really jumped out at me, and has stuck with me for quite a long time, was where he went into the difference between management as taught in business schools (and many businesses) and what he saw as the biblical model of management.

    Traditional model:
    Management is: Getting work done through others.

    Biblical model:
    Management is: Providing the necessary resources to help others accomplish the work they've set out to do.

    In the Traditional model, the employees feel devalued: "We're the brawn; you're the brains." And the managers feel threatened: "If I'm not better than them at doing the work, then they'll take over my job."

    In the Biblical model, the employees are empowered: "We have a role to play in creating a more enjoyable and effective work environment." And the managers are freed to hire superstars for each position, and then get them whatever resources they can to help them work more efficiently and effectively.

    ReplyDelete