This is what I would put, if I were answering this. (I'm in that lucky group that doesn't have to waste time with this dreck.)

  1. Financials (profitability, growth, efficiency, headcount, productivity, sales, etc.)

    Because we use Perl, productivity is way up. This means that efficiency is much higher, too. Profitability is also up, due to increased growth and less headcount. Sales ... well, I'd rather we didn't have a sales force because all they do is sign contracts then check to see if we can fulfill our end.

  2. Service (customer retention, customer satisfaction, level of service, customer survey results, etc.)

    Because we use Perl, customer retention and satisfaction is much higher because we don't have any more bugs. This means we don't have to worry about our level of service because they never bother us.

  3. People (employee development, employee morale, employee commitment, people survey, performance appraisals completed, objectives set, low turnover rate, etc.)

    Because we use Perl, we don't need as many people. Therefore, the amount of money we can spend on each person is higher, even though we've cut the HR and training budgets. This has resulted in higher employee morale and commitment, giving us better employee development. The turnover rate is also down to 1%. (It would be lower except for the fact that Perl doesn't prevent car accidents ... yet.)

  4. Competition/Market Share

    Because we use Perl, we have much higher market share than our competitors who use inferior technologies, such as Java and .NET. (However, we do have to worry about that one company that uses Lisp ...)

  5. Innovation (product or process improvements, problem solving, advancements, etc.)

    Because we use Perl, we can introduce new innovations much quicker than anyone else. In addition, because we only employ members of Perlmonks, our problem solving capabilities as a team are much higher.

  6. Professional Development (personal goals for your professional development)

    I want your salary.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

In reply to Re: Annual Self Appraisal forms and all this (censored) by dragonchild
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.