The Seven No-No's of Performance Evaluation - education

School Administrator, Dec, 1999 by David L. Johnston

The biblical injunction of judgment day is a familiar one, but little did we know there would be more than one.

These days have become known as personnel evaluation. They are no longer judgments nor a day, but instead a process, an event, a performance review, a culminating activity and such. We no longer judge performance, we evaluate it. We no longer judge people, we evaluate them.

As education takes on a higher profile and more folks see it as the most important task before our country, we can expect more judgment days. Whatever performance evaluation is called, rest assured it will be non-threatening, good for you and done with your best interests at heart.

The evaluation of personnel has taken on a new glow as those who evaluate staff performance exercise their faith in the perfectibility of other colleagues. Through evaluation they believe they send messages that can lead to improved schools, increased student achievement and an ever-higher level of performance by those evaluated.

In education, consultants roam the evaluation landscape, peddling their wonderful plans for improving personnel evaluation. Their suggested methods include performance questions such as the ever difficult, "Is the building still standing at the end of the school year?" to the more sublime, "If the building fell on you, how would you deal with the school board?"

Blundering Acts

To ensure that evaluation in your school district becomes an exercise that even Machiavelli would embrace, I have compiled the seven blunders of personnel evaluation now most commonly in use.

No. 1: Trivial Pursuit.

With this method, the evaluator must know all kinds of details, but must never pull the details together into a recognizable descriptive pattern of the performance evaluated. Using Trivial Pursuit, the evaluator begins the year accumulating bits and pieces of information about the evaluatee. No qualitative priority is assigned to the bits and pieces. They are all equal.

Then, at the evaluation conference, all the pieces are brought to the evaluation discussion. If done right, the staff member evaluated will be overwhelmed by their number. More is better!

The random use of bits of information does not lend itself to drawing conclusions about what performance means. Instead, Trivial Pursuit drives a wedge in the head of the person being evaluated because priorities for improvement are random and meaningless.

No. 2: The Shell Game.

This is a fairly straightforward approach. The evaluator asks a staff member to rate himself or herself by identifying personal strengths and weaknesses prior to the evaluation conference. In turn, the staff member's assessment is forwarded to the evaluator. When the evaluation conference is held, the staff member will expect to hear about the evaluation originally forwarded to the evaluator. Surprise! The evaluator sets out three separate evaluations, each under separate cover. One of them is the original.

The staff member will be asked to guess which belongs to him or her. If she picks wrong, she gets someone else's evaluation or the evaluator's creative interpretation of her self-evaluation. The Shell Game is good for surprises and effective in alienating whomever you are evaluating. It is also illegal on the streets of New York.

No. 3: I Perceptor.

This evaluation approach is based on an interior monologue of your evaluator without regard for performance criteria or observation. The person relying on the I Perceptor evaluation approach never questions the condition of the evaluator's mind or its relationship to reality when drawing evaluative conclusions.

This psychological approach to evaluation is a bit deeper than the Shell Game and effectively alienates and demoralizes the evaluated. There is no defense against it. It is based upon facts that only exist in the evaluator's head--regardless of what truths or misconceptions are or are not!

No. 4: "Gotcha."

This approach is easy and requires little thought. Throughout the year, the evaluator observes a staff member's performance and notes it. The more "good" performance items noted, the better "Gotcha" works.

At the evaluation conference, all items on the good performance list are noted without comment. This list of good stuff is immediately followed by mention of any small, inconsequential performance area that went awry such as, "I noticed when you sent a memo there was a bit of confusion over it. This is something you had better work on." Gotcha!

It is upon this incidental negative performance that the overall evaluation is built. The Gotcha technique is particularly effective when evaluators lack time for more complicated evaluation methods and are insecure about their performance in comparison to the person evaluated.

Gotcha is simple in that it requires little intelligence.

No. 5: Covert Evaluation.

Training as a CIA agent helps, but is not required. What is required is a true sense of secretiveness and the ability to gather information clandestinely. The person being evaluated is never asked the truth of the remarks others make about him or her. Nor does the evaluator question the reliability of the information.


 

BNET TalkbackShare your ideas and expertise on this topic

Please add your comment:

  1. You are currently: a Guest |
  2.  

Basic HTML tags that work in comments are: bold (<b></b>), italic (<i></i>), underline (<u></u>), and hyperlink (<a href></a)

advertisement
Click Here
advertisement
  • Click Here
  • Click Here
  • Click Here
  • Click Here
advertisement

Content provided in partnership with Thompson Gale