6: Performance=Results

We take accountability to meet commitments and deliver services better, faster, cheaper.

"Results" are a funny thing. The more you get them, the more you want them. The more you see them around you, the more you aspire to have them yourself. But "results" are terribly misunderstood and misrepresented.

Let's take a quiz. Which of the following are results which equate to a stellar performance?

Employee...

  1. finds a problem with a production system. he doesn't get it fixed but stayed all night to try. 

  2. is consistently at work before 7:00am and consistently leaves after 6:30pm. never takes vacation.

  3. is well liked by customers despite managing a team of people who aren't able to deliver.


Answer? None of the Above.

Performance=Results. Trying is wonderful, but doesn't serve a purpose when attempting to build and develop effective people. We hold ourselves and others accountable to real performance measures, not just our perception of how hard they "tried." This allows people to know where they stand and where they need to be in concrete ways.

Don't get me wrong. Holding people accountable for performance is hard--especially at the Church. But it's a critical thing which pays dividends.

A manager does his employees a disservice by not being accurate in performance appraisals, and by over-rewarding "effort" instead of "results." I had a guy work for me for a few years who frankly only worked 20 hours per week. He also was quite an annoying person to be around. But he delivered. He delivered big! I wasn't interested in his (lack of) effort. I was interested in his results and he delivered! The hours thing never bothered me, though it bothered some of our team members. My advice to them is (and was) get over it! If you want that kind of leniency, then deliver!

"Trying" or "going the extra mile" does have some benefits which are important.

  • It's motivational to the rest of a team.

  • It can help you keep a positive outlook.

  • It keeps you focused on "hard to obtain" results, even in the face of failure.

  • Etc, etc, etc.


Don't mistake my comments as a plea to stop trying. :) Or as an excuse to put in less than an honest day's work for an honest day's pay. But the benefits of "trying" and "showing up on time" start to fade over time in the face of consistent failure. At some point you have to change your approach or change what you do.

How to judge when to do that? Performance=results!

8 comments:

  1. Thanks for the Performance = Results commentary. Upon my first observation of the title (Performance = Results), and the subsequent reading of the content, I translated your meaning to be that performance does not really equal results, but rather it equals only performance be it successful or not. What I did read and understand from between the lines of your message was that success in the acquisition of desired and expected result has much more to do with preparation than performance and that in fact without preparation our performance is somewhat of a charade. I paraphrase Henry Ford: The secret to success is getting ready!

    ReplyDelete
  2. A good manager will also understand what "results" really means. I work in software development (not for the Church), and I see many software engineers getting "results", but often not "true value" in those results - meaning they constantly finish tasks quickly, but not effectively. But often those tasks do not "hold up" - meaning when the software is moved to production, bugs are everywhere, and then large chunks of code needs to be rewritten and redesigned. I always encourage my team to take a little longer to make sure that their tasks are completed correctly before they are completed quickly. I would rather have a software engineer on my team who completes 10 tasks correctly than 20 tasks partially incorrectly within the same time frame. I will take a quality-conscience employee over a results-conscience employee anyday. Over time, quality is far more productive, and really produces results.

    ReplyDelete
  3. It sounds very nice in theory but I have yet to meet the first manager who actually works like that. Why pay a person for a full week when he can apparently do his job properly in 20 hours. Doesn't make sense to me.

    [Joel: The point I was trying to make was really the opposite. If you work 40 hours per week and don't produce value then you're not performing. Performance equals results, not effort.]

    ReplyDelete
  4. Today's management often wants impossible schedules met in which to satisfy impossible "features" that were sold to customers.

    I often say "If you don't want to spend the time doing it right the first time, when are you going to find the time to do it later?"

    Some managers don't care, and rely on "Good enough" or "Hope for the best". Outstanding companies will listen to their customers and go beyond giving them what they want - they give them GREAT SERVICE. It seems to be sorely lacking in today's workplace in so many ways when "going that extra mile" may not always be recognized. But you'd be surprised when it is...

    ReplyDelete
  5. I like your focus and in my experience teams that focus on results tend to start 'winning' and succeeding, which solves a host of internal problems and distractions (not to mention improving the lives of their customers). I've managed performance in the Church for many years and believe employees want clear expectations. Team members appreciate managers who see and reward results rather than monitor and dictate behavior. We shouldn't forget, in all this, that results must equate to something the customer values.

    ReplyDelete
  6. Richard,

    My boss does it for me. He knows it will end up costing more to replace me than to give me projects and let me get it done my own way. I put in 20 hours one week and well over 40 another. He lets me coach football in the fall (still covering the normal responsibilities of my job), and knows I'll make it up to him in the winter and spring. I've been here 7 years, and he knows it's the only reason I'm still here. He's OK with it because he knows I get the job done.

    The only difference between me and Joel's employee is that I'm not anoying to be around. I hope.

    ReplyDelete
  7. This reminds me to two experiences:
    1. In Japan, where I currently work, sales people are rewarded for effort. Working hard is rewarded even if they do not make any sales. A very strange way to run a sales department.

    2. As an IT director, I had an employee who I was having a hard time motivating. Finally, during an interview with him, I found his motivation to be free time to play ping pong and foosball. I told him if he delivered, he could play games as much as he wanted. Within a few weeks, the servers and systems he was responsible for had nearly no problems, the backups worked each night, and there were virtually no user-reported problems. He got to play as much as he wanted. The one drawback was he was very persuasive, and persuaded folks from other groups to play with him, thus lowering their productivity.

    ReplyDelete
  8. Excellent posting. I have been wanting to tell my managers this for years.

    ReplyDelete