I have to agree with the point about valuing time. Since I'm a system administrator instead of a developer, how my company needs my times differ. It's not unusual to be contacted after hours on a thorny problem, or if one of my jr. admins can't handle a problem and it gets bumped up to me. So I really appreciate free time.

One fo the things I was trying to set up was a reward for "best documentation", since we were really lacking in that department from out developers. What we had was that best, as judged by peers, for the week got to leave an hour early on Friday. This added more then an hour of time, since Friday rush-hour traffic near my location is rather bad.

One hard thing is 'appropriate' rewards from both sides. Time is always appreciated, but from the PHB (pointy haired boss) side, that means that you're loosing time from your most productive people (the ones you want to reward). That's why gifts (tickets, gift certificates) and money are so often used - they are easy and don't have a negative aspect on performance. If I have one guy who can handle a problem, and he gets off, then there is no one covering, which is a problem.

One thing that can help is assigning projects. This may not work in a small shop, but in a larger one where there are lots of projects and lots of people, the "better" performers get rewarded by the more interesting projects. This takes a clueful manager (to understand what makes a project interesting), but works well in that you have people happy with what they are working on, and good people working on interesting (which can often be translated to "challenging") projects. Perhaps a choice among several good projects as a reward for finishing on well, but having that lassitude is rare.

One other thing is working environment - important performers get nicer laptops, etc. We give "management" level laptops (lots of bells and whistles) to important people. Makes 'em happy. Cubes with windows. But that is more long term and does have a definite seniority edge, as opposed to instant rewards for a well done job.

=Blue
...you might be eaten by a grue...

In reply to RE: Motivations by Blue
in thread Motivations by jcwren

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.