<?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>TalentOnTarget &#187; appreciating team members</title>
	<atom:link href="http://www.talentontarget.com/index.php/tag/appreciating-team-members/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.talentontarget.com</link>
	<description></description>
	<lastBuildDate>Wed, 12 May 2010 14:08:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Why Generational Profiling Is Bad Management</title>
		<link>http://www.talentontarget.com/index.php/2010/05/why-generational-profiling-is-bad-management/</link>
		<comments>http://www.talentontarget.com/index.php/2010/05/why-generational-profiling-is-bad-management/#comments</comments>
		<pubDate>Wed, 05 May 2010 21:11:06 +0000</pubDate>
		<dc:creator>Rudolf Melik - Project Management Software Blog</dc:creator>
				<category><![CDATA[Generational Trends]]></category>
		<category><![CDATA[Globalization]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[workforce management]]></category>
		<category><![CDATA[appreciating team members]]></category>
		<category><![CDATA[dispersed workforce]]></category>
		<category><![CDATA[global competitiveness]]></category>
		<category><![CDATA[motivation]]></category>
		<category><![CDATA[project team members]]></category>

		<guid isPermaLink="false">http://www.talentontarget.com/?p=1011</guid>
		<description><![CDATA[Here is an interesting perspective on the Generation X, Y and Z at work talk we have all heard lately. Some excerpts:
Would you characterize your employees by gender, age, race, religion,  or in any other way when it comes to managing them and enabling them to  be successful at their jobs? Of course not. And I’m [...]]]></description>
			<content:encoded><![CDATA[<p><a title="Why Generational Profiling Is Bad Management" href="http://blogs.bnet.com/ceo/?p=4531&amp;tag=landing-pad;work-life" target="_blank">Here</a> is an interesting perspective on the Generation X, Y and Z at work talk we have all heard lately. Some excerpts:</p>
<blockquote><p>Would you characterize your employees by gender, age, race, religion,  or in any other way when it comes to managing them and enabling them to  be successful at their jobs? Of course not. And I’m not talking about  verbally or publicly. I’m talking about when you sit down to do their  review, determine their raise, have a one-on-one, or interview them,  would you take any of that stuff into account? Again, of course not.</p>
<p>You know why? Because there are at least a dozen more important and  relevant factors, like job performance, experience, knowledge, team  work, etc. The only profiling I’m aware of in the real business world  has to do with multinational companies managing workforces in other  countries where employment law, compensation, and culture are different.  To me, that makes sense.</p>
<p>But profiling groups by generation is ridiculous, no matter what the  management researchers and gurus say. Not to mention that it’s  dehumanizing.</p></blockquote>
<p>I somewhat agree with Steve Tobak&#8217;s observations in that some of this generation talk is overblown and its importance exaggerated. However, from our own experience at Tenrox younger generations have very different expectations. When it comes to recognition, rewards, raises and bonuses, of course you look at job performance, experience, knowledge and other such factors to determine what is appropriate. But everyone does not feel appreciated or get motivated the same way. For some, an equivalent valued gift, a few extra days off, a paid vacation works better than a cash bonus or a raise. We try to take such things into account when communicating with or rewarding our team members; and yes, the employee&#8217;s generation plays an important role in how we approach such discussions.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.talentontarget.com/index.php/2010/05/why-generational-profiling-is-bad-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Importance of Taking Breaks</title>
		<link>http://www.talentontarget.com/index.php/2010/01/the-importance-of-taking-breaks/</link>
		<comments>http://www.talentontarget.com/index.php/2010/01/the-importance-of-taking-breaks/#comments</comments>
		<pubDate>Wed, 13 Jan 2010 18:14:03 +0000</pubDate>
		<dc:creator>Rudolf Melik - Project Management Software Blog</dc:creator>
				<category><![CDATA[Good Books and Articles]]></category>
		<category><![CDATA[project workforce management]]></category>
		<category><![CDATA[workforce management]]></category>
		<category><![CDATA[appreciating team members]]></category>
		<category><![CDATA[dispersed workforce]]></category>
		<category><![CDATA[efficiency]]></category>
		<category><![CDATA[employee productivity]]></category>
		<category><![CDATA[managing projects]]></category>
		<category><![CDATA[productivity]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project management enterprise software project planning resource planning]]></category>

		<guid isPermaLink="false">http://www.talentontarget.com/?p=960</guid>
		<description><![CDATA[Here is an interesting article on the importance of taking breaks:
http://www.openforum.com/idea-hub/topics/the-world/article/break-through-by-taking-breaks-matthew-e-may
Some excerpts (although reading the entire article is definitely highly recommended):
Ever wonder why our best ideas come when we’re in the shower, driving, daydreaming, or sleeping?
When you look deeper into these ingeniously elegant solutions and brilliant flashes of insight you can see that they came [...]]]></description>
			<content:encoded><![CDATA[<p>Here is an interesting article on the importance of taking breaks:</p>
<p><a href="http://www.openforum.com/idea-hub/topics/the-world/article/break-through-by-taking-breaks-matthew-e-may" target="_blank">http://www.openforum.com/idea-hub/topics/the-world/article/break-through-by-taking-breaks-matthew-e-may</a></p>
<p>Some excerpts (although reading the entire article is definitely highly recommended):</p>
<blockquote><p><em>Ever wonder why our best ideas come when we’re in the shower, driving, daydreaming, or sleeping?</em></p>
<p><em>When you look deeper into these ingeniously elegant solutions and brilliant flashes of insight you can see that they came at strange times and in random locations. They didn&#8217;t occur while actually working on the problem but after an intense, prolonged struggle with it followed by a break. A change of scene and time away seems to have played a part.</em></p>
<p><em>Most &#8220;creatives&#8221;—artists, musicians, writers, etc.—instinctively know that idea incubation involves seemingly unproductive times, but that those downtimes and timeouts are important ingredients of immensely productive and creative periods. But until fairly recently the how, when, and why of being kissed by the muse was something of a myth and mystery, explained only by serendipity.</em></p>
<p><em>New studies show that creative revelations tend to come when the mind is engaged in an activity unrelated to the issue at hand; pressure is not conducive to recombining knowledge in new and different ways, the defining mark of creativity.</em></p>
<p><em>While no one yet knows the exact process, there’s an important implication for all of us: putting pressure on ourselves to try and make our brains work harder, more intensely, or more quickly, may only slow down our ability to arrive at new insights. In other words, if you’re looking to engineer a breakthrough, it may only come through a break. Your brain needs the calm before its storm.</em></p></blockquote>
<p>As one example, one of the best decisions we made at <a href="http://www.tenrox.com/" target="_blank">Tenrox</a> was to shut the company down between Christmas and New Year’s. We do not schedule any internal or external project work, customer calls, visits or implementations during this time. Our professional services and support team is also asked to provide nothing more than essential services by a handful of people who are on call. We have done this for the last two years and it has been an incredible success. Our team returns to work well rested, creative, and fully reenergized. We very much encourage our team to take breaks and all their vacation time on a regular basis. Working hard without sufficient breaks and “off the grid” time leads to an unproductive uninspired team.</p>
<p>Would be great to hear your perspective and suggestions for taking breaks and how you apply this to your project teams.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.talentontarget.com/index.php/2010/01/the-importance-of-taking-breaks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Taking people and their work for granted</title>
		<link>http://www.talentontarget.com/index.php/2008/11/taking-people-and-their-work-for-granted/</link>
		<comments>http://www.talentontarget.com/index.php/2008/11/taking-people-and-their-work-for-granted/#comments</comments>
		<pubDate>Tue, 11 Nov 2008 12:56:25 +0000</pubDate>
		<dc:creator>Rudolf Melik - Project Management Software Blog</dc:creator>
				<category><![CDATA[Enterprise Software]]></category>
		<category><![CDATA[appreciating team members]]></category>
		<category><![CDATA[project team members]]></category>
		<category><![CDATA[team spirit]]></category>

		<guid isPermaLink="false">http://www.tenrox.com/blogs/talentontarget/?p=44</guid>
		<description><![CDATA[I have enjoyed reading the newsletter about enterprise software&#0160;from Michael Burns for years now. I kind of always have taken it for granted that Michael will share his insight with us every month. When he did not write last month I felt like something was missing. It turns out Micheal had a personal health issue. [...]]]></description>
			<content:encoded><![CDATA[<p>I have enjoyed reading the <a href="http://www.180systemsblog.com" title="Enterprise software newsletter">newsletter about enterprise software</a>&#0160;from Michael Burns for years now. I kind of always have taken it for granted that Michael will share his insight with us every month. When he did not write last month I felt like something was missing. It turns out Micheal had a personal health issue. Here are some kind words of advice from Micheal, unrelated to project management but very much worth mentioning.</p>
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<p><em><strong>Something Personal</strong></em></p>
<p><em>I (Michael Burns) do most of the work in sending you our newsletter. We did not send our newsletter last month as I was in the hospital for 4 weeks, and have been recovering since then. I am making good progress and have begun working again. Working for me is great therapy as I enjoy what I do.</em></p>
<p><em>I have had lots of time to contemplate the universe while not well, and you would think that I would be able to share great words of wisdom. Alas, I can’t tell you anything that you don’t already know such as being thankful for health, family and friends. Unfortunately, most of us are so caught up in day-to-day living that we don’t show our appreciation or spend much time with those people we care about. Most of us will get angry over small things and miss the big picture. Don’t wait for a serious health problem to show your appreciation, and to spend quality time with family and good friends.</em></p>
</blockquote>
<p>Micheal, I wish you health and thank you, always, for sharing your thoughts and perspectives with us.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.talentontarget.com/index.php/2008/11/taking-people-and-their-work-for-granted/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
