I used to think these were a waste of time, too. Then I came up with a different approache to using them. Here are my suggestions.

  1. Regardless of what management wants (or you think they want), put exactly what you want to do in your start of year planning. Make your manager change it. Note in the document that it was changed and whether you agree with the change or not. (If you don't get to put in the document what you want, why are you filling it out at all?)
  2. If, in the next year, you are asked to work on something not in the document, treat it like a change of scope/requirements. Make sure the document is updated and the change is recorded.
  3. At year end, know why you've successfully completed or failed to complete your plan. Save emails.
  4. Basically, treat your job like a development project.

If nothing else, you get to make statements like, "By adding this new responsibility to my performance plan, I would have 11 objectives," (there are always 10 blanks for objectives aren't there?), "In order to fairly assess my performance alongside my coworkers, it seems we would either need to remove one of my objectives, or give everyone else another."

--Solo

--
You said you wanted to be around when I made a mistake; well, this could be it, sweetheart.

In reply to Re: Annual Self Appraisal forms and all this (censored) by Solo
in thread Annual Self Appraisal forms and all this (censored) by Jenda

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.