

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><title>Smart Ways To Work</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head><body bgcolor="#000099" leftmargin="0" topmargin="0"><table border="0" width="766" cellspacing="0" cellpadding="0" bgcolor="#FFFFFF"><tr align="left" valign="top" bgcolor="#FFFFFF"><td colspan="4" align="left" valign="top"><a href="../index.html"><img src="../img/header_logo.gif" alt="Logo" width="170" height="83" align="top" border="0"></a><img src="../img/header_address.gif" alt="" width="596" height="83" align="top"></td></tr><tr align="left" valign="top" bgcolor="#FFFFFF"><td bgcolor="#000099" width=88 height=1 nowrap><spacer type=block width=88 height=1><center><a href="../index.html"><img src="../img/nav_home.gif" width="75" height="20" border="0"></a> <a href="../about.html"><img src="../img/nav_about.gif" width="75" height="20" vspace="1" border="0"></a> <a href="../books.html"><img src="../img/nav_books.gif" alt="Books" width="75" height="20" border="0"></a> <a href=../columns.html><img src="../img/nav_columns.gif" width="75" height="20" vspace="1" border="0"></a> <a href="../consulting.html"><img src="../img/nav_consulting.gif" width="75" height="20" border="0"></a> <a href="../diversity.html"><img src="../img/nav_diversity.gif" width="75" height="20" vspace="1" border="0"></a> <a href="../media.html"><img src="../img/nav_media.gif" width="75" height="20" border="0"></a> <a href="../speeches.html"><img src="../img/nav_speeches.gif" width="75" height="20" vspace="1" border="0"></a> <a href="../training.html"><img src="../img/nav_training.gif" alt="Training" width="75" height="20" border="0"></a> <br><br><a href="../mailto:odette@smartwaystowork.com"><b><font color="#FF9900" size="2" face="Geneva, Arial">Contact<br> 
Odette</font></b></a>
</center></td><td bgcolor="#FFFFFF" width=10 height=1 nowrap><spacer type=block width=10 height=1></td>
    <td width="658" align="left" valign="top">
      <!-- start content here -->
      <b><font size="3" face="Helvetica, Arial">Surviving Employee Evaluations</font></b>
<p></p>

<p><font face="Geneva, Arial" size="2">There are very few managers or supervisors 

  who enjoy conducting employee evaluations. The entire process is fraught with 

  anxiety, and they are often delayed until the last minute. In fact, missing 

  the scheduled review date entirely is not uncommon. Annual reviews need not 

  be a heavy weight around your neck. The secret is to manage your interactions 

  with the employee throughout the year. This will provide the foundation for 

  your formal discussion.</font></p>

<p><font face="Geneva, Arial" size="2"><b>Before</b></font></p>

<p><font face="Geneva, Arial" size="2">Throughout the year, discuss performance 

  issues as they occur. This helps the employee understand your concerns, and 

  offers an opportunity to make changes. During these regular mini-reviews, take 

  notes; you will then have a running track record of performance from which you 

  can draw the necessary information for the formal review. The content of an 

  evaluation should never come as a surprise to an employee. The conversation 

  should be more of a summary discussion and never be perceived as a trap.</font></p>

      <p><font face="Geneva, Arial" size="2">Reviews take a lot of focus, attention 

        and emotional energy. Try to avoid scheduling more than two on the same 

        day. You don't want to get burned out on the process. If the review is 

        going to be uncomfortable or highly emotional&#151;i.e. you are placing 

        the employee on a probationary status, schedule the discussion for a Friday. 

        That gives the person the weekend to really think about the situation.</font></p>

<p><font face="Geneva, Arial" size="2"><b>During</b></font></p>

<p><font face="Geneva, Arial" size="2">Give yourself enough time to conduct the 

  review without being rushed. Hold all your calls and do not allow interruptions. 

  The review needs to be thorough. Avoid superficial or tangential issues because 

  that will cause two problems. One, you will not get to the underlying concerns 

  and (2) you risk the employee's misunderstanding the significance of the review 

  process. Hone in on the important and avoid being sidetracked by transient or 

  less critical issues.</font></p>

<p><font face="Geneva, Arial" size="2">Unless you are discussing a pattern of 

  behavior with the view to making recommendations for change, do not dwell on 

  past mistakes. Try to determine the reasons behind a series of misjudgments 

  so that the underlying problem can be identified and addressed. A conversation 

  outlining every date that the person was late to work is less useful than a 

  review of the policy about tardiness, a discussion about the cause, and an agreement 

  reached about what will happen in the future to prevent the tardiness.</font></p>

<p><font face="Geneva, Arial" size="2">People like to feel good about themselves 

  and hear about what they do well. Although evaluations are opportunities to 

  discuss difficulties, problems, or poor performance, they should be balanced 

  with the positives so that the employee has a well-rounded view of his or her 

  performance.</font></p>

<p><font face="Geneva, Arial" size="2">Be cautious about comparing one person 

  to your star performer. That can backfire. Comparisons can set up internal rivalries. 

  Asking a high performer to train another on a specific task is different from 

  a "why can't you be more like her" comparison.</font></p>

<p><font face="Geneva, Arial" size="2">Reviews are not debates or arguments. If 

  you have made a judgment and it is well-reasoned, stick by it and do not let 

  the conversation degenerate. Resist the tendency to be defensive about your 

  judgments. Back up your statements with research and documentation. If the two 

  of you cannot come to agreement, then there are other steps you can take, including 

  referring that employee to human resources.</font></p>

      <p><font face="Geneva, Arial" size="2">Your goal in a review is to solve 

        problems, coach development, and provide support and encouragement to 

        enable the person to excel . During the problem-solving phase, it is not 

        your job to come up with all of the possible solutions. Involve the employee 

        in identifying options so that he or she takes ownership for the strategies. 

        This not only saves you time and energy, but it reduces the likelihood 

        of that person coming back saying, "Well, I never thought that idea would 

        work anyway." In the same vain, avoid like the plague any discussions 

        that start with, "If I were you..."</font></p>

<p><font face="Geneva, Arial" size="2"><b>After</b></font></p>

<p><font face="Geneva, Arial" size="2">Transfer pertinent information from your 

  notes. Note any commitment dates on your calendar. Write up a summary of the 

  discussion for later reference. It never hurts to review the interaction to 

  determine what, if anything, you would do differently the next time. If you 

  view performance evaluations as more of a summary of a series of interactions 

  that have taken place throughout the year, they need not be onerous. Remember, 

  the end result should not be simply checking a task off your to-do list but 

  rather improved performance from someone you work closely with and depend upon. 

  </font></p>

<!-- end content here --><br><font face="Geneva, Arial" size="2">      <hr><!--#include virtual="footer.html" --><a href=../columns.html><strong>Return to Columns Menu</strong></a> </font>       <br>      <br></td><td bgcolor="#FFFFFF" width=10 height=1 nowrap><spacer type=block width=10 height=1></td></tr></table><br></body></html>