<?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>robborley.com &#187; recruitment</title>
	<atom:link href="http://www.robborley.com/category/recruitment/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.robborley.com</link>
	<description>... because everyone else was doing it.</description>
	<lastBuildDate>Wed, 02 Jun 2010 15:25:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The Joel Test: An insight into Headscapes recruitment policy</title>
		<link>http://www.robborley.com/2010/02/23/the-joel-test-an-insight-into-headscapes-recruitment-policy/</link>
		<comments>http://www.robborley.com/2010/02/23/the-joel-test-an-insight-into-headscapes-recruitment-policy/#comments</comments>
		<pubDate>Tue, 23 Feb 2010 13:29:28 +0000</pubDate>
		<dc:creator>Rob Borley</dc:creator>
				<category><![CDATA[headscape]]></category>
		<category><![CDATA[recruitment]]></category>

		<guid isPermaLink="false">http://www.robborley.com/2010/02/23/the-joel-test-an-insight-into-headscapes-recruitment-policy/</guid>
		<description><![CDATA[The Joel Test no.11
Published: February 21, 2010 16:00
The application process is there for two reasons. One, for the employer to get to know if the employee  is a good fit. And second for the employee to get to know if the employer is a good fit.  With any role a new hire needs [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: left; margin-left: 10px;  margin-right: 15px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.robborley.com%2F2010%2F02%2F23%2Fthe-joel-test-an-insight-into-headscapes-recruitment-policy%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.robborley.com%2F2010%2F02%2F23%2Fthe-joel-test-an-insight-into-headscapes-recruitment-policy%2F" height="61" width="51" /></a></div><h3>The Joel Test no.11</h3>
<p>Published: February 21, 2010 16:00</p>
<p>The application process is there for two reasons. One, for the employer to get to know if the employee  is a good fit. And second for the employee to get to know if the employer is a good fit.  With any role a new hire needs to address a number of &#8216;transferable skills&#8217; questions such as &#8216;can this person communicate clearly&#8217;  and &#8216;can this person work with others&#8217;.<br />
However, on top of this each role has specific skillset requirements.  It is  these requirements that need bespoke methods of identification.  The question is, what methods should we use?</p>
<p>All article content is licenced under a <a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons Attribution-Noncommercial Licence</a>.</p>
<p>via <a href="http://cargowire.net/articles/joeltest11">cargowire.net</a></p>
<p><span style="font-size: 10px; "><a href="http://posterous.com">Posted via web</a> from <a href="http://bobscape.com/the-joel-test-an-insight-into-headscapes-recr">bobscape | posterous</a></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.robborley.com/2010/02/23/the-joel-test-an-insight-into-headscapes-recruitment-policy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Warm Body Syndrome &#8211; reprise</title>
		<link>http://www.robborley.com/2009/12/08/warm-body-syndrome-reprise/</link>
		<comments>http://www.robborley.com/2009/12/08/warm-body-syndrome-reprise/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 11:29:40 +0000</pubDate>
		<dc:creator>Rob Borley</dc:creator>
				<category><![CDATA[headscape]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[recruitment]]></category>

		<guid isPermaLink="false">http://www.robborley.com/?p=176</guid>
		<description><![CDATA[Back in March, when I first had an attempt at launching this blog, I published an article called &#8220;Warm Body Syndrome&#8220;. Despite nobody actually reading it at the time (except Sam Barnes; thanks Sam) it is my most popular post via google searches.
As Headscape are back on the recruitment merry-go-round (product marketing or something(?) &#124; tech guy/gal), and some people [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: left; margin-left: 10px;  margin-right: 15px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.robborley.com%2F2009%2F12%2F08%2Fwarm-body-syndrome-reprise%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.robborley.com%2F2009%2F12%2F08%2Fwarm-body-syndrome-reprise%2F" height="61" width="51" /></a></div><p>Back in March, when I first had an attempt at launching this blog, I published an article called &#8220;<a href="http://www.robborley.com/2009/03/16/warm-body-syndrome/">Warm Body Syndrome</a>&#8220;. Despite nobody actually reading it at the time (except <a href="http://www.thesambarnes.com/" target="_blank">Sam Barnes</a>; thanks Sam) it is my most popular post via google searches.</p>
<p>As Headscape are back on the recruitment merry-go-round <a href="http://boagworld.com/news/product-and-marketing" target="_blank">(product marketing or something(?)</a> | <a href="http://boagworld.com/news/another-job">tech guy/gal</a>), and some people actually  read this blog now, it seemed like a good time to float this post back to the top again.</p>
<h3>Found any warm bodies?</h3>
<p>Have a read of  &#8221;<a href="http://www.robborley.com/2009/03/16/warm-body-syndrome/">Warm Body Syndrome</a>&#8220;. Google stats can&#8217;t be wrong! It must be good. *smile*</p>
<p>Let me know what you think. Have you ever recruited a &#8220;warm body&#8221;? Maybe you have been a &#8220;warm body&#8221;. What was your experience?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.robborley.com/2009/12/08/warm-body-syndrome-reprise/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Warm body syndrome</title>
		<link>http://www.robborley.com/2009/03/16/warm-body-syndrome/</link>
		<comments>http://www.robborley.com/2009/03/16/warm-body-syndrome/#comments</comments>
		<pubDate>Mon, 16 Mar 2009 19:33:53 +0000</pubDate>
		<dc:creator>Rob Borley</dc:creator>
				<category><![CDATA[leadership]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[recruitment]]></category>
		<category><![CDATA[team]]></category>

		<guid isPermaLink="false">http://www.robborley.com/?p=30</guid>
		<description><![CDATA[We&#8217;ve all been there. There is a hole in your team, a job that needs to be done. Maybe somebody has moved on leaving a vacancy or your activities have expanded to such an extent that new skills or more resource is needed. And what&#8217;s more, you need it now!
The temptation is to fill the [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: left; margin-left: 10px;  margin-right: 15px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.robborley.com%2F2009%2F03%2F16%2Fwarm-body-syndrome%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.robborley.com%2F2009%2F03%2F16%2Fwarm-body-syndrome%2F" height="61" width="51" /></a></div><p>We&#8217;ve all been there. There is a hole in your team, a job that needs to be done. Maybe somebody has moved on leaving a vacancy or your activities have expanded to such an extent that new skills or more resource is needed. And what&#8217;s more, you need it now!</p>
<p>The temptation is to fill the vacancy as quickly as possible. The first person who is willing and able is given the job. The nearest warm body is plucked out of the air and put in place as soon as possible. You just succumbed to &#8216;warm body syndrome&#8217;.</p>
<p>Ok, so you might get lucky. Somebody was in the right place at the right time and they are perfect for the role. They have all the skills, they have the temperament, you get on well, everything is a roaring success and all live happily ever after. However, sadly, this isn&#8217;t the norm. A simple rule to remember is; &#8220;just because they can, doesn&#8217;t mean they should.&#8221;</p>
<p>A few things to bear in mind:</p>
<ol>
<li>You are not doing anybody a favour by asking somebody to do a job they can&#8217;t do. </li>
<li>You are not helping anybody out by agreeing to a request from somebody to do a job that they are not able to do.</li>
<li>Making a wrong decision is expensive!</li>
<li>Making a wrong decision is waste of time!</li>
<li>Making a wrong decision just upsets all involved.</li>
<li>Making a wrong decision will mean you just have to go through the whole process again.</li>
</ol>
<p>It&#8217;s best to take your time over such things. Don&#8217;t appoint somebody just because there is nobody else. If they are not right for the role then that&#8217;s it. End of story. Remember that undoing this decision is going to be a drawn out and painful process. It&#8217;s worth taking your time and getting it right first time.</p>
<p>This can be difficult. There is a temptation to either put somebody in post because they really want the role. Or to appoint because you really need the position filled.  But it is best to not appoint at all then to make the wrong decision. Taking your time and waiting for the right person may mean that the existing team need to work harder for a while. It may me somebody in the team doesn&#8217;t get the promotion that they have been after. It may mean the new initiative that you want to kick off will need to wait. But all these things are better than the alternative.</p>
<p>Resist the quick fix. Take your time. Get it right.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.robborley.com/2009/03/16/warm-body-syndrome/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
