<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Spin-O-Rama &#187; performance appraisal</title>
	<atom:link href="http://stevebellnow.com/tag/performance-appraisal/feed/" rel="self" type="application/rss+xml" />
	<link>http://stevebellnow.com</link>
	<description>Team Shoots, Team Scores</description>
	<lastBuildDate>Wed, 08 Sep 2010 18:20:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Writing About Yourself</title>
		<link>http://stevebellnow.com/2010/03/09/writing-about-yourself/</link>
		<comments>http://stevebellnow.com/2010/03/09/writing-about-yourself/#comments</comments>
		<pubDate>Tue, 09 Mar 2010 17:39:38 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[Observations]]></category>
		<category><![CDATA[people]]></category>
		<category><![CDATA[performance appraisal]]></category>
		<category><![CDATA[reflections]]></category>
		<category><![CDATA[thoughts]]></category>

		<guid isPermaLink="false">http://stevebellnow.com/?p=634</guid>
		<description><![CDATA[Over the past year, I have had plenty of opportunities to write about myself and I don&#8217;t like it. I find it extremely difficult to do. With the second of self assessment done, rewrote the about me section of this blog a number of times and writing up a bio for a speaking engagement; each [...]]]></description>
			<content:encoded><![CDATA[<p>Over the past year, I have had plenty of opportunities to write about myself and I don&#8217;t like it. I find it extremely difficult to do. With the second of self assessment done, rewrote the about me section of this blog a number of times and writing up a bio for a speaking engagement; each and everyone of them necessary evils that needed to be done. Do you find these activities a struggle? I know I do. Each of them have a different purpose, but they all have one thing in common &#8211; me. I find them uncomfortable to write. The self assessment is something that I have had to do now for 26 years. You would think I should be good at it, well I am not.  Writing about me comes off as bragging and somewhat self serving. I know, I should just suck it up and do my best work. Still does not make it any easier to do.</p>
<p>So, what do I do to make it a bit less painful? Some of my tips/tricks.</p>
<ul>
<li><strong>Documentation</strong>- make sure that you have plenty. As a manager, I have to keep documentation on my direct reports. Why not myself? Treat yourself no different than one of your employee&#8217;s. Keep your records, keep your email thank-yous, awards and anything that will help define your work.</li>
<li><strong>Make Lists</strong> &#8211; sit down with the documentation and start a list of accomplishments, feedback, awards and whatever else is in your folder. This will help to form what will be written. Sort of like a brainstorm list for writing.</li>
<li><strong>Put yourself in a good state of mind</strong> &#8211; insure that you are feeling good, have plenty of time to focus and there are no distractions (people or work). Having a &#8220;good&#8221; day helps. If you wait till the last minute, you will feel rushed and the writing will show it.</li>
<li><strong>Give Examples</strong> &#8211; here is where the documentation is very handy. Make sure to call out the specific examples, involvement you played and the impact. </li>
<li><strong>Be Objective</strong>- when reviewing the documentation and reviewing the rough draft, be objective on everything. In my case, I am overly critical, sometimes too much. Look at the impact &#8211; answer the &#8220;so what&#8221; question. Be real. While spending time reviewing, pay close attention to the tune of the messages.</li>
</ul>
<p>Writing about yourself may come easy to some, but not me. I have to work at it more-so for myself than my direct reports. I have little to no difficulty writing about them. Do you have any tips/tricks to help you with writing about you?</p>
]]></content:encoded>
			<wfw:commentRss>http://stevebellnow.com/2010/03/09/writing-about-yourself/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Now, Is The Time!</title>
		<link>http://stevebellnow.com/2009/12/23/now-is-the-time/</link>
		<comments>http://stevebellnow.com/2009/12/23/now-is-the-time/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 17:30:55 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[Observations]]></category>
		<category><![CDATA[people]]></category>
		<category><![CDATA[performance appraisal]]></category>
		<category><![CDATA[reflections]]></category>

		<guid isPermaLink="false">http://stevebellnow.com/?p=521</guid>
		<description><![CDATA[The end of the year normally very busy, but not when it comes to work. Well, as soon as I publish this &#8211; my inbox will explode with busy work. Normally, folks love to take the weeks of Christmas and New Years off. For the past couple of years, I have found that this is [...]]]></description>
			<content:encoded><![CDATA[<p>The end of the year normally very busy, but not when it comes to work. <em>Well, as soon as I publish this &#8211; my inbox will explode with busy work. </em>Normally, folks love to take the weeks of Christmas and New Years off. For the past couple of years, I have found that this is a wonderful time to get work done. Real work! Get ahead of the game, work!</p>
<p>I went into the office on Monday, because I had a couple of meetings that I had to have. One was with a person that wanted to get active in the companies internal social computing capabilities. I am always into having discussion with folks to demonstrate the social capabilities, discuss potential opportunities, help out or just plain teach. The passion is real, I looked forward to coming into the office, when very few folks were going to be there. I always am on a high after these meetings. So, I scheduled another meeting, one that I am not a fan of &#8211; going over the changes needed to roadmap presentations. Boring and necessary topic. Start the day &#8211; in outstanding fashion, tackle the not so much fun subject next&#8230; Seemed to work for me.</p>
<p>What I really use the week for is &#8211; getting ahead on some of the work that is going to hit and hit hard:</p>
<ul>
<li>Yearly performance appraisal&#8217;s are going to be a big time sync over the January timeframe (getting ahead of that is all goodness)</li>
<li>Budget 2010 should be finalized &#8211; and everyone and their brothers are going to want to know what is coming and when (hence the roadmap discussion). The amount of cycles that will be consumed will be large.</li>
<li>Writing my rev 0 self-assessment for my boss. Since I manage a team, I need my folks to complete theirs to insure that I have not missed anything important.</li>
<li>Preparing for the welcome to the new year fire drill. You know that topic that just keeps on giving that makes your head spin. This year is no different &#8211; centers on social computing again. 2009 for us, was a year of really starting to take shape. Now that some of the leaders have a better understanding (enough to be dangerous, but not enough to fully understand) &#8211; they want to see how we can save some bucks and maybe look to consolidate and integrate. Nobel efforts, but a bit too early, in my opinion.</li>
<li>Setting up the overall groups expectations for 2010. Once everyone is back from their holidays, they will be recharged and ready to go. Time to have what expectations fully lined out. Budget is set, work on the roadmaps has started and we should start to have some vision of 2010.</li>
<li>Lastly, celebrating 2009! Lots of good stuff happened in 2009, don&#8217;t forget that. Have fun and celebrate the wins. Celebrate the near wins&#8230; 2009 was rough in many ways, but I know that I had some wins to celebrate. I told my team to do the same thing!</li>
</ul>
<p>It is nice to have some time to slow down and spend the cycles during the periods when the work force is limited (out enjoying the holidays). For me, it helps to kick of the new year with some work already in the can, or at the very least shaped up to complete on time.</p>
]]></content:encoded>
			<wfw:commentRss>http://stevebellnow.com/2009/12/23/now-is-the-time/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Performance Appraisal: Documenting the Year in Review</title>
		<link>http://stevebellnow.com/2009/05/28/performance-appraisal-documenting-the-year-in-review/</link>
		<comments>http://stevebellnow.com/2009/05/28/performance-appraisal-documenting-the-year-in-review/#comments</comments>
		<pubDate>Thu, 28 May 2009 13:38:49 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[Leading Teams]]></category>
		<category><![CDATA[managing]]></category>
		<category><![CDATA[performance appraisal]]></category>
		<category><![CDATA[performance management]]></category>

		<guid isPermaLink="false">http://stevebellnow.com/?p=168</guid>
		<description><![CDATA[  Performance appraisals, performance reviews, appraisal forms, whatever you want to call them, I&#8217;ll use appraisal. I&#8217;m not sure if it has been the 27 years of writing these for my team or having one done about me, but I think the appraisal is a necessary part of the whole process.  Yearly also seems to [...]]]></description>
			<content:encoded><![CDATA[<p> </p>
<p style="font-size: 11pt; margin: 0in; font-family: Calibri;">Performance appraisals, performance reviews, appraisal forms, whatever you want to call them, I&#8217;ll use appraisal. I&#8217;m not sure if it has been the 27 years of writing these for my team or having one done about me, but I think the appraisal is a necessary part of the whole process.<span style="mso-spacerun: yes;">  </span>Yearly also seems to be the right timeframe. I have done this with every six months to 18 months &#8211; 12 months (January to December). Built in reminders that when the holiday season is coming upon us &#8211; it is time to close the documented part of the year.</p>
<p style="font-size: 11pt; margin: 0in; font-family: Calibri;">From my experiences and tweaking of my past 26 years, here is the checklist for how to close the annual performance appraisal &#8211; start to end!</p>
<p style="font-size: 11pt; margin: 0in; font-family: Calibri;"><strong>Preparation for annual performance appraisal:</strong></p>
<ul style="margin-top: 0in; margin-bottom: 0in; margin-left: 0.75in; direction: ltr; unicode-bidi: embed;" type="circle">
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">Kick-off the end of the year, with a nice reminder to your team that our performance appraisal time is now just around the corner. I usually send this message out with expectations, timelines and expected closure.</span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">Within the initial message, my employee&#8217;s are given a blank document for them to write a self assessment on their key accomplishments, their strengths and some areas that they may want to improve on in the coming year. This provides them some input on their overall assessment.</span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">Provide the opportunity for broader feedback. I use a 360 degree performance feedback request.<span style="mso-spacerun: yes;">  </span>That incorporates feedback from the employee&#8217;s peers, customers, and people who may report to him.<span style="mso-spacerun: yes;">  </span>Each employee can provide me names of the above that they feel will be a good source of providing feedback (I also reserve the right to add additional names). We really want a well rounded loop of feedback.</span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">The self assessment and 360 feedback requests have deadlines that all will be due to me.</span></li>
</ul>
<p style="font-weight: bold; font-size: 11pt; margin: 0in; font-family: Calibri;">Assessing employee and the team performance:</p>
<ul style="margin-top: 0in; margin-bottom: 0in; margin-left: 0.75in; direction: ltr; unicode-bidi: embed;" type="circle">
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">Start the Rev 1 appraisal. This is where I sit down and review the self assessment, 360 comments, during the year coaching session notes, employee 1:1 file (all feedback good or bad, awards and such for the complete year) and write my document that I would say is very close to the performance appraisal (Rev 1). Focus on the expectations for the coming year &#8211; keeping the cycle alive.</span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">Sit down and discuss the Rev 1 document with the employee. One more attempt to review the document and for each to provide feedback. Usually there are minor tweaks or maybe some missing information that may come to the surface, but rarely.</span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">Take my individual employee&#8217;s performance reviews and assess each to the overall team. This is where folks are being ranked and rated to each other. Depending on the team, you may have senior folks and junior folks on the same team &#8211; and assessing them could get a bit difficult. I usually have to remind myself to look at their job expectations, their grade level and level set my expectations to match. Finish up the process by giving each a rating.</span></li>
</ul>
<p style="font-weight: bold; font-size: 11pt; margin: 0in; font-family: Calibri;">Delivering the performance appraisal:</p>
<ul style="margin-top: 0in; margin-bottom: 0in; margin-left: 0.75in; direction: ltr; unicode-bidi: embed;" type="circle">
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">Insure to schedule the meetings! Coming up to an employee that happens to sit in the same site as you, is not really a welcome sight. If the employee&#8217;s are at different sites, insure to schedule conference rooms. Privacy is something that is important.</span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">The night before the scheduled appraisal review session, I send out the Rev 2 document. (I do this for both the folks on and off site). This is the complete review form &#8211; that has been reviewed many times by each of us, discussed and finished up. The main item that the employee really has not seen is the overall performance message and ranking/ratings.</span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">Minutes before the meeting &#8211; I send out to the employee&#8217;s that are off site &#8211; the overall pay letter. Each employee knows to come to the meeting with their laptop to open the emailed pay letter. For those on site, I have a copy for them.</span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">We discuss both documents in detail! Questions and comments &#8211; whatever is needed.</span></li>
</ul>
<p style="font-size: 11pt; margin: 0in 0in 0in 0.75in; font-family: Calibri;"> </p>
<p style="font-size: 11pt; margin: 0in 0in 0in 0.75in; font-family: Calibri;">Tips:</p>
<ul style="margin-top: 0in; margin-bottom: 0in; margin-left: 0.75in; direction: ltr; unicode-bidi: embed;" type="circle">
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">Never schedule these review sessions back to back! You may want to get it over with, but time to discuss is critical and needed. Running a marathon of performance appraisal meetings, is very taxing.</span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">Never schedule on a Friday! From past experience, this gives too much time between delivery and potential additional discussion. If this message is not going to be perceived well, the receiver really does not need to have their weekend wasted. Schedule those messages, early in the week…</span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">For off-site folks, try to be there, physically if possible. If travel is restricted, definitely try to use a video feed. Gauging reaction to messages is very difficult over the phone. </span></li>
<li style="margin-top: 0px; margin-bottom: 0px; vertical-align: middle;"><span style="font-size: 11pt; font-family: Calibri;">After completed, I usually give the employee some time to think about the appraisal some more, and if they have any questions and/or comments &#8211; to just get back to me by 3 days. This is when I usually close our companies policy by uploading the document to the employee&#8217;s record.</span></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://stevebellnow.com/2009/05/28/performance-appraisal-documenting-the-year-in-review/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  stevebellnow.com/tag/performance-appraisal/feed/ ) in 1.29342 seconds, on Sep 9th, 2010 at 10:42 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Sep 9th, 2010 at 11:42 pm UTC -->