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.
- 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?)
- 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.
- At year end, know why you've successfully completed or failed to complete your plan. Save emails.
- 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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|